The Performance System Parameter option supports specific monthly build requirements. If Monthly Mode (1 = Enabled) is enabled, all changes approved during any day in the month are automatically pushed back to the first day of the current month. As a result, the Start Dates and Stop Dates for all membership changes are committed to ENTITY_RANGE_DETAILS as of the first of the month.
...
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
You can set the Monthly Mode setting in the Pending Approvals Details screen. To illustrate, consider an example where a client executes daily builds for 1/1/1980 through 1/31/1980 for the composite shown in the following figure. The builds for the composite determined that JKEnt3a, JKEnt3b, JKEnt3c, and JKEnt3d met the composite criteria with an Effective Date of 1/4/1980. Additionally, JKEnt74 and JKEnt79 met the criteria with Effective Dates of 1/7/1980 and 1/31/1980, respectively. However, because Monthly Mode is enabled, the Start Dates have been converted to 1/1/1980.
| Anchor | ||||
|---|---|---|---|---|
|
...
- In the Performance Composite Pending Approval Details screen, check the check box next to the entity.
- Click Approve at the top of the screen.
This commits the membership change into ENTITY_RANGE_DETAILS for the composite (JKACOM28) for the selected entity with the appropriate Start Date or End Date, which in this case is 3/25/2009. - If the change is not valid, click Reject to ensure the record is not committed.
...