Arama:

BPM for SugarCRM platform

[prisna-google-website-translator]

BPM for SugarCRM platform

SugarCRM is an affordable and easy to use customer relationship management (CRM) platform, designed to help businesses communicate with prospects, share sales information, close deals and keep customers happy. Thousands of successful companies use SugarCRM everyday to manage sales, marketing and support.

ProcessMaker is a cost effective and easy to use open source business process management (BPM) application. BPM software such as ProcessMaker can assist organizations of any size with designing, automating and deploying business processes or workflows of various kinds. Like SugarCRM, ProcessMaker is web-based, open source and can be run in the cloud or on-premise.

ProcessMaker SugarCRM Edition is a module designed to add a powerful visual BPMN 2.0 compliant Designer, a Business Rules Editor, and BPM/BRE Engines to SugarCRM. This product is based on our award winning ProcessMaker technology, and it has been re-built from the ground up as a native module to deliver the technology integration needed by SugarCRM enterprise customers. Thanks to this integrated module, enterprises can design custom, rules-based workflows inside SugarCRM, control how tasks are routed to different users, track how long tasks take to be completed and more. The results are better lead management, happier leads and higher conversion rates.

This is not your typical connector or poorly held together web services integration. Instead, we built a completely new version of our award winning ProcessMaker technology and we built it just for SugarCRM. This new product was designed from the ground up to be a native part of SugarCRM. We believe in the enormous worldwide community of SugarCRM, and we believed that it deserved a true process engine inside SugarCRM. And that is what we have built. See for yourself in these videos.

 

Video 1 – Creating A Process

first video

This video will get you started with ProcessMaker SugarCRM Edition. You will learn how to create your first process and the different component types of the designer and what they do.

Video 2 – Designing A Process

second video

In this video, you will learn how to piece a process together, how the components interact with each other and lay the foundations for your first working process.

Video 3 – Configuring A Process

third video

This video will take you through the fundamentals of process configuration. Inspecting each element in turn and setting the properties accordingly.

Video 4 – Executing A Process

forth video

In this video, you can see the final result of the previous videos. Here, we run the process from the end user perspective.

 

This has all the components of a world class workflow or bpm product. There is a BPMN 2.0 compliant designer (unbelieveable, right?), there is a workflow engine capable of running tens of thousands of cases a day, there is an inbox, forms builder, business rules engine, document management…the list goes on and on. But wait, the best is yet to come.

SugarCRM users won’t have to learn anything new. Everything is done natively in SugarCRM. Everything starts with the way the product loads. ProcessMaker SugarCRM Edition loads like a normal Sugar Module in just seconds. Then we add a few dashlets to our interface, and we are ready to begin working.

The form builder is the SugarCRM form builder. The email template builder is the SugarCRM template builder. The mail engine is the SugarCRM mail engine. The logical expression builder is the Sugar logic expression builder. That’s right – we took all the best of SugarCRM and we left it alone. It’s all native. And that means that you already know how to use this product.

 

The “My activities” dashlet in Sugar manages the tasks that have been assigned to a user through the ProcessMaker workflow engine and effectively replaces the ProcessMaker inbox in favor of the “My Activities” Sugar dashlet. This is the main feature of CRM workflow and ensures that the users can route cases from one user to another.

SugarCRM workflow can extract data from any sugar module and use it for the purposes of routing/assigning activities. SugarCRM workflow users who are familiar with ProcessMaker will be pleased to know that the use of variables in ProcessMaker can now be Sugar variables as well as ProcessMaker variables. Options are available to ProcessMaker designers when they need to select from a list of variables for the purpose of evaluation and assignment of conditions.

A great example of what can be achieved with CRM workflow is a high value lead qualification process. In this CRM workflow process, users can check the value of an opportunity after it has been converted from a lead and then apply a custom routing rule. If the Opportunity amount is greater than $10,000, the CRM workflow process will automatically generate a parallel thread to the VP of Finance who must add notes to update the opportunity.

 

ProcessMaker, BPM

[prisna-google-website-translator]

slide-processmaker3-coming-v3

 

PROCESSMAKER IS YOUR OPEN SOURCE BPM WORKFLOW SOFTWARE SOLUTION

ProcessMaker is a cost effective and easy to use open source business process management (BPM) or workflow software application. Workflow software such as ProcessMaker can assist organizations of any size with designing, automating and deploying business processes or workflows of various kinds.

ProcessMaker workflow software features an extensive toolbox which provides the ability to easily create digital forms and map out fully functioning workflows. The software is completely web based and accessed via any web browser, making it simple to manage and coordinate workflows throughout an entire organization – including user groups and departments. ProcessMaker workflow software can also interact with other applications and systems such as ERP, business intelligence, CRM and document management.

