ABOUT THE RELEASE NOTES
The release notes provide information about new major RiMANGGIS features and major enhancements to existing features.The release notes include:
- Brief, high-level descriptions of the functionality
- Setup information
The release notes also identify all other changes and provide details about how those changes might affect your organisation.
FEATURE SUMMARY AND USER IMPACT
The new version of 14th August 2015 has added automation function to improve users’ experience.
This release note describes the new features available in this release.
The concept of automation is to help users to send a series of automated campaigns base on trigger conditions. Users can set segment conditions to specify automation recipients, and then users can set a trigger condition, trigger schedule and execution period. Based on users’ trigger settings, RiMANGGIS will automatically send trigger campaigns to specified recipients who match the trigger condition according to trigger schedule in automation execution period.
The automation workflow includes three steps: Trigger->Campaign->Confirmation
Trigger setting step
Trigger setting step is used to set automation flow basic information:
- Automation name: set automation name to recognize different automation flows.
- Recipients: set segment condition to specify automation recipients.
- Action options: set a trigger condition to check recipients’ date property value.RiMANGGIS will send the first campaign to recipients of which property match thetrigger condition.
- Automation start and end time: set a date range to specify the automation executionperiod.
- Schedule: set the trigger campaign execution schedule(daily/weekly/monthly).RiMANGGIS execution automation campaign according to the schedule.
Campaign setting step
Campaign setting step is used to add and edit campaign, and set each subsequent campaign sending condition and schedule. At the scheduled automation time, the first campaign is sent to recipients immediately as long as recipients match the trigger condition. However, the subsequent campaign is merely sent to recipients whose previous campaign behavior matches the campaign sending condition according to each campaign-sending schedule.
An automation flow can include at most 5 campaigns, and the content of each campaign is edited independently.
Automation privilege confirmation step
Campaign confirmation step is used to confirm the completeness of automation settings and included campaign information.
A complete automation should have all prepared trigger setting information and complete campaign content, otherwise the automation can not be executed.
Automation privilege
Automation is an independent functional unit, its privilege is separated from campaign. Only users assigned with automation privilege can make related authorized operations.