Arama:

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

Credit Application Demo – Video

[prisna-google-website-translator]

Credit Application Process

Despite being a slightly complicated and arduous process, the Credit Application Process has been immensely simplified with the power of ProcessMaker. The beauty of this particular process is that it can be initiated by anybody applying for credit from a bank or credit company.

The bank or credit company creates a form that can be hosted on one of their internet pages of their website. Prospecting applicants can navigate to that page and begin the application process by completing the form in its entirety. Various drop downs, grids and other useful fields are featured on the form to make it as user friendly and simple as possible and as with all ProcessMaker forms, the form can be fully customized with colors and graphics for standardization.

When the applicant submits the form, they are emailed immediately to inform them that the application has been received and is being reviewed. It is here that the application is sent to two different recipients of the credit department – one of these people will verify the personal information of the applicant while the other will verify the financial information. Each of these users can only see the information relevant to their task for data security reasons.

Assuming that both users of the credit department successfully verify the information in their relevant tasks, the applicant is emailed again inviting them to attend an interview at the bank in order to answer further questions to support their application. That task also features a form where the interviewer can take notes and complete more information about the request. If this is successful, then the case is passed onto a senior member of the bank in order to have repayment information established and the terms of the credit.

Finally, a manager or supervisor reviews all of the information before the credit is granted to the applicant.

processmaker_credit_application_process_sm

Back to Videos

Expense Report Demo – Video

[prisna-google-website-translator]

movie_tape_icon_wordpress-2222px

Expense Report Process

The expense report process is a simple process that allows an employee to request a cash advance prior to traveling and then report actual expenses incurred once the employee returns from the trip.  If the employee does not require a cash advance then he simply would begin the process from the task of reporting actual expenses incurred.

Both the cash advance and the reported expenses are sent to an approval task where the employee’s manager must approve the request (Note: the employee’s manager is either defined in the ProcessMaker user tables or is pulled from an Active Directory server or LDAP server via our advanced LDAP/AD synch or Active Directory Single Sign On plug-in).  If the request is denied, it will be routed back to the employee to be fixed or changed with further clarification.

In this workflow if the employee has receipts to attach, the employee will be prompted to upload a scanned copy of the receipts.  These receipts are stored in the ProcessMaker Document Management System and associated with the expense filing.

Once the expense report has been approved, it is then routed to finance for either payment or collection.  If the employee requested an advance and did not spend the full amount advanced, then he will be responsible for returning the unspent funds.  If the company owes the employee money, then the company will indicate how the additional money will be reimbursed to the employee (either in a payroll check, cash, etc.)

This Expense Report process can easily be changed and modified to meet the specific needs of any given company.  We recognize that each company has different policies and procedures with respects to expenses and expense reimbursement.  This Expense Report Process has been designed according to known best practices and should work for most organizations with minimal changes.

Part 1

In this video, we look at the process map of this workflow and how it laid out in ProcessMaker.  We also identify the 2 starting tasks of the process.  The video also shows how an employee can log in and submit and expense report by completing a form and uploading copies of reciepts to back up their claim.

Part 2

In this video, we demonstrate how an expense report is passed to the correct supervisor upon submission by the employee.  All of the data submitted is displayed to the supervisor in read only mode with a section for the supervisor to either approve or reject the request and add their own comments regarding their decision.

Part 3

This video shows the end of the Expense Report Process.  The finance department are passed the request if the supervisor has approved it.  Like the supervisor, the finance department can view all of the originators data they submitted before selecting “Cash” or “Check” as the method of reimbursement.

Following this, ProcessMaker generates an output document which the finance team will print and ask the originator to sign as confirmation of receiving the reimbursement.

See preview Process Maker 3.0

[prisna-google-website-translator]

movie_tape_icon_wordpress-2222px

Introducing ProcessMaker 3.0

 

ProcessMaker BETA Version 3.0 will be available for download on July 22, 2014.

This promises to be the fastest, most powerful version of ProcessMaker ever released. We think you will be blown away by what you can now do with ProcessMaker.  Here is a summary of what’s new:

  1. A new HTML5 Form Designer with multi-column drag and drop designing that let’s users develop responsive UI forms which auto adjust to the size of a users screen (monitor, tablet, cellphone)
  2. A new jQuery BPMN 2.0 process designer with support for undo, redo, zoom, multi-object grab and drag, and much more
  3. Support for additional new BPMN 2.0 elements such as message and timer start events, and sub-process call activities, multiple artefacts, and more
  4. A powerful new RESTful API which will give developers full control over all functions in both the designer and the run-time engine and make it much easier to embed ProcessMaker in anytype of system or product

Download it on July 22nd!

LINKS:

ProcessMaker Workflow Designer
Dynaforms / Webforms
Output Document Builder
Web Services API Trigger Builder
Advanced Debugger
User Management
For ProcessMaker Users
Document Management
Videos

Community/Support   |  Success Stories |  Documentation  |  About Process Maker |  Webinars | Download v.3

For ProcessMaker Users

[prisna-google-website-translator]

Cases Inbox

The Cases Inbox feature is where the end user interaction takes place.  The layout has been designed to appear similar to an email client with a list of folders on the left of the screen seperating cases between an inbox, drafts, participated (or sent) as well as several other folder features unique to ProcessMaker.

A case in ProcessMaker is simply and actionable item or request that moves through the process from user to user and task to task.  It is comparable to what some might call a ticket, in that each has a unique identifying number, and will appear in a users Cases Inbox when it becomes assigned to a user.

Cases within the inbox can be sorted, filtered and searched through.  Users can also sort the case list in a variety of ways by clicking on a column header.  There is a large quantity of information available to the end user when they look at their Cases Inbox, such as who sent the case to them, the date that the case is due, the case priority, which process the case is being run through and which particular task within that process the case is currently pending on.

End users will interact with ProcessMaker from the Home area and the cases inbox module of ProcessMaker.  They typically do not have access to the designer or other areas of ProcessMaker and can sort, view and filter their cases inbox in their own preferred method.  To open a case and enter the information pertinent to the case, the user simply double clicks on a case within the inbox, whereupon the web form for that task will be displayed, ready for data entry.

 

LINKS:

ProcessMaker Workflow Designer
Dynaforms / Webforms
Output Document Builder
Web Services API Trigger Builder
Advanced Debugger
User Management
For ProcessMaker Users
Document Management
Videos

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