Hot Deployment : Modifications Allowed in Hot Deployment

Modifications Allowed in Hot Deployment
You can make only certain changes during a hot deployment. Supported changes are listed in Table 43, Hot Deployment Supported Modifications. Supported modifications for In Memory and Berkeley DB object management are the same; for Cache OM they are more limited.
In some cases, you can work around a limitation. For example, you cannot hot deploy event modifications, so you can’t change which rule function is used for an event’s expiry action. However you can change the code of the rule function that is already specified.
 
Global Variables  When using the hot deployment feature to deploy a project, TIBCO BusinessEvents ignores any changes to global variables in the project.
*  Cache object management  When Cache object management is used, hot deployment is available only for rules and rule functions. For state machines, you can change an existing action or condition, but you can’t add anything (including changing an empty action to non-empty).
**  For state machine hot deployment  You can only hot deploy new state machines (and state machine components) that are associated with new concepts, that is, concepts added in the same hot deployment. Adding a state machine or state machine component that is associated with an existing concept modifies that concept, and concept modification is not allowed. Also see notes for Cache object management above.