Bundle Templates Processes
General Overview
The bundle templates are used for the Trial Server. "Trial Documentation" This means when a new user creates a Trial Version of ProcessMaker, it is used these templates. We also use the bundle templates in the sales server and local sales server. Every sales rep has a PM workspace that has all the bundle templates configured, Dashboards, KPI's, and the enterprise plugins. All the mentioned servers should be upgraded every time that a new version of ProcessMaker is released. There is a difference between upgrading the trial server and others server. The trial server has amounts of workspaces. Therefore, Sales Engineering created a method to upgrade it. See documentation Here!
Templates for WEB
List of the templates we use as shown below. Most of the templates have its own documentation.
Processes
Operations
1. Supplier Registration - Review Document
2. IT Service Request - Review Document
3. Purchase Request - Review Document
Finance
1. Expense Report - Review Document
2. Invoice Approval - Review Document
HR
1. Leave of Absence - Review Document
2. Employee On-boarding
3. Employee Off-boarding Plugins
1. ProcessMakerBundle.tar (Used in the trial server and sales server)
2. Intercom Plugin (Used only in the trial server)
Features
1. Dashboards
2. KPI's
3. Data Reporting ToolNote: The trialbundle.tar template has been generated in PM v3.1. The trialbundle.tar file should be renamed to colosaTpl.tar in the trial server due to this name is hard coded in the plugins that use the trial server.
Steps to Restore the Web bundle templates
Find the bundle templates in a google folder Here!.
Find the details of every file in the google folder as follows;
1. The file trialbundle.tar is the template (ProcessMaker workspace backup),
2. The plugin.singleton is the configuration of that workspace. (The singleton file is different for the Trial server it has to enabled all enterprise plugins, this file you can find in the trial server. Ask to DevOps for accessing)
3. The ProcessMakerBundle.tar is the plugin that we use in the two process. Purchase Process and Leave of Absence Process.
Follow these below instructions to restore them. Go to your ProcessMaker installation folder and execute these commands;
1. Copy the files to your server
2. cp trialbundle.tar /opt/processmaker/shared/backups/
3. cd processmaker
4. ./processmaker workspace-restore -o trialbundle newWorkspace
5. cp plugin.singleton /opt/processmaker/shared/sites/newWorkspace/
Template for Mobile
The mobile template is used for the trial server. Below is shown in details:
Process
1. Material Ordering
Plugins
1. Intercom Plugin
Features
1. Dashboards
2. KPI's 3. Simple Report
4. SLA Report
Note: The mobileTpl.tar template has been generated in PM v3.0.1.8. However, the process works pretty well in the v3.1.
Steps to Restore the Mobile bundle templates
Find the Mobile bundle templates in a google folder Here!. This process is not documented yet.
Find the details of every file in the google folder as follows;
1. The file mobileTpl.tar is the template (ProcessMaker workspace backup),
2. The plugin.singleton is the configuration of that workspace.
Follow these below instructions to restore them. Go to your ProcessMaker installation folder and execute these commands;
1. Copy the files to your server
2. cp mobileTpl.tar /opt/processmaker/shared/backups/
3. cd processmaker
4. ./processmaker workspace-restore -o mobileTpl newWorkspace
5. cp plugin.singleton /opt/processmaker/shared/sites/newWorkspace/
@Jose Maldonado (Unlicensed) - just a reminder that as soon as Carlos is onboard and we are back up to speed in the SE group, we need to really have a look at our templates. In my opinion, we need 50 templates in our bundle. 50 templates is no more difficult than 10. The only thing that should change are a few field names and the process names and descriptions. That's all. The reason for 50 is simple. Look at this attack by kissflow. Here you can see that the number of templates shows up in the comparison table.
Here are some more thoughts for getting the templates built.
I know that JC and Rodney worked on this for nearly 6 months - not sure where it stands.
We wanted to make our bundle simple - meaning it should preferably not use any code or triggers. We need to keep our first impression simple. It is fine to have more complex examples as well, but those can be kept in a private repository or we can use those for the demos we do. For a customer trial that gets initiated by a customer in our enterprisetrial the experience has to be clean and simple.
If we need to use triggers, I asked @Juan Carlos Yujra and Rodney to make a list of all the triggers. Do we have that list? For example, in order to have a single header on your forms with a company logo, you need to use a trigger. We need a list of triggers like these so we can get them to engineering and ask them to build interfaces. We should have had this done a long time ago. This is low hanging fruit. We identify the places where the 10-20 most common triggers are used, and we have engineering build a plugin to provide interfaces for doing these common triggers. Then we show customers that THEY DO NOT NEED to code to do basic processes in processmaker.
Common header and footer - all process should look the same
ACCEPT REJECT HEADERS AND FOOTERS - all 50 processes should use the same footer for approve and reject. It looks much better this way. We can also standardize our templates like kissflow for APPROVE/REJECT/QUERY - if we want. There is no reason not to do this. Many of our partners already do it with ProcessMaker because it is a better approach. Yet, when I look at the way we build our SE demos, each one is different. Of course, some clients might ask for something different, but we need a standard approach.
Reports - We need to study Kissflow's standard reports and let's copy them. I am asking @Enrique Ponce de Leon and @Jose Maldonado (Unlicensed) to look at some reporting options including Klipfolio, MS PowerBI, and a couple others. There is no reason we can't use an external BI tool embedded in our Enterprise trial and start showing beautiful reports. We need to target getting this done in the next 60 days (we are speaking with a possible consultant who can actually create the reports).
thanks,