When an automation chain step that runs in parallel with other steps is removed, it does not affect the operation of the remaining steps. The other steps that were originally set up to run in parallel will continue to run in parallel unless their configuration is changed manually.
ReferencesKinaxis RapidResponse's documentation on automation chains clarifies the behavior of parallel steps in an automation chain when one step is modified or removed. The behavior and configuration of the remaining steps persist until they are manually changed.
References:The answer is based on general knowledge of automation chains and parallel processing.For specific Kinaxis RapidResponse functionality, please refer to the official training materials and documentation123.

To identify an automation chain and its associated resources, searching for resources based on the specific table involved in the automation (in this case, "HistoricalPartKPI") will help you find the correct automation chain. This approach ensures that you identify all the resources related to that particular table, including automation chains.
ReferencesThe Kinaxis RapidResponse documentation for administrators provides guidance on how to search for and identify resources associated with specific tables or actions within the system, which includes searching for resources based on table names.

To track which performers are late and by how much for each activity in a process orchestration scenario, you need to access data that includes information on activity assignments, due dates, and completion status. The Assignment table within the ProcOrch (Process Orchestration) namespace contains this data. You can use this table to identify the performers assigned to each activity, check the planned completion dates against actual completion dates, and calculate the delays.
By creating a worksheet based on the Assignment table, you can include columns for activity IDs, performer IDs, due dates, completion dates, and a calculated field for the delay. The delay can be calculated by comparing the due date with the completion date or the current date if the activity is not yet completed. If there is more than one performer per activity, each performer's assignment will be a separate record in the Assignment table, allowing the worksheet to show delays for each performer.
References:
* Kinaxis RapidResponse documentation on creating worksheets based on specific tables.
* Training and knowledge resources provided by Kinaxis on how to use and configure worksheets in RapidResponse for process orchestration scenarios.

The expression to display the number of the calendar week from the beginning of the year takes today's date, resets it to the start of the year (the 0 Year part), and then calculates the week number from this start date, adding 1 since week numbers generally start at 1, not 0.
ReferencesThe logic for calculating week numbers from a given date is commonly described in Kinaxis RapidResponse documentation and training materials concerning date and time functions.

Structure II shows BuyerCode connected to Department and Department connected to Manager. This setup supports multiple departments per manager while allowing for each department to be on a specific floor. Since users may want to filter on combinations of BuyerCode, Manager, Department, and Floor, this design accommodates such queries efficiently by structuring the Department as a central entity that relates to the others. In Structure II, Department is linked to BuyerCode and Manager, enabling a query to traverse from BuyerCode to Manager through Department, making it optimal for the desired filters.
ReferencesBest practices for database design suggest structuring your data model to reflect the relationships between entities in a way that supports the expected queries and filters. In Kinaxis RapidResponse, this often means creating a logical structure that minimizes join complexity and optimizes the data model for typical user operations.