Manual processmaker 2.0

For instance if there are three users named "Sally", "Jane", and "Anne" assigned to a task, then the users will be designated to work on cases in the following manner:. ProcessMaker cycles through the pool of available users, assigning each one of them in order, until it has run through the entire pool of users, then it starts the cycle over.

This option should assure that all the users get assigned to an equal number of cases, However, ProcessMaker makes no attempt to check the workload of a particular user or how many cases that user has pending. If a user is out of the office or has hundreds of uncompleted cases, ProcessMaker will continue assigning cases to that user. Note: Users who have been set as "On Vacation" have the ability to be assigned to tasks.

Nevertheless, they won't be assigned to running cases until they log in again in this type of assignment. With manual assignment, the user who completes the previous task in the process will manually select the user to work on the next task in the process. After completing the previous task, the user will be presented with a list of all the assigned users to the next task and will be asked to chose one to work on the next task.

Value Based Assignment allows a variable to specify which user will be given authority to work on a task. The variable can be set in the Variable for Value Based Assignment textbox which appears when the option is selected. A custom variable could also be used. For instance, if you want different users to handle a task, depending upon the amount of money involved in the case, you could define a custom variable NextUser to enter in the Variable for Value Based Assignment field.

Value Based Assignment can be useful if the same user needs to work on a task repeatedly. For example, imagine a process contains a task where an employee fills out a report. If that report is sent back to the same task for revision, the same employee who initially filled out the report should be assigned to the task again. All subsequent times, the task will still be assigned to the same user.

Here is the trigger code which would be fired before task assignment:. If the next user to work on the task needs to be randomly assigned from the pool of assigned users, then the following trigger code could be used instead:. The Reports To assignment rule takes into account your organization's structure organigram as represented by ProcessMaker Departments. If a supervisor for a sub-department completes the previous task, then Reports To will select the supervisor in the parent department to work on the current task.

In this way, tasks can be passed up the chain of command in an organization. The Reports To assignment rule is useful when a task can be worked on by a large pool of supervisors. For example, a complex organization wants to use the Expense Report Process , but that organization has employees from 10 different departments who can report the expenses that they incurred on the job.

The problem is there are employees who are assigned to the "Report Expenses" task and 10 different supervisors assigned to the "Approve Report" task. The supervisor of the employee who initially reports the expense should be the person who reviews it and decides whether to approve or disapprove the expense. Once the organizational structure is defined, then click on the [Edit] link for each department and click on Assign users to select the users who will be members of that department.

According to previous explanation, if in a derivation, the top level of a department has been reached, it means if the supervisor doesn't have another "supervisor" to report the case, reports to assignment rule will be applied assigning the next task to the same user. This validation was added from version 2. A Self Service assignment rule allows any user from the pool of assigned users to grab the case and work on the task.

Self Service can be used to reduce congestion in the workflow, especially when the users can best judge their capacity to take on new cases. When a case is routed to a task with a Self Service assignment rule, then the status of the case will be listed as "Unassigned":. The case will then appear in the "Unassigned" list of cases for all the users who have been assigned to the task.

Any user in the pool of assigned users can examine the case by clicking on View to see the details of the case. The case will then be moved to the Inbox of that user to be worked on and will disappear from the Unassigned list for all other users in the pool of assigned users. The Credit Card Application process is a good example of how Self Service assignment can be effectively used.

Normally, the "Data Base Update" task is handled by Cyclical assignment, but Self Service assignment is more efficient and productive, because any of the assigned users who is currently working can then enter the credit card application into the database.

This avoids untimely delays, because it is no longer necessary to wait until a particular employee comes to work. Furthermore, the employees at work can best judge whether they are free to handle the "Data Base Update" task at any particular time.

Available Version: From 2. As it is explained before, when a case use Self Service assignment rule, any user from the pool who is assigned in the task with this rule defined could claim the case, on previous versions if nobody claims the case it will remain on the unassigned folder forgotten by users or even users may not know that they have a case to claim.

To avoid this conflict, a time limit was added, which allows users the possibility to configure time the case will be remain on the unassigned folder, if that time is surpassed, a Trigger will be executed automatically, for instance that trigger could send a notification which would indicate there is a case to claim, it could derive the case, etc.

The trigger will execute while the case remains in the unassigned folder; configure the trigger if it requires to be executed only once. When Self Service option is chosen inside Assignment Rules a new option will be enabled:. Back in the "Create Task" dialog box, go to the Actions tab and click on the New button. For the Action dropdown box, select "Start a program". Next create a second action to backup the MySQL databases.

It is not recommended to use data from one version of ProcessMaker with a different version of ProcessMaker. Reinstall the same version of ProcessMaker, which you were using previously. If you want to use upgrade ProcessMaker to a newer version, first install the old version of ProcessMaker and then restore the data from your workspaces in the old version. Then, upgrade ProcessMaker to the newer version. To restore the files in ProcessMaker's shared directory, simply delete the existing files and then decompress the backup file in its place.

If restoring to a different installation of MySQL it is necessary to recreate the 3 MySQL users for the 3 databases for each workspace and give them permissions to access their databases. If a backup was made of the mysql database, this can easily be done:. However, this will overwrite the existing configuration and users of the MySQL installation.

Then use 7-zip or WinRAR to decompress the backuped archive into its place. All rights reserved. Version: 3.

Please rate how useful you found this document:. Select rating Give 2. X into 2. X Importing Workspaces into newer versions of 2. Download our app. Contact us. Watch Now. Go Paperless Digitize your paper forms and requests for use in your daily business processes. Streamline Compliance Improve workflow agility for compliance control, policy management effectiveness, and risk management transparency. Great conversations start with ProcessMaker.

Trouble Scheduling a Demo? Let us know how we can help. Privacy Update. Before version 2. From version 2. Note 2: If any programs such as Skype use port 80, either reconfigure the program to use a different port or leave it running on during the ProcessMaker installation, so that the ProcessMaker installer will choose a different port.

Find out which ports are being used with the DOS command: netstat -anb. If you want to use 64 bit versions, then do a manual install. Download ProcessMaker X -Setup.

Beta versions of ProcessMaker have the word beta appended to the version number. To download a recent version of ProcessMaker, go to the Releases folder and look for the highest version numbers. Look for the version to be installed inside each folder.

After downloading the installer, double click it to begin the installation. First, select which language to use in the installation wizard. To install in a new directory, click on Make New Folder to create a folder and give it a name, such as ProcessMaker. Next, decide whether to select the option for Enable heartbeat. The " Heartbeat " is used to collect anonymous statistics every seven days about the number of workspaces, users and processes being used.