On the Conditions tab, click Add. Click OK. Click OK. Click OK. Click OK.

3-52 Application Administrators Guide for Content Server

g. On the Conditions tab, click Add.

h. Enter the name of the field condition for example, PositionAppliedFor.

i. Click OK.

j. In the lower Value field, enter an appropriate statement for example, Please specify the position title.

k. Click OK.

l. Click OK.

m. Click OK.

3.2.7.2.3 Create the Black-Hole Check In Profile for Resumes To create the black-hole

checkin profile: 1. Open the Profile tab on the Configuration Manager Application Page and click Select . The Add Profile Screen is displayed.

2. Select Type from the Field Name drip down option list.

3. Click OK.

4. Click Add on the Profiles tab.

The Add Profile Screen is displayed. 5. Enter the name of the profile for example, BlackHoleResumeCheckIn.

6. Click OK.

The AddEdit Profile Screen is displayed. 7. Enter the profile description in the Description field for example, For internal user resumes only.

8. Select HRresumes or the equivalent option from the Trigger option list.

9. Click Add to include the rules in this profile.

The Add Rule Screen is displayed.

10. Select the NoExtraFields rule from the Name option list.

11. Select a general priority placement from the Rule Priority option list.

12. Click OK.

13. Click Add.

14. Select the VisibleFields rule from the Name option list.

15. Select a general priority placement from the Rule Priority option list.

16. Click OK.

17. Click OK.

The Add Profile screen closes and the profile is added to the list of profiles on the Profiles tab.

3.2.7.3 Global Rule to Restrict Content Check-In Based on User Role

This example shows how to create a global rule that can validate metadata fields when users check in content. The global rule validates the data in a request, and returns an Managing Metadata 3-53 error message if the data is incorrect. Specifically, this example shows how to allow only an administrator to check in content that specifies ADACCT as the Content Type.

3.2.7.3.1 Enable Content Server to Issue a Fatal Error Upon a Global Rule Violation

1. In a text editor, open the config.cfg file: IntradocDirconfigconfig.cfg 2. Add the following configuration setting: IsDpSubmitErrorFatal=true 3. Close and save the file. 4. Restart the Content Server.

3.2.7.3.2 Create a Global Rule to Restrict Content Type Check-Ins This global rule validates

the value for dDocType and ensures that an administrator is checking in an ADACCT document. However, the rule is configured to affect only the Check In and Update pages. 1. Open the Rules tab on the Configuration Manager Application Page , and click Add . The AddEdit Rule Screens is displayed. 2. On the General tab, enter the name of the global rule in the Name field for example, FailOnCheckInError. 3. Optionally, enter a description for the global rule.

4. Select the Is global rule with priority check box. You can optionally change the

priority number.

5. Select the Use rule activation condition check box and click the corresponding

Edit button. The Edit Activation Condition Screen Tabs is displayed.

6. Click Add.

The Edit Activation Condition: Add Condition Screen is displayed. 7. Enter the name of the condition in the Name field for example, CheckIn.

8. Click OK.

The Add Condition screen closes and the General Tab is displayed. The clause-generating tabs display on the lower pane.

9. Select the Use event check box.

10. Select the On Submit check box.

11. Select the Use action check box.

12. Select the Check in new, Check in selected, and Content update check boxes.

13. Click OK.

The Edit Activation Condition screen closes and the activation condition clause is entered into the Use rule activation condition text pane.

14. Click the Fields tab.

The AddEdit Rule Field ’name’ Screen is displayed. 3-54 Application Administrators Guide for Content Server

15. Click Add.

The Add Rule Field Screen is displayed.

16. Select Type from the Field Name list.

17. Optionally, select a general position form the Field Position list.

18. Click OK.

The AddEdit Rule Field ’name’ Screen is displayed.

19. Select the Is derived field check box and click the corresponding Edit button.

The Edit Derived Value: Conditions Tab is displayed.

20. Click the Custom tab.

The Edit Derived Value: Custom Tab is displayed.

21. Select the Custom check box and enter the following Idoc Script:

if dDocType like ADACCT and not userHasRoleadmin abortToErrorPageOnly administrators can use ADACCT. endif

22. Click OK.

23. Click OK.

24. Click OK.

The rule is added to the list of Rules.

3.2.7.4 Global Rule to Restrict Content Type Metadata Changes

This example shows how to create a global rule that can validate metadata fields when users check in content. The global rule validates the data in a request, and returns an error message if the data is incorrect. Specifically, this example shows how to allow only an administrator to change the content type of a checked-in document.

3.2.7.4.1 Enable Content Server to Issue a Fatal Error Upon a Global Rule Violation

1. In a text editor, open the config.cfg file: IntradocDirconfigconfig.cfg 2. Ensure that you set this configuration earlier: IsDpSubmitErrorFatal=true 3. Close and save the file. 4. Restart the Content Server.

3.2.7.4.2 Create a Global Rule to Restrict Content Type Changes This global rule validates

the value for dDocType and ensures that an administrator is changing the content type of a checked-in document. However, it is configured to affect only the Check In page. 1. Open the Rules tab on the Configuration Manager Application Page and click Add . The AddEdit Rule Screens is displayed. 2. On the General tab, enter the name of the global rule in the Name field for example, FailOnCheckInError. 3. Optionally, enter a description for the global rule. Managing Metadata 3-55

4. Select the Is global rule with priority check box. You can optionally change the

priority number.

5. Select the Use rule activation condition check box and click the corresponding

Edit button. The Edit Activation Condition Screen Tabs is displayed.

6. Click Add.

The Edit Activation Condition: Add Condition Screen is displayed. 7. Enter the name of the condition in the Name field for example, CheckIn.

8. Click OK.

The Add Condition screen closes and the Edit Activation Condition is displayed. The clause-generating tabs display on the lower pane.

9. Select the Use event check box.

10. Select the On Submit check box.

11. Select the Use action check box.

12. Select the Content update check box.

13. Click OK.

The Edit Activation Condition screen closes and the activation condition clause is entered into the Use rule activation condition text pane.

14. Click the Fields tab.

The Fields Tab is displayed.

15. Click Add.

The Add Rule Field Screen is displayed.

16. Select Type from the Field Name list.

17. Optionally, select a general position form the Field Position list.

18. Click OK.

The AddEdit Rule Field ’name’ Screen is displayed.

19. Select the Is derived field check box and click the corresponding Edit button.

The Edit Derived Value: Conditions Tab is displayed.

20. Click the Custom tab.

The Edit Derived Value: Custom Tab is displayed.

21. Select the Custom check box and enter the following Idoc Script:

oldType = getValueDOC_INFO, dDocType newType = getValuelocal, dDocType if not newType like oldType and not userHasRoleadmin abortToErrorPageOnly administrators can change dDocType. endif

22. Click OK.

23. Click OK.

24. Click OK.

The rule is added to the list of Rules. 3-56 Application Administrators Guide for Content Server 4 Managing Workflows 4-1 4 Managing Workflows This chapter provides task information as well as conceptual and reference information for using the workflow functionality available with Content Server. This chapter contains the following topics: ■ Introduction to Workflows on page 4-1