Configure approvals

Approvals are available for Projects, Products and Subjects. Responsible stakeholders can sign off their area of responsibility. This article explains how to configure approval types, user roles or team roles, and the dialogs for Approvals.

Target groups

• Solution developers

Context

Approvals can be configured for projects, marketing plans, tactics, campaigns, products and subjects.

Prerequisites

Approvals are only available with the censhare Dedicated solutions.

Introduction

The censhare Standard workspace provides a preconfigured Approval feature. You can use Approvals in project assets of the type Project, Campaign, Tactic, Marketing plan, in Subject type assets. Approval allows the responsible stakeholders to sign off their area of responsibility independently. The Approvals tab of the respective assets shows the current status, history, and the dialog elements of approvals.

To use Approvals in your system, you must assign an approval type for projects, products, or subjects. You can assign multiple approval types to one asset type. Approvals can be restricted to asset types, user roles, and team roles. If needed, you can add custom approval types.

By default, Approvals do not restrict the approval actions. If required, you can customize the approval dialogs in the workspace configuration of the respective user roles.

Data model

Approvals are stored and controlled with a structure of hierarchical Features and the respective Feature items:

(1) The Approval history feature can store multiple Approval type child feature values. Each value represents an approval action.

(2) The Approval type feature stores the type of approval value and the respective child feature values. Multiple values are allowed.

(3) The Approval status child feature is set by any approval action that a user performs. The Approval date, Approval person and Approval asset version child feature values are set automatically. The Approval comment child feature is optional for each approval action.

(4) The Approval type feature items represent the areas of responsibility and can be enabled individually for each asset type. Custom types can be added.

(5) The Approval status values are stored in a value list in the Approval status feature.

In the Standard workspace, the Approvals tab (resource key: censhare:workspace.container.approvals) is configured for Project, Campaign, Tactic, Marketing plan, Product and Subject asset pages. The tab contains the Approvals actions widget and the Approvals history widget configurations.

Approval history

The Approval history feature stores the values of the approval type child features. Each approval type and each approval action create a new Approval history value.

The child features store the following details that display in the Approvals history table:

• Approval date: Timestamp of an approval action. Values are generated automatically.

• Approval status: User selected value from the approval status value list.

• Approval type: The available approval type must be configured for each asset type. See Configure Approval types section below.

• Approval person: The user that performs an approval action. Values are generated automatically.

• Approval asset version: Each approval action creates a new asset version. Values are generated automatically.

• Approval comment: Stores user-generated comments to each action.

Key steps

1. Configure Approval types

2. Configure Approval type settings

3. Customize approval dialogs

Approval types

The Approval type feature is configured as dynamic value list. Initially, the dynamic value list is empty, and no approval type is configured.

Approval types are stored as Feature item assets that are assign to the Approval type feature. Available approval types must be configured in the Approval type feature. The following approval types are available in the censhare Standard workspace:

The desired Feature items must be assigned to the Approval type feature. In the Feature item, you can define a user role and a team role filter for the respective approval type.

To add an approval type, proceed as follows:

1. In censhare Web, search for the Approval type feature (resource key: censhare:feature.approval.type) and open it in an asset page.

2. In the Child feature items widget, click .

3. In the Add top-level asset dialog, filter the results for Approval type*.

4. Select the desired Approval type: ... feature items.

5. To save your changes and close the dialog, click OK.

The selected Approval types display in the Child feature items widget.

Approval type settings

For each approval type, you can define user roles, team roles, and asset type filters. Proceed as follows:

1. To open the desired Approval type: ... feature item, double-click it in the Child feature items widget of the Approval type feature.

2. In the Feature item properties widget, click

   

   .

3. In the Configuration area, select the desired roles and filters:

   • Role: Select a user role. The approval is only shown to users that work with the respective role in their domain. You can select multiple items.

   • Team role: Select a team role that a user must have to perform this approval. You can select only one item.

     Note: If a team role is assigned to a user, the user role is overruled. Team roles are not applicable to Products.

   • Asset type filter: Enter the ID of the asset type for which this Approval is applicable ( for example: project.). For multiple asset types, click below the input field  to add a new field. Enter only one asset ID per field!

     Note: By default, approvals are configured for the asset types marketing-plan., project., project., campaign., project.tactic., product. and subject. - if you enter other asset type filters, the Approval becomes unavailable.

