Operation is where the activities/tasks you have in your organization that you want your end users to fill out. This is beneficial as it allows organizations to digitize their activities/tasks.
Operation is used to attach forms of all your activities in your organizations.
This is where your activities/forms are attached and activated. When there is an active instance of an Operation it will have a pink background on the operation name.
Just click on the three dotted menu on the Work Area and select Add Operation.
- Complete when all children complete - It can have a “Parent-Child” Operation, meaning that one Operation would be the main and the other one the sub operation. What this does is that when a certain condition in the main operation is triggered then the sub operation would be active.
- Expire Children when expired - To expire all the sub (child) operations once the main(parent) operation has expired.
- Manual Trigger - You can have it manually triggered once enabled
- Expire - Set expiry for the Operation
- Operation Mode - this is for if the operation allows for multiple active instance all at the same time or if this operation is only good for one-time instance
Form Settings are a powerful feature that allow local set-up and configuration of a form to occur.
When developing forms for your Operations, you may tend to have the same sort of form used over and over again, with only slight differences.
A good example of this is a Checklist, where users need to verify something is done or not. So the response will always be Yes or No. If No, then perhaps some actions or reasons why and an image to support. Then you have the Checklist criteria, that will change from form to form. But, the remainder of the form is the same. Any you may have this type of thing used over and over many times. So, dont develop many many forms over and over again! Make one form, once and use the Settings to add your Checklist Criteria, in each Operation.
If you have added a settings container in the form when making it in in the form builder, then you can adjust the form settings in this tab.
Schedules are used to trigger Operations automatically, according to timeframes that have been set up in the Scheduler.
Operations will be triggered at the Schedule Start, and Expire at the Schedule End, automatically.
Users are expected to interact with the Operation by submitting data within the Schedule. Once the required data has been submitted, within the Schedule range, the Operation is complete.
You need to have Schedules already set up to assign them to an Operation.
After you have made your schedule, you can assign it to the Operation in this tab. Simply look for the schedule name you need. More than one Schedule can be assigned to an Operation. For example you may have:
- AM Schedule (say 6am till 11am)
- PM Schedule (say 3pm till 11pm)
You may assign both these Schedules to the same Operation. Once you have added your Schedule, select Save.
Performance Reporting is heavily related to Schedules, as follow:
- Operation is In Progress: blue
- Operations completed within Schedule: Complete 100% and green
- Operations not completed within Schedule: Expired 0% and red
Please refer to the Performance Reporting for more details.
Presets allow you to save field inputs to an Operation that is accessed by a special link. Presets are a very powerful feature that enables a “frictionless” action to occur. Submit-on-load triggers the Operation submission as soon as the link is loaded.
This combination means that data can be submitted by loading the Preset special link. Links can be exported as a url or QR Code for print and mobile scanning.
From Admin, the Export Operations are Presets. If no Presets are saved for an Operation, then the normal Operation link is exported.
End-Users cannot Export Operations with Presets, this can only be done by the Admin.
Links can also easily be written onto nfc tags. This produces a true frictionless approach to submitting an Operation. Users simply tap the tag with a mobile phone, and the Operation with its corresponding Preset data is submitted in the same action.
Enabled Submit-on-load: the Operation is submitted with corresponding data, once the tag is tapped.
Disabled Submit-on-load: the Operation form is loaded, with the Preset data pre-populated. The user then completes the remaining inputs and submits like normal.
Use Case: Safety alerts
Set up an Operation that is used to alert the team of a safety incident: Presets may include location, current time, geo-stamp, users, zone, and severity type of hazard. Actions include emails, sms and action plan. This data is all saved as a Preset, and Submit-on-load is enabled. The link is written onto a QR Code or NFC tag, and physically located on-site.
In the event of a safety, a user can simply tap or scan the QR and get an instant verification that the issue has been reported.
All without any typing, calling, finding a computer … all from their mobile in seconds!!
There are many many use cases where Presets serve to facilitate data being submitted for further action, totally frictionless. We think that’s pretty cool.
Presets do not interfere with a normal / native Operation that is accessed from a Work Area. Operations continue as normal whether or not Presets are saved.
In this tab you can preview how your form looks and behaves in the Operation, after form Settings have been applied and saved. Preview renders the End-User view.