Capability to have an Active / Inactive flag for attributes like Transaction Class and others (configurable) to block users from selecting inactive or wrong name

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Financial lookups are system restricted and cannot be marked as inactive

Steps to Reproduce: 

1. Create Transaction Class, Investment Class, Company Class, etc... or other financial setup object  
2. No method to mark as inactive

Expected Results: Capability to mark financial classes as inactive.

Actual Results:  Not possible to mark financial classes as inactive.

Workaround: None. 

Environment

Release : 16.x 

Cause

DE67939 

Resolution

This will be handled as an enhancement through feature/story work. 

Targeted implementation for Release 16.2.0 

Additional Information

Implementation Comments:

1. Verified that Active flag is available in Company class, WIP Class, Investment Class and Transaction class. 
2. On creation of the class by Default Active flag is checked. 
3. User has ability to check and uncheck the active flag from properties page, list page or via xog. 
4. Once value is assigned and made inactive then the value is persisted in the lookup. 

Company Class:

1. When company class is inactive user will not be able to browse them in the lookup in rate matrix, companies and Entity. 

WIP Class:

1. When WIP class is inactive user will not be able to browse them in the lookup in rate matrix, Projects, NPIO's and Entity. 

Investment Class:

1. When Investment class is inactive user will not be able to browse them in the lookup in rate matrix, Projects, NPIOs and Entity. 

Transaction Class:

1. When transaction class is inactive user will not be able to browse them in the lookup in rate matrix, cost plan details, resource, setting transaction defaults, setting plan defaults. 
2. When user tries to xog in a resource with inactive transaction class throws exception. 
3. Lookup API for transaction class does not fetch inactive transaction class. 
4. User will be able to xog in cost plan details with inactive transaction class. 
5. Once resource is financially enabled, then inactivating transaction class persists the value in the transaction class, as resource is still financially enabled user can perform end to end transactions for that resource via xog or via posting timesheet and also when user tries to create a manual transaction then transaction class is auto populated.
6. User can perform wip adjustment, approve wip adjustment for that particular resource.