4. To close the dialog, click OK.

5. Repeat the previous steps for each Approval type.

Approval dialogs

By default, any user can start, ignore, or delete all approvals that are configured for an asset type. We recommend disabling the Edit dialog for user roles that are not allowed to sign off approvals.

In the Approvals actions widget, users can change the Approval status of and asset. The status of an Approvals are configured in a value list of the Approval status feature (ID: censhare:approval.status). The following values are configured:

Users with the respective user roles, or users that are assigned in the respective team role, can start, approve, or reject their approvals directly in the Approvals actions widget. In the Edit dialog of the Approvals actions widget, users can start, delete, and ignore Approvals. You can customize the widget dialog of the Approvals actions widget for different workspaces/user roles.

Users can comment on each Approval action in a context dialog. If you do not require this option, you can disable the comments dialog for the respective steps.

The dialog customization is done in the workspace configuration of the censhare Dedicated solutions. For each custom configuration, add a resource replace variant of the respective Module asset. The following graphic shows the asset structure in the workspace configuration:

(1) Approvals are configured in an asset workspace page.

(2) The Approval tab is configured in a generic workspace container.

(3) The Approvals actions are configured in a Properties widget.

(4) The Dialog asset stores the HTML configuration of the Approvals actions widget.

(5) The Script asset renders the approval data and user interface controls of the Approvals actions widget.

(6) The Approval history is configured in a Report widget.

(7) The Transformation widget stores the XSLT of the report widget.

To add a custom configuration, proceed as follows:

1. In censhare Web, search for the Approvals Display Dialog Controller Script asset (resource key: censhare:metadata.approval.display.dialog.controller).

2. Click the three dots to open the Page actions menu, and select Variants ► Resource replace variant. The asset variant displays in the Resource replace variants widget.

3. Move the cursor over the entry, click the three dots, and select

   

    Edit relation properties.

4. In the dialog, select a Resource replace role. To add more roles, click . If the logged-in user has the respective role, the Resource replace variant is used instead of the default script.

5. To save your changes and close the dialog, click OK.

6. Open the Resource replace variant in an asset page.

7. Go to the Editor tab.

8. Edit the script according to your requirements. For details, see the User interface controls section below.

9. Click SAVE.

10. To add another configuration, repeat the previous steps.

User interface controls

In the Approvals Display Dialog controller script, search the following snippet and edit it as described in the table below:

$scope.approvalStatusConfig = {
	none: 	   {value:'none',
		   		display_value:'None',
		   		buttonLabel:'',
		   		enabled:true,
		   		addComment:true,
		  		createTask:false},
	start: 	   {value:'started',
				display_value:'Started',
				buttonLabel:'Start approval',
				enabled:true,
				addComment:true,
				createTask:false},
	approve:   {value:'approved',
				display_value:'Approved',
				buttonLabel:'Approve',
				enabled:true,
				addComment:true,
				createTask:false},
	reject:	   {value:'rejected',
				display_value:'Rejected',
				buttonLabel:'Reject',
				enabled:true,
				addComment:true,
				createTask:false},
	delete:    {value:'deleted',
				display_value:'Deleted',
				buttonLabel:'Delete',
				enabled:false,
				addComment:true,
				createTask:false},
	ignore:    {value:'ignored',
				display_value:'Ignored',
				buttonLabel:'Ignore',
				enabled:false,
				addComment:true,
				createTask:false}
};

Notes:

(1) Disabling the approval status none has no effect. If you disable the start status, the approval is started automatically, and the Approve/Reject buttons display at the start. If you disable the delete status, approvals cannot be reset.

(2) If you change the configuration, always test if the Approvals controls work as expected.

Result

The appropriate approvals are available to the users in their workspace. Users can perform the appropriate actions in the Approvals actions widget.