Changing an object's attributes can break processes. If you add, remove, reorder, or modify attributes, any process that reads from or writes to that object may fail or produce incorrect results.
Before making any structural change to an object, you must identify every process that depends on it.
Why This Matters
Processes expect a specific column order, a defined list of attributes, and a consistent structure. If the object changes and the process logic workbook is not updated to match, the process may fail during execution, write data to the wrong columns, or read incorrect values.
Every structural change requires a dependency review before it is applied.
Step 1 - Identify Process Inputs
Open the Configuration application and navigate to Process Configuration \> Process Inputs.
Open the filter panel and filter by Object Specification = the object you plan to change.
Record the names of all processes listed as inputs.
These are processes that read data from the object.
Step 2 - Identify Process Outputs
Navigate to Process Configuration \> Process Outputs.
Filter by Object Specification = the object you plan to change.
Record all processes listed as outputs.
These are processes that write data to the object. They must be updated if the object structure changes.
Step 3 - Identify Process Deletions
Navigate to Process Configuration \> Process Deletions.
Filter by Object Specification = the object you plan to change.
Record all processes that delete records from the object.
Deletion logic may also depend on the object's structure.
Step 4 - Review and Update Process Logic Workbooks
For each process identified in steps 1-3:
open the process logic workbook
review column mappings and formulas
update any references to attributes being added, removed, or reordered
remove references to deleted attributes
add references to new attributes where required
The workbook must produce data that matches the updated object structure before the object change is applied.
Step 5 - Apply the Object Changes
Only after all dependent processes have been identified, their workbooks updated, and changes tested should you modify the object's attributes on the Object Attributes screen.
Applying the object change before updating process logic will cause those processes to fail on their next execution.
Design Principle
Never change object attributes without checking dependencies first. Attribute changes are structural and require coordinated updates across process inputs, outputs, deletions, and any related workbooks. Skipping this step risks breaking processes that may be running on a schedule.