On some investments, users have 2 options in the Status field, but on other investments there are more than 3 different options. Studio shows that the project object has the seeded 'Status' attribute defined to use the 'Investment Object State' lookup. This lookup has some values which are only available on edit mode of the project view. Does the Status field have a dependency with another attribute to define the available options?
Release: 16.2.1 and beyond.
The Project Status field uses the system-restricted lookup 'Investment Object State'. The 'Investment Object State' Lookup has six values defined: 'Approved', 'Cancelled', 'On Hold', 'Rejected', 'Resumed', 'Unapproved'.
The 'Investment Object State' lookup has 3 additional lookup values defined: 'Converted', 'Incomplete', and 'Submitted for Approval'. These lookup values are used for the Idea Object and only appear on Idea instance records.
There is logic built into the application that controls which values are available. This logic is based on the values in the Status field, the Progress Field, and the date fields in the Investment.
* For item 6 above, in 16.2.1 and greater, additional values were added to change from 'Resumed' status. Now you can change from 'Resumed' to 'Approved' or from 'Resumed' to 'On Hold'.
Note: In Studio, the administrator has the ability to define an 'Override Default' value for this attribute. Although this is possible, the 'Override Default' value will not be used for this attribute because this attribute employs the use of application rules to display selected lookup values based on other project conditions. Also, Be mindful of these rules when developing BPM Process definitions that attempt to update the Project Status or Idea Status attribute. If you attempt to set the Project Status attribute that violates the built-in logic your process step will generate an error.
Setting the Default for this field does not work due to the built-in logic and therefore if an Idea is converted to a Project, the Status field will not use the value set for the Default field, but will be automatically set based on the built-in logic described above when the project is created.
Refer to the attached document that provides a matrix of the possible combination of values based on the logic