Subject matter experts and business analysts choose ProcessMaker as their workflow software solution because they can accomplish more and communicate with their technical teams more efficiently. System administrators select ProcessMaker as a workflow software solution because they don’t have to spend a lot of time programming, thanks to its intuitive point and click interface and end users prefer ProcessMaker because it is so easy to use.

ProcessMaker is extremely efficient, lightweight and has one of the lowest overheads of any workflow software in the industry. With the additional benefit of it being open source, ProcessMaker Enterprise clients can take advantage of a fully supported, high quality BPM suite. Customers on 5 continents, through 17 different languages and across a variety of industries including manufacturing, telecommunications, finance and government, healthcare and education are using ProcessMaker workflow software.

With business processes governing more complex relationships and interacting with many different business systems, companies need an easy way to manage and improve their processes. Several factors make it difficult to manage these processes in human resources, finance, compliance, and other business functions.

  • Paper-based processes and business system silos prevent information and approvals from passing across departments easily
  • Limited IT (internal or outsourced) resources burdened by complex system installations that require too much time and trouble-shooting and by an ongoing assault of help desk requests.
  • Difficult-to-define business problems. When different stakeholders have different views of a problem and the description and scope of the problem often changes, finding a solution through a traditional linear process may not be possible.

For workers in organizations that must process and manage a heavy workload of requests as part of their job, workflow software helps them handle those requests more efficiently and quickly.

  • Improved communication and resolution of requests with and from other departments and customers. Web-based, form-driven processes and graphical drag-and-drop workflow maps automate processes and radically reduce paperwork, so business users can easily and quickly complete their tasks.
  • IT staff can be used more efficiently. Simple deployment and development means that technology managers can quickly get the software up and running without spending a lot of time with complex and unreliable installations. Business managers can create and modify established workflows, so changes can be completed more quickly with minimal IT involvement.
  • Continuous improvement of business processes. Designed for an adaptive approach, where technology and business managers work together to target problem processes for improvement in the larger stream of business activities. Workflows automated with ProcessMaker become consistent, repeatable, and measurable, so processes can be continuously refined and adapted to new conditions.

Functional specification

Process Designers need features and tools that make it extremely simple to build and maintain business processes: Read more…

Clients

LINKS:

Functionalities  |  See Preview |  Community/Support   |  Success Stories |  Documentation  |  About Process Maker |  Webinars

 

IT Support Demo – Video

[prisna-google-website-translator]

IT Support Request

The IT support request process is designed to allow end users in an organization to submit a ticket to report technology problems to the IT department. Problems can range from a broken computer mouse to lack of server access. With ProcessMaker as the workflow solution to this process, tickets can be submitted and escalated as needed as well as recorded and logged for future reference.

Part 1

When a user has a problem that they need to report to the IT department, they launch a new case in ProcessMaker and select the IT Service Request process. The first Dynaform displayed will automatically fill in the information about the requesting user – such as the user’s name. Other data is also automatically entered and the user simply has to complete the form with the selection of a drop down and a free text box to describe the problem to the IT department. Finally, they can determine the level of urgency from another drop down box.

 

Part2

When a case is escalated to IT, the first level IT support engineer receives the case. If there is more than one first level support engineer, then each engineer will take turns receiving incoming cases in a ’round-robin’ fashion. The engineer will look over the notes submitted by the end user in read-only format and go ahead and try to resolve the issue – contacting the end user if necessary.

If the first level support engineer can resolve the issue himself, he will select a dropdown box to close the ticket which will assign the case back to the end user to verify that the issue is in fact resolved. If not, the case will be escalated to a second level support engineer.

Part3

The second level support engineer receives the IT support request case if the first level engineer is unable to resolve the issue. At this point in the process, the engineer is able to review all notes in read only format in order to see what has been done to resolve the issue so far. In the process we’ve created here, the second level support engineer is as high as the escalation can go so we will expect the issue to be resolve in some manner at this stage.

Once the second level support engineer resolves the issue, he closes off the ticket by using the drop down box selection and adds notes to record what was done. The ticket will now be passed back to the originating user who will verify that the case is now closed.

Part4

The last task of the process is for the originating user to verify and accept that their IT support request was resolved. They can review the notes on the case which were logged by the IT department and perform their own testing if necessary. If the issue is not resolved, the user can choose not to close the case, add more notes and send the case back to the IT department – which will cycle the case through the tasks again. If the issue is now resolved, then the user simply closes out the case with the drop down box and the case is officially closed and stored in the database.

 Back to Videos

