The latest version of SAS 360 Match introduces the approval workflow for flights in a tier. This optional customer configuration requires that edits to a flight must be approved by a second user before any changes can be made active.
To enable this option, select Require Approval for a tier. When this option is selected, flights in the tier require approval by a second user before any changes can take effect.
When a flight is changed in a tier that requires approval, a draft of the flight is created. The edits are not applied to the live flight. Another user must review and approve the changes to the flight before the changes are applied to the live flight. Draft flights can be edited multiple times or discarded.
Any user who can edit flights can approve changes to a flight. However, the user who approves changes to a flight must be different from the user who made the edit. The last editor and the approver are recorded in the audit log for the flight.
Be aware of the following limitations when you enable this feature:
- Do not enable this feature if you are using the sales workflow with proposals and line items. The proposal conversion process is incompatible with use of approval workflow tiers.
- Screens for inline edits and multiedits are unavailable in flights that are assigned to a tier that requires approval.
- You cannot use the campaigns API to manage flights if any flight within the campaign is in a tier that uses workflow approval. The ability to use the campaigns API to manage flights has been deprecated. Instead, use the documented flight API instead. In a future update, SAS 360 Match will provide a time line for the removal of the deprecated APIs.
Contact SAS Technical Support to enable this option.
