...
Excerpt | ||||
---|---|---|---|---|
In NOAH 3 it was only possible to edit Actions within the same calendar day they were created. This has been changed in Noah 4 – By default Noah will allow Actions to be edited beyond the calendar day they were created. However this only applies to Noah 4 modules and there are two exceptions to this rule: 1. This feature can be disabled by the Business System. If this feature is disabled then the ‘EditOldActionsAllowed’ property of the ModuleAPI returns false. 2. The Action cannot be edited if it is referenced by another Action.
In the following two examples we will assume that the Action we are editing isn’t referenced by another Action and the Business System allows Actions to be edited beyond the current calendar day. Example 1) what happens in Noah 4 if an Action from the current calendar day is edited? Example 2) what will happen if an Action not belonging to the current calendar day is edited? Archived Actions cannot be edited themselves.
In the following example we will assume that either the Action we are editing is referenced by another Action and/or the Business System doesn’t allow Actions to be edited beyond the current calendar day. Example 3) what will happen if an attempt to edit the Action is made?
Code samples for working with Archived Actions Example 1) Get archived actionsIn this example we assume that we have an instantiated ModuleAPI object named myModuleAPI that is connected to Noah. The code in this sample will iterate over all actions for the selected patient and retrieve available archived actions.
Example 2) Update an action which result in an archived actionIn this example we assume that we have an instantiated ModuleAPI object named myModuleAPI that is connected to Noah. The code in this sample will iterate over all actions for the selected patient which belong to a Session that is different from today and modify the description for all actions.
|
...