Purchase Request Demo -Video

[prisna-google-website-translator]

Purchase Request Process

The purchase request process is used by organizations to place and track orders for supplies.  These could be anything from stationary to office furniture or more.  This process allows end users to place an order, receive supervisor approval and most importantly, allow external vendors or suppliers to submit prices for quotes without the need for them to be registered as ProcessMaker users.

To begin, the end user logs into ProcessMaker and begins a case in the purchase request process.  Some of the information about the user is automatically filled in.  However in the initial form there are two dependant fields shown – ‘Category’ and ‘Item’.  The Category drop down field is for the user to select the category of item they wish to request and the item drop down field will change its available options depending on the category chosen.  They select the item, quantity and give a brief description before the case moves for supervisor approval.

When the supervisor receives the case in the purchase request process, they can review all of the information submitted by the originating user.  The supervisor now simply selects whether this is approved or not.  If it is not approved, a comments box appears for them to enter a reason for the decision and the originator will be informed via email of this decision.  If the supervisor does give approval however, the case will move to the warehouse manager (Or inventory controller) for a quote request from the vendors.

In task 3, the warehouse manager can review the information and move forward for a quote request.  Here they can insert as many rows as they wish – 1 for each vendor.  They select which vendor they wish to receive quotes from and the information regarding their contact at that supplier is automatically filled in.  An email will be sent to each specified vendor asking for the price of the item in question.

This task is known as ‘External User Entry’.  Each vendor selected in the previous task receives an email with a link to a form.  The beauty of this is that the vendors have access to this form even though they are not ProcessMaker users.  Each vendor’s form is customized for them, featuring the name of the company and the details of the request.  The vendor simply reviews the request and enters a price with comments.  This form is 100% customizable, so it’s also possible to include more information about the item and even an upload button for the vendor to attach an official quote document.

The case is now residing with the originators manager, who has the final say on which item is purchased.  The manager can now see the information which was supplied by the external vendors and make an informed decision on which item to proceed with the purchase.  This form is designed so that only 1 item can be selected with the use of the check boxes.  The manager then confirms with a yes/no drop down to proceed with the purchase and enters any comments he or she feels is necessary.  At this point the order is placed manually, however ProcessMaker can also be programmed to send another email back to the chosen vendor to confirm a purchase and request an invoice.  In our demonstration process however, ProcessMaker will simply produce a purchasing document with the information about the item.

The final task is handled by the warehouse manager once again who waits to confirm reception of the goods requested.  The warehouse manager can review the purchasing document if he or she wishes with a click on a link provided in the form.  Once the item is received, the warehouse manager will confirm receipt with a drop down field and the case will come to an end.  This fantastic process allows organizations to track requests for items and guides them through the purchasing process from initial order all the way to item delivery and is simple and extremely effective.

Leave of Absence Demo -Video

[prisna-google-website-translator]

Leave of Absence Request

The leave of absence request process is designed so that employees of an organization can request vacation time, sick leave or business trip leave and receive approval quickly and efficiently.  Furthermore, this process can also be used to update human resource systems that keep track of paid sick or vacation leave.

Removing paper forms from the equation and also the supervisor or department head having to take time to sign off on paper and return it, the leave of absence request allows an employee to log in to ProcessMaker and simply begin a case in the leave of absence process.  Before presenting any information, ProcessMaker will verify that the user still has vacation time remaining against a database before displaying the request form to the user.  The user fills out the form with the help of dropdown menus, date pickers and text boxes and presses ‘submit’.  ProcessMaker will then perform a lookup against the submitting user to find out who is that employee’s supervisor and route the case accordingly.

The supervisor is notified of the leave of absence request via email.  All of the information about the user and the request is present in the email with the addition of two buttons labeled “Approve” and “Reject”.  These buttons make it possible for the supervisor to make a decision regarding this request directly from the email without even needing to log into ProcessMaker – perfect for supervisors who are travelling or on the go with their laptop or mobile device.  Once a decision has been made, the employee is instantly notified via email of the outcome of the supervisor’s decision.

The final two tasks of the leave of absence process are for the employee to return from their leave and confirm the number of days that they took reflect the number of days that they requested (The employee could have returned earlier than anticipated).   The supervisor then has the option to concur with this or send it back to the employee challenging the information submitted.  All comments between the two parties are consolidated into a comments history log for the duration of the process.

Once the supervisor is content that all of the information is correct, he will choose to “update the system” whereby ProcessMaker will deduct the number of vacation days taken from the database and produce a summary of how many vacation days the employee has remaining.

ProcessMaker Leave of Absence Request Process

Back to Videos