Approval Not Needed

Introduction

The ‘Approval Not Needed’ enables Authors and Process Owners to make a conscious decision to select 'Approval Not Needed' instead of leaving the field blank. Library Administrators and Approvers will have clearer status visibility in the web based Approval screen. Maps with Approval Status' of 'Approved', 'Rework' or 'Approval Not Needed' will not be included in the list of Unapproved Maps (or receive subsequent approval and overdue e-mail alerts). 
 
 

How to add new options to Approval Status in Node properties

The ‘Approver Not Needed’ option can be typed directly into the properties Approval Status text field. Alternatively, users can edit the Properties.xml file so that it will be available in the Approval Status drop down list as shown in the image below:

To add ‘Approval Not Needed’ open your customised Properties.xml file.

Go to Approval section; add a new row value called ‘Approval Not Needed’ (shown in blue below):

<group groupName="Approval" groupCaption="Approval">

<row rowName="tr_complianceapprovalstatus" rowCaption="Compliance Approval Status" rowType="3" rowVisioDataType="0">

                <rowValue>New</rowValue>

                <rowValue>Modified</rowValue>

                <rowValue>Approved</rowValue>

                <rowValue>Rework</rowValue>

                <rowValue>Approval Not Needed</rowValue>

</row>

<row rowName="complianceapprover" rowCaption="Compliance Approver" rowType="3" rowVisioDataType="0"/>

<row rowName="complianceapprovaldate" rowCaption="Compliance Approval Date" rowType="5" rowVisioDataType="5"/>

<row rowName="tr_complianceapprovalstatus_reason" rowCaption="Compliance reason for rework" rowType="0" rowVisioDataType="0"/>

 


The above amendment should be done for all Approval types created for each site and for each separate properties.xml files, for example where there are separate property files for each library. 

 
Below is a table showing various Node properties selection results which displays when the strapline is visible on the process maps. 

Content Approver

map status

Compliance Approver

map status

Strapline visible (Yes\No)

New

New

Yes

Approver not needed

Approver not needed

No

Approver not needed

New

Yes

New

Approver not needed

Yes

Approved

Approved

No

New

Blank

Yes

Blank

Blank

No

Approver not needed

Blank

No

Blank

Approver not needed

No

Approved

Approver not needed

No

Approver not needed

Approved

No


Rework and Modified status are temporary states which change to either Approved or Approver Not Needed.

Note: To view any changes that may have been made to process maps within your libraries, at least one publication cycle is required after the creation of each new Approval, Rework or Modified process cycle.
SelectionFile type iconFile nameDescriptionSizeRevisionTimeUser
Comments