🔍

GCX016ER - Thematically Grouped Rules

A dual-persona matrix designed specifically for Development scoping. Requirements are hierarchically structured by Epic → Module Program → Business Theme.

Epic Core: GCX016ER Processing

Module Tracker: GCX016E

3573 Validations & Rules
Module Objective: No description provided from architecture analysis.
⚙️ General Logic & Formats 104 logic blocks
R-GCX016E-cbl-02868 Check Message Backout Count
Validation Rules
📊 Business Logic Narrative
When the process 'Check Message Backout Count' is invoked, and assuming that a message has been successfully retrieved from the queue, when the message backout count is evaluated, the desired outcome is that if backout count is zero, mark as good message; if backout count is greater than zero, mark as skip message due to high backout count.
💻 Technical Criteria
Given A message has been successfully retrieved from the queue
When The message backout count is evaluated
Then If backout count is zero, mark as good message; if backout count is greater than zero, mark as skip message due to high backout count
R-GCX016E-cbl-00074 Apply CPRS Special Processing
Decision Rules
📊 Business Logic Narrative
When the process 'Apply CPRS Special Processing' is invoked, and assuming that a train has been successfully found in the system, when the train is identified as a cprs train, the desired outcome is that the system applies cprs-specific processing rules and continues with train processing.
💻 Technical Criteria
Given A train has been successfully found in the system
When The train is identified as a CPRS train
Then The system applies CPRS-specific processing rules and continues with train processing
R-GCX016E-cbl-02879 Apply CPRS Special Processing
Process Rules
📊 Business Logic Narrative
When the process 'Apply CPRS Special Processing' is invoked, and assuming that a train has been identified as cprs type, when cprs special processing is triggered, the desired outcome is that cprs-specific business rules and processing logic are applied to the train.
💻 Technical Criteria
Given A train has been identified as CPRS type
When CPRS special processing is triggered
Then CPRS-specific business rules and processing logic are applied to the train
R-GCX016E-cbl-02883 Set Train Error Flag
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Train Error Flag', assuming that a train not found error has occurred and merlin message has been created, when error flag setting is processed, the desired outcome is that train error flag is set to indicate train lookup failure.
💻 Technical Criteria
EXCLUDING A train not found error has occurred and Merlin message has been created
When Error flag setting is processed
Then Train error flag is set to indicate train lookup failure
R-GCX016E-cbl-02884 Continue Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue Processing' is invoked, and assuming that train lookup processing has completed (either successfully or with error), when train lookup phase is finished, the desired outcome is that system continues with the next phase of message processing.
💻 Technical Criteria
Given Train lookup processing has completed (either successfully or with error)
When Train lookup phase is finished
Then System continues with the next phase of message processing
R-GCX016E-cbl-00156 Train Found in System?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Train Found in System?', assuming that a train id has been extracted from m10 segment and vessel name does not start with 'train' or 'day', when the system searches the train list for the specified train id, the desired outcome is that the system determines if the train exists in the system or generates train not found error if train does not exist.
💻 Technical Criteria
EXCLUDING A train ID has been extracted from M10 segment AND vessel name does not start with 'TRAIN' or 'DAY'
When The system searches the train list for the specified train ID
Then The system determines if the train exists in the system OR generates train not found error if train does not exist
R-GCX016E-cbl-00164 Generate Error Message - Train Not Found
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error Message - Train Not Found', assuming that a train id has been validated and the train does not exist in the train list, when the system attempts to process a lock request for non-existent train, the desired outcome is that the system generates an error message indicating train not found.
💻 Technical Criteria
EXCLUDING A train ID has been validated AND the train does not exist in the train list
When The system attempts to process a lock request for non-existent train
Then The system generates an error message indicating train not found
R-GCX016E-cbl-00168 Train Found in System?
Decision Rules
📊 Business Logic Narrative
When the process 'Train Found in System?' is invoked, and assuming that a train id has been extracted from the m10 segment, when the system searches for the train in the train list, the desired outcome is that if the train is found, processing continues; if not found, an error is generated.
💻 Technical Criteria
Given A train ID has been extracted from the M10 segment
When The system searches for the train in the train list
Then If the train is found, processing continues; if not found, an error is generated
R-GCX016E-cbl-00175 Generate Error Message - Train Not Found
Action Rules
📊 Business Logic Narrative
When the process 'Generate Error Message - Train Not Found' is invoked, and assuming that a train id has been provided for unlock processing, when the train cannot be found in the system, the desired outcome is that the system generates an error message indicating train not found.
💻 Technical Criteria
Given A train ID has been provided for unlock processing
When The train cannot be found in the system
Then The system generates an error message indicating train not found
R-GCX016E-cbl-00179 Train Found in System?
Validation Rules
📊 Business Logic Narrative
When the process 'Train Found in System?' is invoked, and assuming that a train id has been extracted from the m10 segment, when the system searches for the train in the train list, the desired outcome is that the system determines if the train exists and is valid for seizure processing.
💻 Technical Criteria
Given A train ID has been extracted from the M10 segment
When The system searches for the train in the train list
Then The system determines if the train exists and is valid for seizure processing
R-GCX016E-cbl-00182 Set Train Seizure Flag to 'Y'
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Train Seizure Flag to 'Y'', assuming that a train is not currently seized and seizure processing is required, when the system processes the seizure request, the desired outcome is that the system sets the train seizure flag to 'y'.
💻 Technical Criteria
EXCLUDING A train is not currently seized and seizure processing is required
When The system processes the seizure request
Then The system sets the train seizure flag to 'Y'
R-GCX016E-cbl-00190 Generate Error Message - Train Not Found
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error Message - Train Not Found', assuming that a train id has been extracted but the train is not found in the system, when the system cannot locate the train for seizure processing, the desired outcome is that the system generates an error message indicating train not found.
💻 Technical Criteria
EXCLUDING A train ID has been extracted but the train is not found in the system
When The system cannot locate the train for seizure processing
Then The system generates an error message indicating train not found
R-GCX016E-cbl-00192 Complete Train Seizure Processing
Process Rules
📊 Business Logic Narrative
When the process 'Complete Train Seizure Processing' is invoked, and assuming that all seizure processing steps have been completed or skipped appropriately, when the system reaches the end of seizure processing, the desired outcome is that the system completes the train seizure processing and returns control to the main workflow.
💻 Technical Criteria
Given All seizure processing steps have been completed or skipped appropriately
When The system reaches the end of seizure processing
Then The system completes the train seizure processing and returns control to the main workflow
R-GCX016E-cbl-00195 Train Found in System?
Validation Rules
📊 Business Logic Narrative
When the process 'Train Found in System?' is invoked, and assuming that a train id is provided for seizure release processing, when the system looks up the train in the train list, the desired outcome is that the system determines if the train exists and is valid for processing.
💻 Technical Criteria
Given A train ID is provided for seizure release processing
When The system looks up the train in the train list
Then The system determines if the train exists and is valid for processing
R-GCX016E-cbl-00208 Generate Train Not Found Error
Validation Rules
📊 Business Logic Narrative
When the process 'Generate Train Not Found Error' is invoked, and assuming that a train id is provided for seizure release, when the train cannot be found in the system, the desired outcome is that a train not found error is generated and processing stops.
💻 Technical Criteria
Given A train ID is provided for seizure release
When The train cannot be found in the system
Then A train not found error is generated and processing stops
R-GCX016E-cbl-03159 SCAC Code Available?
Decision Rules
📊 Business Logic Narrative
When the process 'SCAC Code Available?' is invoked, and assuming that cprs traffic has been identified for processing, when the system checks for scac code availability, the desired outcome is that if scac code is available, use existing scac code, otherwise set scac as unknown.
💻 Technical Criteria
Given CPRS traffic has been identified for processing
When the system checks for SCAC code availability
Then if SCAC code is available, use existing SCAC code, otherwise set SCAC as unknown
R-GCX016E-cbl-03473 More Counterparts to Check?
Process Rules
📊 Business Logic Narrative
When the process 'More Counterparts to Check?' is invoked, and assuming that one counterpart code has been processed, when the system checks the remaining counterpart code list, the desired outcome is that the system determines if more counterpart codes require processing.
💻 Technical Criteria
Given One counterpart code has been processed
When The system checks the remaining counterpart code list
Then The system determines if more counterpart codes require processing
R-GCX016E-cbl-00394 Retrieve Freight Forwarder Email Address
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Freight Forwarder Email Address' is invoked, and assuming that the freight forwarder name has been successfully looked up, when the system searches the broker email address table (gcstbrt), the desired outcome is that the system retrieves the freight forwarder's email address.
💻 Technical Criteria
Given The freight forwarder name has been successfully looked up
When The system searches the broker email address table (GCSTBRT)
Then The system retrieves the freight forwarder's email address
R-GCX016E-cbl-00406 Retry Limit Reached?
Validation Rules
📊 Business Logic Narrative
When the process 'Retry Limit Reached?' is invoked, and assuming that email delivery has failed and a retry attempt is being considered, when the system checks the current retry count against the maximum retry limit, the desired outcome is that if retry limit is not reached, continue retry attempts; otherwise, log delivery failure and complete process.
💻 Technical Criteria
Given Email delivery has failed and a retry attempt is being considered
When The system checks the current retry count against the maximum retry limit
Then If retry limit is not reached, continue retry attempts; otherwise, log delivery failure and complete process
R-GCX016E-cbl-00422 Check for Follower Manifests?
Decision Rules
📊 Business Logic Narrative
When the process 'Check for Follower Manifests?' is invoked, and assuming that a lead manifest is being processed, when the system checks for associated follower manifests, the desired outcome is that all linked follower manifests are identified and prepared for processing.
💻 Technical Criteria
Given A lead manifest is being processed
When The system checks for associated follower manifests
Then All linked follower manifests are identified and prepared for processing
R-GCX016E-cbl-00427 Include Entry Numbers in Message
Process Rules
📊 Business Logic Narrative
When the process 'Include Entry Numbers in Message' is invoked, and assuming that a follower manifest message is being prepared and entry numbers exist, when the message content is assembled, the desired outcome is that all relevant entry numbers are included in the follower manifest message.
💻 Technical Criteria
Given A follower manifest message is being prepared AND entry numbers exist
When The message content is assembled
Then All relevant entry numbers are included in the follower manifest message
R-GCX016E-cbl-00556 Train Found in System?
Validation Rules
📊 Business Logic Narrative
When the process 'Train Found in System?' is invoked, and assuming that a train id has been extracted from the m10 segment, when the system searches for the train in the train list, the desired outcome is that the system determines if the train exists or not found.
💻 Technical Criteria
Given A train ID has been extracted from the M10 segment
When The system searches for the train in the train list
Then The system determines if the train exists or not found
R-GCX016E-cbl-00559 Clear Train Arrival Date
Action Rules
📊 Business Logic Narrative
When the process 'Clear Train Arrival Date' is invoked, and assuming that a train has an existing arrival date, when the train arrival is being cancelled, the desired outcome is that the system clears the train arrival date field.
💻 Technical Criteria
Given A train has an existing arrival date
When The train arrival is being cancelled
Then The system clears the train arrival date field
R-GCX016E-cbl-00560 Reset Train Arrival Flags
Action Rules
📊 Business Logic Narrative
When the process 'Reset Train Arrival Flags' is invoked, and assuming that a train has arrival flags set, when the train arrival is being cancelled, the desired outcome is that the system resets all train arrival flags to their initial state.
💻 Technical Criteria
Given A train has arrival flags set
When The train arrival is being cancelled
Then The system resets all train arrival flags to their initial state
R-GCX016E-cbl-00566 Generate Train Not Found Error
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Train Not Found Error', assuming that a train id has been extracted from the m10 segment, when the train is not found in the train list, the desired outcome is that the system generates a train not found error message.
💻 Technical Criteria
EXCLUDING A train ID has been extracted from the M10 segment
When The train is not found in the train list
Then The system generates a train not found error message
R-GCX016E-cbl-00754 Release Quantity < 0?
Validation Rules
📊 Business Logic Narrative
When the process 'Release Quantity < 0?' is invoked, and assuming that a calculated release quantity exists, when the release quantity is validated for minimum bounds, the desired outcome is that if release quantity is less than zero, the release quantity is set to zero.
💻 Technical Criteria
Given A calculated release quantity exists
When The release quantity is validated for minimum bounds
Then If release quantity is less than zero, the release quantity is set to zero
R-GCX016E-cbl-00862 Log Canadian Manifest Match
Process Rules
📊 Business Logic Narrative
When the process 'Log Canadian Manifest Match' is invoked, and assuming that canadian manifest matching has been completed successfully, when logging is performed, the desired outcome is that system logs the successful canadian manifest match with relevant details.
💻 Technical Criteria
Given Canadian manifest matching has been completed successfully
When Logging is performed
Then System logs the successful Canadian manifest match with relevant details
R-GCX016E-cbl-00970 Set Message Type as RELEASE
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Message Type as RELEASE' is invoked, and assuming that a comprehensive release message has been formatted, when the system finalizes message properties, the desired outcome is that the system sets the message type indicator to release for proper routing and processing.
💻 Technical Criteria
Given A comprehensive release message has been formatted
When The system finalizes message properties
Then The system sets the message type indicator to RELEASE for proper routing and processing
R-GCX016E-cbl-01029 SCAC Code Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'SCAC Code Valid?' is invoked, and assuming that a scac code has been extracted from the m10 segment, when the system validates the scac code against business rules, the desired outcome is that the scac code is determined to be valid if it is not spaces and meets format requirements, otherwise it is invalid.
💻 Technical Criteria
Given A SCAC code has been extracted from the M10 segment
When The system validates the SCAC code against business rules
Then The SCAC code is determined to be valid if it is not spaces and meets format requirements, otherwise it is invalid
R-GCX016E-cbl-01033 Country Code Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Country Code Valid?' is invoked, and assuming that a country code has been extracted from the m10 segment, when the system validates the country code against acceptable country codes, the desired outcome is that the country code is determined to be valid if it matches recognized country identifiers, otherwise it is invalid.
💻 Technical Criteria
Given A country code has been extracted from the M10 segment
When The system validates the country code against acceptable country codes
Then The country code is determined to be valid if it matches recognized country identifiers, otherwise it is invalid
R-GCX016E-cbl-01035 Construct M10 Manifest Segment
Process Rules
📊 Business Logic Narrative
When the process 'Construct M10 Manifest Segment' is invoked, and assuming that all required data elements have been extracted and validated from the input, when the system constructs the m10 manifest segment, the desired outcome is that a properly formatted m10 segment is created with all required fields populated.
💻 Technical Criteria
Given All required data elements have been extracted and validated from the input
When The system constructs the M10 manifest segment
Then A properly formatted M10 segment is created with all required fields populated
R-GCX016E-cbl-01040 M10 Segment Complete?
Validation Rules
📊 Business Logic Narrative
When the process 'M10 Segment Complete?' is invoked, and assuming that an m10 manifest segment has been constructed with populated fields, when the system validates the completeness of the m10 segment, the desired outcome is that the m10 segment is determined to be complete if all mandatory fields are populated, otherwise it is incomplete.
💻 Technical Criteria
Given An M10 manifest segment has been constructed with populated fields
When The system validates the completeness of the M10 segment
Then The M10 segment is determined to be complete if all mandatory fields are populated, otherwise it is incomplete
R-GCX016E-cbl-01042 Store M10 Manifest Segment
Process Rules
📊 Business Logic Narrative
When the process 'Store M10 Manifest Segment' is invoked, and assuming that an m10 manifest segment has been constructed and validated, when the system stores the m10 segment, the desired outcome is that the m10 segment is stored in the appropriate data structure for subsequent processing steps.
💻 Technical Criteria
Given An M10 manifest segment has been constructed and validated
When The system stores the M10 segment
Then The M10 segment is stored in the appropriate data structure for subsequent processing steps
R-GCX016E-cbl-03035 Show Before Release Quantity
Process Rules
📊 Business Logic Narrative
When the process 'Show Before Release Quantity' is invoked, and assuming that quantity impact has been detected, when the system processes quantity display, the desired outcome is that the current release quantity before changes is shown in the message.
💻 Technical Criteria
Given Quantity impact has been detected
When The system processes quantity display
Then The current release quantity before changes is shown in the message
R-GCX016E-cbl-03036 Show After Release Quantity
Process Rules
📊 Business Logic Narrative
When the process 'Show After Release Quantity' is invoked, and assuming that before release quantity has been displayed, when the system continues quantity processing, the desired outcome is that the projected release quantity after changes is shown in the message.
💻 Technical Criteria
Given Before release quantity has been displayed
When The system continues quantity processing
Then The projected release quantity after changes is shown in the message
R-GCX016E-cbl-03041 Add Processing Details
Process Rules
📊 Business Logic Narrative
When the process 'Add Processing Details' is invoked, and assuming that processing context and details are available, when the system assembles message content, the desired outcome is that processing details are added to provide context in the merlin message.
💻 Technical Criteria
Given Processing context and details are available
When The system assembles message content
Then Processing details are added to provide context in the Merlin message
R-GCX016E-cbl-03048 Assemble Complete Message Content
Process Rules
📊 Business Logic Narrative
When the process 'Assemble Complete Message Content' is invoked, and assuming that all message components have been processed and formatted, when the system assembles complete content, the desired outcome is that all components are combined into complete merlin message content.
💻 Technical Criteria
Given All message components have been processed and formatted
When The system assembles complete content
Then All components are combined into complete Merlin message content
R-GCX016E-cbl-03049 Validate Message Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Message Format' is invoked, and assuming that complete message content has been assembled, when the system validates message format, the desired outcome is that message format is validated against merlin standards and requirements.
💻 Technical Criteria
Given Complete message content has been assembled
When The system validates message format
Then Message format is validated against Merlin standards and requirements
R-GCX016E-cbl-03277 Validate K1 Segment Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate K1 Segment Format' is invoked, and assuming that a k1 segment is received for processing, when the system validates the k1 segment format and structure, the desired outcome is that the segment is accepted if format is valid, otherwise it is rejected and logged as invalid.
💻 Technical Criteria
Given A K1 segment is received for processing
When The system validates the K1 segment format and structure
Then The segment is accepted if format is valid, otherwise it is rejected and logged as invalid
R-GCX016E-cbl-03417 Extract K1 Comment Text
Process Rules
📊 Business Logic Narrative
When the process 'Extract K1 Comment Text' is invoked, and assuming that a k1 segment is received in the message, when the system processes the k1 segment, the desired outcome is that the comment text is extracted from the k1 segment and made available for content analysis.
💻 Technical Criteria
Given A K1 segment is received in the message
When The system processes the K1 segment
Then The comment text is extracted from the K1 segment and made available for content analysis
R-GCX016E-cbl-03529 Extract Comment Text Content
Process Rules
📊 Business Logic Narrative
When the process 'Extract Comment Text Content' is invoked, and assuming that a k1 segment is received with comment data, when the system processes the k1 segment, the desired outcome is that the comment text content is extracted and made available for pattern matching analysis.
💻 Technical Criteria
Given A K1 segment is received with comment data
When The system processes the K1 segment
Then The comment text content is extracted and made available for pattern matching analysis
R-GCX016E-cbl-01176 Prepare Freight Forwarder Data for Processing
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Freight Forwarder Data for Processing' is invoked, and assuming that a freight forwarder has been successfully identified and the found flag has been set, when the system prepares the freight forwarder data for downstream processing, the desired outcome is that freight forwarder data is formatted and made available for subsequent business processes.
💻 Technical Criteria
Given A freight forwarder has been successfully identified and the found flag has been set
When The system prepares the freight forwarder data for downstream processing
Then Freight forwarder data is formatted and made available for subsequent business processes
R-GCX016E-cbl-01197 Validate Email Address Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Email Address Format' is invoked, and assuming that an email address has been retrieved from the broker table, when the system validates the email address format, the desired outcome is that the email address format is checked for validity according to standard email formatting rules.
💻 Technical Criteria
Given An email address has been retrieved from the broker table
When The system validates the email address format
Then The email address format is checked for validity according to standard email formatting rules
R-GCX016E-cbl-01212 Retrieve Email Address from Broker Table
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Email Address from Broker Table' is invoked, and assuming that a valid freight forwarder has been identified, when the system accesses the broker table segments (gcstbrt), the desired outcome is that the system retrieves the email address associated with the freight forwarder.
💻 Technical Criteria
Given A valid freight forwarder has been identified
When The system accesses the broker table segments (GCSTBRT)
Then The system retrieves the email address associated with the freight forwarder
R-GCX016E-cbl-01232 Increment Retry Counter
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Increment Retry Counter', assuming that email delivery attempt failed, when the delivery is not successful, the desired outcome is that the system increments the retry counter to track delivery attempts.
💻 Technical Criteria
EXCLUDING Email delivery attempt failed
When The delivery is not successful
Then The system increments the retry counter to track delivery attempts
R-GCX016E-cbl-01234 Wait for Retry Interval
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Wait for Retry Interval', assuming that email delivery failed and retry limit has not been reached, when the system processes retry interval, the desired outcome is that the system waits for the configured retry interval before attempting delivery again.
💻 Technical Criteria
EXCLUDING Email delivery failed and retry limit has not been reached
When The system processes retry interval
Then The system waits for the configured retry interval before attempting delivery again
R-GCX016E-cbl-01235 Log Delivery Failure
Process Rules
📊 Business Logic Narrative
When the process 'Log Delivery Failure' is invoked, and assuming that email delivery has failed and retry limit has been reached, when the system processes the final delivery failure, the desired outcome is that the system logs the delivery failure for audit and troubleshooting purposes.
💻 Technical Criteria
Given Email delivery has failed and retry limit has been reached
When The system processes the final delivery failure
Then The system logs the delivery failure for audit and troubleshooting purposes
R-GCX016E-cbl-01261 Send Message to Basket
Action Rules
📊 Business Logic Narrative
When the process 'Send Message to Basket' is invoked, and assuming that a message recipient has been determined, when message delivery is initiated, the desired outcome is that the message should be sent to the recipient's designated basket.
💻 Technical Criteria
Given A message recipient has been determined
When Message delivery is initiated
Then The message should be sent to the recipient's designated basket
R-GCX016E-cbl-01262 Message Delivered Successfully
Validation Rules
📊 Business Logic Narrative
When the process 'Message Delivered Successfully' is invoked, and assuming that a message has been sent to a recipient's basket, when the delivery is successful, the desired outcome is that the system should confirm successful message delivery.
💻 Technical Criteria
Given A message has been sent to a recipient's basket
When The delivery is successful
Then The system should confirm successful message delivery
R-GCX016E-cbl-01265 Log Delivery Failure
Action Rules
📊 Business Logic Narrative
When the process 'Log Delivery Failure' is invoked, and assuming that a message delivery has failed and rerouting has been attempted, when the rerouting also fails, the desired outcome is that the delivery failure should be logged.
💻 Technical Criteria
Given A message delivery has failed and rerouting has been attempted
When The rerouting also fails
Then The delivery failure should be logged
R-GCX016E-cbl-03088 Set Default Recipient OM01247
Decision Rules
📊 Business Logic Narrative
When the process 'Set Default Recipient OM01247' is invoked, and assuming that either no ad segment is available or no valid recipient was found in ad segment, when the system applies default recipient logic, the desired outcome is that the system sets om01247 as the message recipient.
💻 Technical Criteria
Given Either no AD segment is available or no valid recipient was found in AD segment
When The system applies default recipient logic
Then The system sets OM01247 as the message recipient
R-GCX016E-cbl-01275 Send to Configured Recipient
Action Rules
📊 Business Logic Narrative
When the process 'Send to Configured Recipient' is invoked, and assuming that a valid recipient has been identified, when the delivery process executes, the desired outcome is that the message is sent to the configured recipient.
💻 Technical Criteria
Given A valid recipient has been identified
When The delivery process executes
Then The message is sent to the configured recipient
R-GCX016E-cbl-01276 Send to Default Recipient OM01247
Process Rules
📊 Business Logic Narrative
When the process 'Send to Default Recipient OM01247' is invoked, and assuming that no valid configured recipient was found, when the fallback process activates, the desired outcome is that the message is automatically sent to default recipient om01247.
💻 Technical Criteria
Given No valid configured recipient was found
When The fallback process activates
Then The message is automatically sent to default recipient OM01247
R-GCX016E-cbl-01281 Send to Alternative Recipient
Action Rules
📊 Business Logic Narrative
When the process 'Send to Alternative Recipient' is invoked, and assuming that rerouting process has identified alternative recipients, when the alternative delivery executes, the desired outcome is that the message is sent to backup recipients aei9999 and om01247.
💻 Technical Criteria
Given Rerouting process has identified alternative recipients
When The alternative delivery executes
Then The message is sent to backup recipients AEI9999 and OM01247
R-GCX016E-cbl-01290 Queue Open Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Queue Open Successful?' is invoked, and assuming that system has attempted to open gc350.exp.input queue, when queue opening attempt completes, the desired outcome is that system determines if queue opening was successful or failed.
💻 Technical Criteria
Given System has attempted to open GC350.EXP.INPUT queue
When Queue opening attempt completes
Then System determines if queue opening was successful or failed
R-GCX016E-cbl-01296 Log Queue Open Failure
Process Rules
📊 Business Logic Narrative
When the process 'Log Queue Open Failure' is invoked, and assuming that gc350.exp.input queue opening has failed, when queue opening error handling is processed, the desired outcome is that queue opening failure details are logged to system audit trail.
💻 Technical Criteria
Given GC350.EXP.INPUT queue opening has failed
When Queue opening error handling is processed
Then Queue opening failure details are logged to system audit trail
R-GCX016E-cbl-01318 Validate Segment Completeness
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Segment Completeness' is invoked, and assuming that all segment structures have been created and populated, when the system validates segment completeness, the desired outcome is that the system checks that all mandatory fields contain valid data and all segment structures are properly formed.
💻 Technical Criteria
Given All segment structures have been created and populated
When The system validates segment completeness
Then The system checks that all mandatory fields contain valid data and all segment structures are properly formed
R-GCX016E-cbl-01391 Validate U1 Segment Data
Validation Rules
📊 Business Logic Narrative
When the process 'Validate U1 Segment Data' is invoked, and assuming that the u1 segment has been populated with all required data elements, when the system validates the u1 segment data, the desired outcome is that the system should verify that all mandatory fields are populated and data formats are correct.
💻 Technical Criteria
Given The U1 segment has been populated with all required data elements
When The system validates the U1 segment data
Then The system should verify that all mandatory fields are populated and data formats are correct
R-GCX016E-cbl-01426 Validate Reference Number Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Reference Number Format' is invoked, and assuming that n9 reference numbers have been retrieved, when the system validates the format of each reference number, the desired outcome is that each reference number is confirmed to meet format requirements.
💻 Technical Criteria
Given N9 reference numbers have been retrieved
When The system validates the format of each reference number
Then Each reference number is confirmed to meet format requirements
R-GCX016E-cbl-01427 Reference Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Reference Type?' is invoked, and assuming that n9 reference numbers have been validated for format, when the system examines the reference type qualifier, the desired outcome is that references are classified as either fda references (a1/a3) or general references.
💻 Technical Criteria
Given N9 reference numbers have been validated for format
When The system examines the reference type qualifier
Then References are classified as either FDA references (A1/A3) or general references
R-GCX016E-cbl-01428 Process FDA Reference Numbers - A1/A3
Process Rules
📊 Business Logic Narrative
When the process 'Process FDA Reference Numbers - A1/A3' is invoked, and assuming that n9 references are classified as fda type with a1 or a3 qualifiers, when the system processes these fda references, the desired outcome is that fda reference numbers are processed with specialized fda handling rules.
💻 Technical Criteria
Given N9 references are classified as FDA type with A1 or A3 qualifiers
When The system processes these FDA references
Then FDA reference numbers are processed with specialized FDA handling rules
R-GCX016E-cbl-01429 Process General Reference Numbers
Process Rules
📊 Business Logic Narrative
When the process 'Process General Reference Numbers' is invoked, and assuming that n9 references are classified as general (non-fda) type, when the system processes these general references, the desired outcome is that general reference numbers are processed using standard reference handling procedures.
💻 Technical Criteria
Given N9 references are classified as general (non-FDA) type
When The system processes these general references
Then General reference numbers are processed using standard reference handling procedures
R-GCX016E-cbl-01479 Apply CPRS Special Processing Rules
Process Rules
📊 Business Logic Narrative
When the process 'Apply CPRS Special Processing Rules' is invoked, and assuming that a train has been identified as cprs type, when the system applies cprs-specific processing rules, the desired outcome is that execute cprs special processing logic and then set train found flag.
💻 Technical Criteria
Given A train has been identified as CPRS type
When The system applies CPRS-specific processing rules
Then Execute CPRS special processing logic and then set train found flag
R-GCX016E-cbl-01624 Use V9 Segment Date
Action Rules
📊 Business Logic Narrative
When the process 'Use V9 Segment Date' is invoked, and assuming that the v9 segment date has been validated as correct, when the system processes the train arrival date assignment, the desired outcome is that the system assigns the v9 segment date as the official train arrival date.
💻 Technical Criteria
Given The V9 segment date has been validated as correct
When The system processes the train arrival date assignment
Then The system assigns the V9 segment date as the official train arrival date
R-GCX016E-cbl-01648 K1 Segment Detected in Message Stream
Validation Rules
📊 Business Logic Narrative
When the process 'K1 Segment Detected in Message Stream' is invoked, and assuming that a message segment is being processed, when the segment type is 'k1' and train context is being evaluated, the desired outcome is that the system should identify the k1 segment and check if train processing context is active.
💻 Technical Criteria
Given A message segment is being processed
When The segment type is 'K1' and train context is being evaluated
Then The system should identify the K1 segment and check if train processing context is active
R-GCX016E-cbl-01649 Extract Free-Form Text from K1 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Free-Form Text from K1 Segment' is invoked, and assuming that a k1 segment is detected and train context is active, when the system processes the k1 segment content, the desired outcome is that the free-form text should be extracted from the k1 segment data.
💻 Technical Criteria
Given A K1 segment is detected and train context is active
When The system processes the K1 segment content
Then The free-form text should be extracted from the K1 segment data
R-GCX016E-cbl-01656 Include K1 Text in Train Merlin Messages
Process Rules
📊 Business Logic Narrative
When the process 'Include K1 Text in Train Merlin Messages' is invoked, and assuming that k1 remark is logged for the train, when the system generates merlin messages for the train, the desired outcome is that the k1 text should be included in the train merlin messages.
💻 Technical Criteria
Given K1 remark is logged for the train
When The system generates Merlin messages for the train
Then The K1 text should be included in the train Merlin messages
R-GCX016E-cbl-01657 Continue to Next Message Segment
Process Rules
📊 Business Logic Narrative
When the process 'Continue to Next Message Segment' is invoked, and assuming that k1 processing is complete (either with train context or without), when the system finishes k1 segment processing, the desired outcome is that the system should continue to process the next message segment.
💻 Technical Criteria
Given K1 processing is complete (either with train context or without)
When The system finishes K1 segment processing
Then The system should continue to process the next message segment
R-GCX016E-cbl-01658 K1 Segment Detected in Message
Decision Rules
📊 Business Logic Narrative
When the process 'K1 Segment Detected in Message' is invoked, and assuming that a message segment is being processed, when the segment type is identified as 'k1', the desired outcome is that the system should invoke b400-process-k1-segment routine.
💻 Technical Criteria
Given A message segment is being processed
When The segment type is identified as 'K1'
Then The system should invoke B400-PROCESS-K1-SEGMENT routine
R-GCX016E-cbl-01659 Extract Free-Form Text Message
Process Rules
📊 Business Logic Narrative
When the process 'Extract Free-Form Text Message' is invoked, and assuming that a k1 segment is being processed, when the segment contains free-form text data, the desired outcome is that the system should extract and store the text message content.
💻 Technical Criteria
Given A K1 segment is being processed
When The segment contains free-form text data
Then The system should extract and store the text message content
R-GCX016E-cbl-01668 Continue Message Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue Message Processing' is invoked, and assuming that k1 segment processing is complete including logging, when the system needs to continue with remaining message segments, the desired outcome is that the system should proceed to process the next segment in the message sequence.
💻 Technical Criteria
Given K1 segment processing is complete including logging
When The system needs to continue with remaining message segments
Then The system should proceed to process the next segment in the message sequence
R-GCX016E-cbl-01751 Include Entry Numbers in Message
Process Rules
📊 Business Logic Narrative
When the process 'Include Entry Numbers in Message' is invoked, and assuming that a follower manifest message is being prepared and entry numbers exist, when the system includes entry numbers in the message, the desired outcome is that all relevant entry numbers are included in the follower manifest message.
💻 Technical Criteria
Given A follower manifest message is being prepared and entry numbers exist
When The system includes entry numbers in the message
Then All relevant entry numbers are included in the follower manifest message
R-GCX016E-cbl-01837 Check Entry Number Format
Validation Rules
📊 Business Logic Narrative
When the process 'Check Entry Number Format' is invoked, and assuming that an entry number is received from x4 segment, when the system checks the entry number format, the desired outcome is that the entry number is validated for proper format structure and marked as valid or invalid format.
💻 Technical Criteria
Given An entry number is received from X4 segment
When The system checks the entry number format
Then The entry number is validated for proper format structure and marked as valid or invalid format
R-GCX016E-cbl-01846 V37 Entry Found?
Decision Rules
📊 Business Logic Narrative
When the process 'V37 Entry Found?' is invoked, and assuming that a special v37 entry search result, when the system evaluates if v37 entry was found, the desired outcome is that if v37 entry is found, mark entry number as valid, otherwise generate entry number error.
💻 Technical Criteria
Given A special V37 entry search result
When The system evaluates if V37 entry was found
Then If V37 entry is found, mark entry number as valid, otherwise generate entry number error
R-GCX016E-cbl-01883 Create New FDA Reference Entry
Process Rules
📊 Business Logic Narrative
When the process 'Create New FDA Reference Entry' is invoked, and assuming that an n9 segment is being processed and no existing fda data is found, when the system creates a new fda reference entry, the desired outcome is that a new fda reference entry should be created with appropriate prefix formatting.
💻 Technical Criteria
Given An N9 segment is being processed and no existing FDA data is found
When The system creates a new FDA reference entry
Then A new FDA reference entry should be created with appropriate prefix formatting
R-GCX016E-cbl-01885 Validate FDA Reference Number Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate FDA Reference Number Format' is invoked, and assuming that an fda reference number has been formatted with appropriate prefix, when the system validates the fda reference number format, the desired outcome is that the fda reference number format should be verified as compliant with regulatory standards.
💻 Technical Criteria
Given An FDA reference number has been formatted with appropriate prefix
When The system validates the FDA reference number format
Then The FDA reference number format should be verified as compliant with regulatory standards
R-GCX016E-cbl-03318 SCAC Code Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'SCAC Code Valid?' is invoked, and assuming that a scac code has been extracted from the m10 segment, when the system validates the scac code, the desired outcome is that the scac code must be non-blank and contain valid alphanumeric characters.
💻 Technical Criteria
Given A SCAC code has been extracted from the M10 segment
When The system validates the SCAC code
Then The SCAC code must be non-blank and contain valid alphanumeric characters
R-GCX016E-cbl-03451 Extract M10 Segment Data
Process Rules
📊 Business Logic Narrative
When the process 'Extract M10 Segment Data' is invoked, and assuming that an m10 segment is available for processing, when the system processes the m10 segment, the desired outcome is that all m10 segment data fields are extracted and made available for manifest building.
💻 Technical Criteria
Given An M10 segment is available for processing
When The system processes the M10 segment
Then All M10 segment data fields are extracted and made available for manifest building
R-GCX016E-cbl-03452 Map SCAC Code from M10
Definitional Rules
📊 Business Logic Narrative
When the process 'Map SCAC Code from M10' is invoked, and assuming that m10 segment data has been extracted, when the system processes the scac code field from m10 segment, the desired outcome is that the scac code is mapped to the appropriate field in the foreign manifest structure.
💻 Technical Criteria
Given M10 segment data has been extracted
When The system processes the SCAC code field from M10 segment
Then The SCAC code is mapped to the appropriate field in the foreign manifest structure
R-GCX016E-cbl-03462 Build Complete Manifest Structure
Process Rules
📊 Business Logic Narrative
When the process 'Build Complete Manifest Structure' is invoked, and assuming that all field mappings have been validated successfully, when the system builds the foreign manifest structure, the desired outcome is that a complete foreign manifest data structure is constructed with all required fields properly populated.
💻 Technical Criteria
Given All field mappings have been validated successfully
When The system builds the foreign manifest structure
Then A complete foreign manifest data structure is constructed with all required fields properly populated
R-GCX016E-cbl-02468 Before/After Quantities Different?
Decision Rules
📊 Business Logic Narrative
When the process 'Before/After Quantities Different?' is invoked, and assuming that release quantity impact has been calculated, when before and after quantities are compared, the desired outcome is that the system determines if there is a significant difference requiring quantity impact messaging.
💻 Technical Criteria
Given Release quantity impact has been calculated
When Before and after quantities are compared
Then The system determines if there is a significant difference requiring quantity impact messaging
R-GCX016E-cbl-02469 Format Quantity Impact Message
Process Rules
📊 Business Logic Narrative
When the process 'Format Quantity Impact Message' is invoked, and assuming that before and after quantities are different, when quantity impact messaging is required, the desired outcome is that the system formats a detailed message showing the quantity changes.
💻 Technical Criteria
Given Before and after quantities are different
When Quantity impact messaging is required
Then The system formats a detailed message showing the quantity changes
R-GCX016E-cbl-02486 Finalize Message Content
Process Rules
📊 Business Logic Narrative
When the process 'Finalize Message Content' is invoked, and assuming that system processing time has been added, when message content assembly is complete, the desired outcome is that the system finalizes the message content structure and prepares for message attributes.
💻 Technical Criteria
Given System processing time has been added
When Message content assembly is complete
Then The system finalizes the message content structure and prepares for message attributes
R-GCX016E-cbl-02506 Release Quantity Changed?
Decision Rules
📊 Business Logic Narrative
When the process 'Release Quantity Changed?' is invoked, and assuming that before and after release quantities are available, when the system compares the quantities for changes, the desired outcome is that if the before and after quantities are different, the system identifies that release quantity has changed, otherwise no change is detected.
💻 Technical Criteria
Given Before and after release quantities are available
When The system compares the quantities for changes
Then If the before and after quantities are different, the system identifies that release quantity has changed, otherwise no change is detected
R-GCX016E-cbl-02565 Return Table Data
Process Rules
📊 Business Logic Narrative
When the process 'Return Table Data' is invoked, and assuming that table data was successfully found during lookup, when the data return process is executed, the desired outcome is that the system should return the retrieved table data to the caller.
💻 Technical Criteria
Given Table data was successfully found during lookup
When The data return process is executed
Then The system should return the retrieved table data to the caller
R-GCX016E-cbl-02581 K1 Comments Available?
Decision Rules
📊 Business Logic Narrative
When the process 'K1 Comments Available?' is invoked, and assuming that k1 segment processing has been completed, when determining message content components, the desired outcome is that if k1 comments are available and relevant, they are included; otherwise, processing continues without them.
💻 Technical Criteria
Given K1 segment processing has been completed
When Determining message content components
Then If K1 comments are available and relevant, they are included; otherwise, processing continues without them
R-GCX016E-cbl-02582 Include Free-Form Text Messages
Computation Rules
📊 Business Logic Narrative
When the process 'Include Free-Form Text Messages' is invoked, and assuming that k1 comments are available and contain free-form text, when k1 comments are determined to be relevant for the message, the desired outcome is that free-form text messages from k1 segments are included in the merlin message.
💻 Technical Criteria
Given K1 comments are available and contain free-form text
When K1 comments are determined to be relevant for the message
Then Free-form text messages from K1 segments are included in the Merlin message
R-GCX016E-cbl-02642 Extract Freight Forwarder Code from GCSUSS03
Process Rules
📊 Business Logic Narrative
When the process 'Extract Freight Forwarder Code from GCSUSS03' is invoked, and assuming that the gcsuss03 segment has been successfully retrieved, when the system processes the gcsuss03 segment data, the desired outcome is that the freight forwarder code is extracted from the gcsuss03 segment.
💻 Technical Criteria
Given The GCSUSS03 segment has been successfully retrieved
When The system processes the GCSUSS03 segment data
Then The freight forwarder code is extracted from the GCSUSS03 segment
R-GCX016E-cbl-02680 Freight Forwarder Name Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Freight Forwarder Name Found?' is invoked, and assuming that the freight forwarder name lookup has been completed, when the system evaluates whether a valid freight forwarder name was found, the desired outcome is that the system determines whether to proceed with email address retrieval or terminate processing.
💻 Technical Criteria
Given The freight forwarder name lookup has been completed
When The system evaluates whether a valid freight forwarder name was found
Then The system determines whether to proceed with email address retrieval or terminate processing
R-GCX016E-cbl-02682 Valid Email Address?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid Email Address?' is invoked, and assuming that email address retrieval from gcstbrt table has been completed, when the system evaluates the retrieved email address for validity, the desired outcome is that the system determines whether to proceed with email content building or terminate processing.
💻 Technical Criteria
Given Email address retrieval from GCSTBRT table has been completed
When The system evaluates the retrieved email address for validity
Then The system determines whether to proceed with email content building or terminate processing
R-GCX016E-cbl-02698 Set Initial Delivery Attempt
Process Rules
📊 Business Logic Narrative
When the process 'Set Initial Delivery Attempt' is invoked, and assuming that email message content is prepared and ready for delivery, when the system sets up the initial delivery attempt, the desired outcome is that the retry counter is set to zero and delivery parameters are initialized for the first attempt.
💻 Technical Criteria
Given Email message content is prepared and ready for delivery
When The system sets up the initial delivery attempt
Then The retry counter is set to zero and delivery parameters are initialized for the first attempt
R-GCX016E-cbl-02699 Attempt Email Delivery
Action Rules
📊 Business Logic Narrative
When the process 'Attempt Email Delivery' is invoked, and assuming that email message is prepared and delivery attempt is initialized, when the system attempts email delivery, the desired outcome is that the email is transmitted to the freight forwarder's internet address if available, otherwise to the default merlin id.
💻 Technical Criteria
Given Email message is prepared and delivery attempt is initialized
When The system attempts email delivery
Then The email is transmitted to the freight forwarder's internet address if available, otherwise to the default Merlin ID
R-GCX016E-cbl-02702 Increment Retry Counter
Process Rules
📊 Business Logic Narrative
When the process 'Increment Retry Counter' is invoked, and assuming that email delivery has failed, when the system increments the retry counter, the desired outcome is that the retry counter is increased by one to track the current attempt number.
💻 Technical Criteria
Given Email delivery has failed
When The system increments the retry counter
Then The retry counter is increased by one to track the current attempt number
R-GCX016E-cbl-02703 Max Retries Reached?
Decision Rules
📊 Business Logic Narrative
When the process 'Max Retries Reached?' is invoked, and assuming that email delivery has failed and retry counter has been incremented, when the system checks if maximum retries have been reached, the desired outcome is that if retry counter equals or exceeds maximum retry limit, proceed to failure logging, otherwise continue with retry delay.
💻 Technical Criteria
Given Email delivery has failed and retry counter has been incremented
When The system checks if maximum retries have been reached
Then If retry counter equals or exceeds maximum retry limit, proceed to failure logging, otherwise continue with retry delay
R-GCX016E-cbl-02708 Alternative Available?
Decision Rules
📊 Business Logic Narrative
When the process 'Alternative Available?' is invoked, and assuming that primary email delivery has failed and alternative routing is initiated, when the system checks alternative recipient availability, the desired outcome is that if alternative recipients (aei9999, om01247) are available, proceed to send to default recipient, otherwise log final failure.
💻 Technical Criteria
Given Primary email delivery has failed and alternative routing is initiated
When The system checks alternative recipient availability
Then If alternative recipients (AEI9999, OM01247) are available, proceed to send to default recipient, otherwise log final failure
R-GCX016E-cbl-02745 Use Default Recipient OM01247
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Use Default Recipient OM01247', assuming that a message recipient has been determined, when the recipient is not valid, the desired outcome is that the system should use default recipient om01247.
💻 Technical Criteria
EXCLUDING A message recipient has been determined
When The recipient is not valid
Then The system should use default recipient OM01247
R-GCX016E-cbl-02781 Message Delivered Successfully
Process Rules
📊 Business Logic Narrative
When the process 'Message Delivered Successfully' is invoked, and assuming that a merlin message delivery attempt has been completed, when the delivery is determined to be successful, the desired outcome is that the system marks the message as delivered successfully and completes the process.
💻 Technical Criteria
Given A Merlin message delivery attempt has been completed
When The delivery is determined to be successful
Then The system marks the message as delivered successfully and completes the process
R-GCX016E-cbl-02782 Handle Delivery Failure
Process Rules
📊 Business Logic Narrative
When the process 'Handle Delivery Failure' is invoked, and assuming that a merlin message delivery attempt has failed, when the delivery failure is detected, the desired outcome is that the system initiates delivery failure handling procedures.
💻 Technical Criteria
Given A Merlin message delivery attempt has failed
When The delivery failure is detected
Then The system initiates delivery failure handling procedures
R-GCX016E-cbl-02804 Create M10 Vessel Segment
Process Rules
📊 Business Logic Narrative
When the process 'Create M10 Vessel Segment' is invoked, and assuming that train message arrays are initialized, when the system creates m10 vessel segment, the desired outcome is that m10 segment structure is created and ready to receive vessel data.
💻 Technical Criteria
Given Train message arrays are initialized
When The system creates M10 vessel segment
Then M10 segment structure is created and ready to receive vessel data
R-GCX016E-cbl-02805 Set Vessel Name from Train ID
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Vessel Name from Train ID' is invoked, and assuming that m10 vessel segment is created and train id is available, when the system sets vessel name from train id, the desired outcome is that vessel name field in m10 segment is populated with train identifier.
💻 Technical Criteria
Given M10 vessel segment is created and train ID is available
When The system sets vessel name from train ID
Then Vessel name field in M10 segment is populated with train identifier
R-GCX016E-cbl-02808 Set SCAC Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Set SCAC Code' is invoked, and assuming that country code is set in m10 segment, when the system sets scac code, the desired outcome is that scac code is assigned to identify the carrier responsible for the train.
💻 Technical Criteria
Given Country code is set in M10 segment
When The system sets SCAC code
Then SCAC code is assigned to identify the carrier responsible for the train
R-GCX016E-cbl-02809 Create V9 Event Segment
Process Rules
📊 Business Logic Narrative
When the process 'Create V9 Event Segment' is invoked, and assuming that m10 segment is completed with all required data, when the system creates v9 event segment, the desired outcome is that v9 segment structure is created and ready to receive event data.
💻 Technical Criteria
Given M10 segment is completed with all required data
When The system creates V9 event segment
Then V9 segment structure is created and ready to receive event data
R-GCX016E-cbl-02811 Set Event Date and Time
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Event Date and Time' is invoked, and assuming that event code is set in v9 segment, when the system sets event date and time, the desired outcome is that event date and time fields are populated with current timestamp.
💻 Technical Criteria
Given Event code is set in V9 segment
When The system sets event date and time
Then Event date and time fields are populated with current timestamp
R-GCX016E-cbl-02814 Validate Segment Data
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Segment Data' is invoked, and assuming that m10 and v9 segments are populated with data, when the system validates segment data, the desired outcome is that all required fields are verified for completeness and accuracy.
💻 Technical Criteria
Given M10 and V9 segments are populated with data
When The system validates segment data
Then All required fields are verified for completeness and accuracy
🏷️ CCN & Waybill Identification 219 logic blocks
R-GCX016E-cbl-00024 Cargo Lookup Method?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Lookup Method?' is invoked, and assuming that x4 segment contains disposition code and processing parameters, when processing type is by car id and waybill, the desired outcome is that route to car/waybill-based cargo processing.
💻 Technical Criteria
Given X4 segment contains disposition code and processing parameters
When Processing type is by car ID and waybill
Then Route to car/waybill-based cargo processing
R-GCX016E-cbl-00026 22:Cargo Processing by Car/Waybill
Process Rules
📊 Business Logic Narrative
When the process '22:Cargo Processing by Car/Waybill' is invoked, and assuming that disposition code requires car/waybill-based processing, when car id and waybill are identified from segments, the desired outcome is that process all cargos with matching car id and waybill.
💻 Technical Criteria
Given Disposition code requires car/waybill-based processing
When Car ID and waybill are identified from segments
Then Process all cargos with matching car ID and waybill
R-GCX016E-cbl-00028 42:S09 Status Segment Processing
Process Rules
📊 Business Logic Narrative
When the process '42:S09 Status Segment Processing' is invoked, and assuming that cargo requires status segment processing, when s09 segments are fetched for cargo, the desired outcome is that create or replace s09 segments for cargo records and manage status arrays with sequence numbers.
💻 Technical Criteria
Given Cargo requires status segment processing
When S09 segments are fetched for cargo
Then Create or replace S09 segments for cargo records and manage status arrays with sequence numbers
R-GCX016E-cbl-00038 57:Status Array Verification
Validation Rules
📊 Business Logic Narrative
When the process '57:Status Array Verification' is invoked, and assuming that status array has been updated with disposition codes, when status array verification is performed, the desired outcome is that verify status array integrity and sequence numbers.
💻 Technical Criteria
Given Status array has been updated with disposition codes
When Status array verification is performed
Then Verify status array integrity and sequence numbers
R-GCX016E-cbl-00041 65:Multi-Cargo Processing by Car/Waybill
Process Rules
📊 Business Logic Narrative
When the process '65:Multi-Cargo Processing by Car/Waybill' is invoked, and assuming that multiple cargos exist with same car id and waybill, when multi-cargo processing is initiated, the desired outcome is that process all related cargos and verify release status for each ccn.
💻 Technical Criteria
Given Multiple cargos exist with same car ID and waybill
When Multi-cargo processing is initiated
Then Process all related cargos and verify release status for each CCN
R-GCX016E-cbl-00048 77:Comprehensive Merlin Message Formatting
Process Rules
📊 Business Logic Narrative
When the process '77:Comprehensive Merlin Message Formatting' is invoked, and assuming that cargo processing requires merlin notification, when merlin message formatting is initiated, the desired outcome is that include disposition code messages unless manual/auto release, add car id, waybill, us ccn, date/time, special comments up to 3 lines, k1 comments up to 4 lines, and quantity impact information.
💻 Technical Criteria
Given Cargo processing requires Merlin notification
When Merlin message formatting is initiated
Then Include disposition code messages unless manual/auto release, add car ID, waybill, US CCN, date/time, special comments up to 3 lines, K1 comments up to 4 lines, and quantity impact information
R-GCX016E-cbl-00312 Extract Waybill Number from N7 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Waybill Number from N7 Segment' is invoked, and assuming that an n7 equipment segment contains waybill information, when the system processes the n7 segment for waybill data, the desired outcome is that the waybill number is extracted from the n7 segment.
💻 Technical Criteria
Given An N7 equipment segment contains waybill information
When The system processes the N7 segment for waybill data
Then The waybill number is extracted from the N7 segment
R-GCX016E-cbl-00314 Search Cargo Database by Car/Waybill Index
Action Rules
📊 Business Logic Narrative
When the process 'Search Cargo Database by Car/Waybill Index' is invoked, and assuming that a formatted car id and waybill number are available, when the system searches for existing cargo records, the desired outcome is that the system queries the cargo database using the car/waybill index to find matching records.
💻 Technical Criteria
Given A formatted car ID and waybill number are available
When The system searches for existing cargo records
Then The system queries the cargo database using the car/waybill index to find matching records
R-GCX016E-cbl-00315 Cargo Records Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Records Found?' is invoked, and assuming that a search has been performed on the cargo database using car id and waybill, when the system evaluates the search results, the desired outcome is that the system determines if cargo records were found and routes processing accordingly.
💻 Technical Criteria
Given A search has been performed on the cargo database using car ID and waybill
When The system evaluates the search results
Then The system determines if cargo records were found and routes processing accordingly
R-GCX016E-cbl-00316 Retrieve First Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve First Cargo Record' is invoked, and assuming that cargo records exist for the car id and waybill combination, when the system needs to begin processing cargo records, the desired outcome is that the first cargo record matching the criteria is retrieved for processing.
💻 Technical Criteria
Given Cargo records exist for the car ID and waybill combination
When The system needs to begin processing cargo records
Then The first cargo record matching the criteria is retrieved for processing
R-GCX016E-cbl-00318 More Records Exist?
Decision Rules
📊 Business Logic Narrative
When the process 'More Records Exist?' is invoked, and assuming that one cargo record has been processed for a car/waybill combination, when the system checks for additional matching records, the desired outcome is that the system determines if more cargo records exist with the same car id and waybill and continues processing if found.
💻 Technical Criteria
Given One cargo record has been processed for a car/waybill combination
When The system checks for additional matching records
Then The system determines if more cargo records exist with the same car ID and waybill and continues processing if found
R-GCX016E-cbl-00319 Retrieve Next Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Next Cargo Record' is invoked, and assuming that additional cargo records exist for the same car id and waybill combination, when the system continues processing multiple records, the desired outcome is that the next cargo record in the sequence is retrieved for processing.
💻 Technical Criteria
Given Additional cargo records exist for the same car ID and waybill combination
When The system continues processing multiple records
Then The next cargo record in the sequence is retrieved for processing
R-GCX016E-cbl-00320 Process Next Individual Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Process Next Individual Cargo Record' is invoked, and assuming that a subsequent cargo record has been retrieved for the same car/waybill combination, when the system processes this additional cargo record, the desired outcome is that the cargo record is processed with the same disposition codes, status updates, and business rule validations as previous records.
💻 Technical Criteria
Given A subsequent cargo record has been retrieved for the same car/waybill combination
When The system processes this additional cargo record
Then The cargo record is processed with the same disposition codes, status updates, and business rule validations as previous records
R-GCX016E-cbl-00321 CPRS Traffic?
Decision Rules
📊 Business Logic Narrative
When the process 'CPRS Traffic?' is invoked, and assuming that no existing cargo records were found for the car/waybill combination, when the system evaluates the traffic type, the desired outcome is that the system determines if this is cprs traffic and routes to appropriate processing.
💻 Technical Criteria
Given No existing cargo records were found for the car/waybill combination
When The system evaluates the traffic type
Then The system determines if this is CPRS traffic and routes to appropriate processing
R-GCX016E-cbl-00323 Log Car/Waybill Processing Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Car/Waybill Processing Action' is invoked, and assuming that car/waybill processing has been completed, when the system finalizes the processing step, the desired outcome is that the processing actions and results are logged for audit trail and business tracking purposes.
💻 Technical Criteria
Given Car/waybill processing has been completed
When The system finalizes the processing step
Then The processing actions and results are logged for audit trail and business tracking purposes
R-GCX016E-cbl-02899 Extract Car ID and Waybill from X4 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Car ID and Waybill from X4 Segment' is invoked, and assuming that an x4 segment contains equipment and waybill information, when the system processes the x4 segment for car/waybill search, the desired outcome is that car id and waybill number are extracted and prepared for database search.
💻 Technical Criteria
Given An X4 segment contains equipment and waybill information
When The system processes the X4 segment for car/waybill search
Then Car ID and waybill number are extracted and prepared for database search
R-GCX016E-cbl-02901 Search Cargo Database by Car/Waybill Index
Action Rules
📊 Business Logic Narrative
When the process 'Search Cargo Database by Car/Waybill Index' is invoked, and assuming that a formatted car id and waybill number are available for search, when the system searches the cargo database, the desired outcome is that database is searched using car/waybill index to locate existing cargo records.
💻 Technical Criteria
Given A formatted car ID and waybill number are available for search
When The system searches the cargo database
Then Database is searched using car/waybill index to locate existing cargo records
R-GCX016E-cbl-02902 Cargo Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Found?' is invoked, and assuming that a database search has been performed using car id and waybill, when the system evaluates the search results, the desired outcome is that system determines if cargo records exist and routes processing accordingly.
💻 Technical Criteria
Given A database search has been performed using car ID and waybill
When The system evaluates the search results
Then System determines if cargo records exist and routes processing accordingly
R-GCX016E-cbl-02903 Retrieve First Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve First Cargo Record' is invoked, and assuming that cargo records exist for the car id and waybill combination, when the system needs to process the cargo, the desired outcome is that the first cargo record is retrieved and prepared for processing.
💻 Technical Criteria
Given Cargo records exist for the car ID and waybill combination
When The system needs to process the cargo
Then The first cargo record is retrieved and prepared for processing
R-GCX016E-cbl-02904 Check for Additional Records with Same Car/Waybill
Process Rules
📊 Business Logic Narrative
When the process 'Check for Additional Records with Same Car/Waybill' is invoked, and assuming that a first cargo record has been retrieved for a car id and waybill, when the system checks for additional records, the desired outcome is that all cargo records with the same car id and waybill are identified for processing.
💻 Technical Criteria
Given A first cargo record has been retrieved for a car ID and waybill
When The system checks for additional records
Then All cargo records with the same car ID and waybill are identified for processing
R-GCX016E-cbl-02905 CPRS Traffic?
Decision Rules
📊 Business Logic Narrative
When the process 'CPRS Traffic?' is invoked, and assuming that no existing cargo records are found for the car id and waybill, when the system evaluates the traffic type, the desired outcome is that system determines if this is cprs traffic requiring special processing rules.
💻 Technical Criteria
Given No existing cargo records are found for the car ID and waybill
When The system evaluates the traffic type
Then System determines if this is CPRS traffic requiring special processing rules
R-GCX016E-cbl-02908 Perform US-CCN Key Renumbering
Computation Rules
📊 Business Logic Narrative
When the process 'Perform US-CCN Key Renumbering' is invoked, and assuming that cprs cargo requires key renumbering due to scac validation results, when the system processes the ccn key, the desired outcome is that us-ccn key is renumbered according to cprs business rules to ensure unique identification.
💻 Technical Criteria
Given CPRS cargo requires key renumbering due to SCAC validation results
When The system processes the CCN key
Then US-CCN key is renumbered according to CPRS business rules to ensure unique identification
R-GCX016E-cbl-02915 Return Cargo Record for Processing
Process Rules
📊 Business Logic Narrative
When the process 'Return Cargo Record for Processing' is invoked, and assuming that a cargo record has been found or created through the search process, when the system completes the car/waybill database search, the desired outcome is that cargo record is returned to the calling process for disposition code processing and status updates.
💻 Technical Criteria
Given A cargo record has been found or created through the search process
When The system completes the car/waybill database search
Then Cargo record is returned to the calling process for disposition code processing and status updates
R-GCX016E-cbl-03161 Cargo Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Found?' is invoked, and assuming that car id search has been performed for cprs cargo, when the system evaluates search results, the desired outcome is that if cargo record is found, use existing cargo record, otherwise proceed to us-ccn key requirements check.
💻 Technical Criteria
Given car ID search has been performed for CPRS cargo
When the system evaluates search results
Then if cargo record is found, use existing cargo record, otherwise proceed to US-CCN key requirements check
R-GCX016E-cbl-03162 US-CCN Key Renumbering Needed?
Decision Rules
📊 Business Logic Narrative
When the process 'US-CCN Key Renumbering Needed?' is invoked, and assuming that no existing cargo record was found and us-ccn key requirements are being checked, when the system evaluates us-ccn key renumbering requirements, the desired outcome is that if renumbering is needed, renumber us-ccn key, otherwise keep original us-ccn key.
💻 Technical Criteria
Given no existing cargo record was found and US-CCN key requirements are being checked
When the system evaluates US-CCN key renumbering requirements
Then if renumbering is needed, renumber US-CCN key, otherwise keep original US-CCN key
R-GCX016E-cbl-03163 Renumber US-CCN Key
Action Rules
📊 Business Logic Narrative
When the process 'Renumber US-CCN Key' is invoked, and assuming that us-ccn key renumbering has been determined as necessary, when the system performs key renumbering, the desired outcome is that generate new us-ccn key value and update cargo identification.
💻 Technical Criteria
Given US-CCN key renumbering has been determined as necessary
When the system performs key renumbering
Then generate new US-CCN key value and update cargo identification
R-GCX016E-cbl-03164 Apply CPRS Cargo Creation Rules
Policy Rules
📊 Business Logic Narrative
When the process 'Apply CPRS Cargo Creation Rules' is invoked, and assuming that us-ccn key processing is complete for new cprs cargo, when the system applies cprs-specific cargo creation rules, the desired outcome is that enforce cprs business rules and validation requirements for cargo creation.
💻 Technical Criteria
Given US-CCN key processing is complete for new CPRS cargo
When the system applies CPRS-specific cargo creation rules
Then enforce CPRS business rules and validation requirements for cargo creation
R-GCX016E-cbl-00324 Cargo Found in System?
Validation Rules
📊 Business Logic Narrative
When the process 'Cargo Found in System?' is invoked, and assuming that a cargo ccn (container control number) is provided for processing, when the system searches for the cargo record in the database, the desired outcome is that if the cargo record is found, proceed with processing; if not found, generate an error message indicating cargo not available.
💻 Technical Criteria
Given A cargo CCN (Container Control Number) is provided for processing
When The system searches for the cargo record in the database
Then If the cargo record is found, proceed with processing; if not found, generate an error message indicating cargo not available
R-GCX016E-cbl-02920 157: Status Array Management and Processing
Process Rules
📊 Business Logic Narrative
When the process '157: Status Array Management and Processing' is invoked, and assuming that disposition codes have been added or removed from the status array, when the system completes the array modification operations, the desired outcome is that reorganize the status array sequence numbers to maintain consecutive numbering and update the total count of active status codes.
💻 Technical Criteria
Given Disposition codes have been added or removed from the status array
When The system completes the array modification operations
Then Reorganize the status array sequence numbers to maintain consecutive numbering and update the total count of active status codes
R-GCX016E-cbl-03181 Update Array Sequence Numbers
Process Rules
📊 Business Logic Narrative
When the process 'Update Array Sequence Numbers' is invoked, and assuming that the status array has been compressed after code removal, when the system updates sequence numbers, the desired outcome is that all remaining disposition codes are assigned sequential numbers starting from 1.
💻 Technical Criteria
Given The status array has been compressed after code removal
When The system updates sequence numbers
Then All remaining disposition codes are assigned sequential numbers starting from 1
R-GCX016E-cbl-03182 Validate Array Integrity
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Array Integrity' is invoked, and assuming that the status array has been modified through code removal and compression, when the system validates array integrity, the desired outcome is that the array structure is verified for proper sequence numbers, valid codes, and data consistency.
💻 Technical Criteria
Given The status array has been modified through code removal and compression
When The system validates array integrity
Then The array structure is verified for proper sequence numbers, valid codes, and data consistency
R-GCX016E-cbl-00398 Include Waybill Information
Process Rules
📊 Business Logic Narrative
When the process 'Include Waybill Information' is invoked, and assuming that equipment details have been included in the email, when the system adds waybill information to the email, the desired outcome is that the email includes waybill numbers and associated shipping documentation details.
💻 Technical Criteria
Given Equipment details have been included in the email
When The system adds waybill information to the email
Then The email includes waybill numbers and associated shipping documentation details
R-GCX016E-cbl-00399 Include CCN and Content Description
Process Rules
📊 Business Logic Narrative
When the process 'Include CCN and Content Description' is invoked, and assuming that waybill information has been included in the email, when the system adds ccn and content information to the email, the desired outcome is that the email includes the cargo control number and detailed description of cargo contents.
💻 Technical Criteria
Given Waybill information has been included in the email
When The system adds CCN and content information to the email
Then The email includes the Cargo Control Number and detailed description of cargo contents
R-GCX016E-cbl-00400 Include Origin/Destination Stations
Process Rules
📊 Business Logic Narrative
When the process 'Include Origin/Destination Stations' is invoked, and assuming that ccn and content description have been included in the email, when the system adds location information to the email, the desired outcome is that the email includes origin station, destination station, and routing information.
💻 Technical Criteria
Given CCN and content description have been included in the email
When The system adds location information to the email
Then The email includes origin station, destination station, and routing information
R-GCX016E-cbl-00411 Track Maximum Sequence Numbers
Validation Rules
📊 Business Logic Narrative
When the process 'Track Maximum Sequence Numbers' is invoked, and assuming that status arrays contain existing disposition code entries, when processing status array data, the desired outcome is that the system identifies and tracks the maximum sequence number for each status array type to determine the next available sequence number for new entries.
💻 Technical Criteria
Given Status arrays contain existing disposition code entries
When Processing status array data
Then The system identifies and tracks the maximum sequence number for each status array type to determine the next available sequence number for new entries
R-GCX016E-cbl-00414 Update Existing Status Entry
Process Rules
📊 Business Logic Narrative
When the process 'Update Existing Status Entry' is invoked, and assuming that a disposition code matches an existing entry in the status array, when processing the disposition code update, the desired outcome is that the system updates the existing status array entry with new quantity, date/time, and other relevant information while maintaining the original sequence number.
💻 Technical Criteria
Given A disposition code matches an existing entry in the status array
When Processing the disposition code update
Then The system updates the existing status array entry with new quantity, date/time, and other relevant information while maintaining the original sequence number
R-GCX016E-cbl-00423 Lead Manifest CCN differs from US CCN Key?
Decision Rules
📊 Business Logic Narrative
When the process 'Lead Manifest CCN differs from US CCN Key?' is invoked, and assuming that a follower manifest is identified for processing and a lead manifest ccn exists, when the lead manifest ccn is compared to the current us ccn key, the desired outcome is that if the lead manifest ccn differs from the us ccn key, special action processing is initiated, otherwise standard follower processing continues.
💻 Technical Criteria
Given A follower manifest is identified for processing AND a lead manifest CCN exists
When The lead manifest CCN is compared to the current US CCN key
Then If the lead manifest CCN differs from the US CCN key, special action processing is initiated, otherwise standard follower processing continues
R-GCX016E-cbl-00424 Prepare 350 Special Action Messages
Process Rules
📊 Business Logic Narrative
When the process 'Prepare 350 Special Action Messages' is invoked, and assuming that a follower manifest requires processing and the lead manifest ccn differs from us ccn and the message type is gcw016, when the system prepares the follower manifest message, the desired outcome is that a special action code of 350 is set in the message for proper routing and processing.
💻 Technical Criteria
Given A follower manifest requires processing AND the lead manifest CCN differs from US CCN AND the message type is GCW016
When The system prepares the follower manifest message
Then A special action code of 350 is set in the message for proper routing and processing
R-GCX016E-cbl-00470 Apply CPRS Special Processing
Process Rules
📊 Business Logic Narrative
When the process 'Apply CPRS Special Processing' is invoked, and assuming that cargo is identified as cprs traffic and no initial record was found, when cprs special processing is triggered, the desired outcome is that the system handles scac unknown scenarios and performs us-ccn key renumbering for cprs-specific lookup.
💻 Technical Criteria
Given Cargo is identified as CPRS traffic and no initial record was found
When CPRS special processing is triggered
Then The system handles SCAC unknown scenarios and performs US-CCN key renumbering for CPRS-specific lookup
R-GCX016E-cbl-00472 Perform US-CCN Key Renumbering
Computation Rules
📊 Business Logic Narrative
When the process 'Perform US-CCN Key Renumbering' is invoked, and assuming that cprs traffic requires special key handling, when us-ccn key renumbering is performed, the desired outcome is that the system creates an updated lookup key using cprs-specific numbering rules.
💻 Technical Criteria
Given CPRS traffic requires special key handling
When US-CCN key renumbering is performed
Then The system creates an updated lookup key using CPRS-specific numbering rules
R-GCX016E-cbl-00473 Search Again with Updated Key
Action Rules
📊 Business Logic Narrative
When the process 'Search Again with Updated Key' is invoked, and assuming that a renumbered us-ccn key has been created for cprs traffic, when the system searches the database again, the desired outcome is that the system queries the cargo database using the updated cprs key.
💻 Technical Criteria
Given A renumbered US-CCN key has been created for CPRS traffic
When The system searches the database again
Then The system queries the cargo database using the updated CPRS key
R-GCX016E-cbl-00483 Build Car/Waybill Search Key
Definitional Rules
📊 Business Logic Narrative
When the process 'Build Car/Waybill Search Key' is invoked, and assuming that formatted car id and waybill number are available, when system prepares to search for cargo records, the desired outcome is that system builds composite search key using car id and waybill number combination.
💻 Technical Criteria
Given Formatted car ID and waybill number are available
When System prepares to search for cargo records
Then System builds composite search key using car ID and waybill number combination
R-GCX016E-cbl-00484 Search GCSUSRT Database by Car/Waybill Index
Action Rules
📊 Business Logic Narrative
When the process 'Search GCSUSRT Database by Car/Waybill Index' is invoked, and assuming that car/waybill search key is constructed, when system searches gcsusrt database using car/waybill index, the desired outcome is that system retrieves cargo records matching the car/waybill combination.
💻 Technical Criteria
Given Car/waybill search key is constructed
When System searches GCSUSRT database using car/waybill index
Then System retrieves cargo records matching the car/waybill combination
R-GCX016E-cbl-00485 First Cargo Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'First Cargo Record Found?' is invoked, and assuming that database search for car/waybill combination is completed, when system checks search results, the desired outcome is that system determines if first cargo record exists and proceeds with retrieval or handles not found scenario.
💻 Technical Criteria
Given Database search for car/waybill combination is completed
When System checks search results
Then System determines if first cargo record exists and proceeds with retrieval or handles not found scenario
R-GCX016E-cbl-00486 Retrieve First Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve First Cargo Record' is invoked, and assuming that first cargo record exists for car/waybill combination, when system retrieves the first matching cargo record, the desired outcome is that system loads cargo record data for processing.
💻 Technical Criteria
Given First cargo record exists for car/waybill combination
When System retrieves the first matching cargo record
Then System loads cargo record data for processing
R-GCX016E-cbl-00488 Search for Additional Records with Same Car/Waybill
Action Rules
📊 Business Logic Narrative
When the process 'Search for Additional Records with Same Car/Waybill' is invoked, and assuming that first cargo record is processed and stored, when system searches for additional records with same car/waybill, the desired outcome is that system identifies all remaining cargo records with matching car/waybill combination.
💻 Technical Criteria
Given First cargo record is processed and stored
When System searches for additional records with same car/waybill
Then System identifies all remaining cargo records with matching car/waybill combination
R-GCX016E-cbl-00490 Retrieve Next Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Next Cargo Record' is invoked, and assuming that additional cargo records exist for car/waybill combination, when system retrieves next matching cargo record, the desired outcome is that system loads additional cargo record data for processing.
💻 Technical Criteria
Given Additional cargo records exist for car/waybill combination
When System retrieves next matching cargo record
Then System loads additional cargo record data for processing
R-GCX016E-cbl-00492 CPRS Traffic?
Decision Rules
📊 Business Logic Narrative
When the process 'CPRS Traffic?' is invoked, and assuming that all cargo records for car/waybill combination are collected, when system checks cargo characteristics for cprs traffic indicators, the desired outcome is that system determines if cprs special handling rules should be applied.
💻 Technical Criteria
Given All cargo records for car/waybill combination are collected
When System checks cargo characteristics for CPRS traffic indicators
Then System determines if CPRS special handling rules should be applied
R-GCX016E-cbl-00496 Handle Cargo Not Found Scenario
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Handle Cargo Not Found Scenario', assuming that no cargo records exist for the specified car/waybill combination, when system handles cargo not found scenario, the desired outcome is that system logs the not found condition and continues processing without cargo records.
💻 Technical Criteria
EXCLUDING No cargo records exist for the specified car/waybill combination
When System handles cargo not found scenario
Then System logs the not found condition and continues processing without cargo records
R-GCX016E-cbl-00508 Add Equipment Details
Process Rules
📊 Business Logic Narrative
When the process 'Add Equipment Details' is invoked, and assuming that a log message has timestamp information added, when the system adds equipment details to the log message, the desired outcome is that the system must include equipment id, waybill number, and us-ccn in the log message.
💻 Technical Criteria
Given A log message has timestamp information added
When The system adds equipment details to the log message
Then The system must include equipment ID, waybill number, and US-CCN in the log message
R-GCX016E-cbl-00536 Add Waybill Information to Error
Process Rules
📊 Business Logic Narrative
When the process 'Add Waybill Information to Error' is invoked, and assuming that the error message includes equipment details, when waybill information is available, the desired outcome is that waybill information is added to the error message.
💻 Technical Criteria
Given The error message includes equipment details
When Waybill information is available
Then Waybill information is added to the error message
R-GCX016E-cbl-00569 Phase 1: Search with Partial CCN and Car ID
Process Rules
📊 Business Logic Narrative
When the process 'Phase 1: Search with Partial CCN and Car ID' is invoked, and assuming that a formatted car id and partial ccn are available for cargo search, when the system searches the us cargo root segments using both partial ccn and car id as search criteria, the desired outcome is that the system returns cargo records that match both the partial ccn and car id combination.
💻 Technical Criteria
Given A formatted car ID and partial CCN are available for cargo search
When The system searches the US cargo root segments using both partial CCN and car ID as search criteria
Then The system returns cargo records that match both the partial CCN and car ID combination
R-GCX016E-cbl-00570 Cargo Found with Partial CCN?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Found with Partial CCN?' is invoked, and assuming that a search has been performed using partial ccn and car id, when the system evaluates the search results, the desired outcome is that if cargo records are found, proceed to return found cargo; if no records found, initiate secondary search phase.
💻 Technical Criteria
Given A search has been performed using partial CCN and car ID
When The system evaluates the search results
Then If cargo records are found, proceed to return found cargo; if no records found, initiate secondary search phase
R-GCX016E-cbl-00571 Phase 2: Search with Car ID Only
Process Rules
📊 Business Logic Narrative
When the process 'Phase 2: Search with Car ID Only' is invoked, and assuming that primary search with partial ccn and car id found no matching cargo records, when the system searches the us cargo root segments using only car id as search criteria, the desired outcome is that the system returns all cargo records that match the car id regardless of ccn.
💻 Technical Criteria
Given Primary search with partial CCN and car ID found no matching cargo records
When The system searches the US cargo root segments using only car ID as search criteria
Then The system returns all cargo records that match the car ID regardless of CCN
R-GCX016E-cbl-00573 Handle SCAC Unknown Scenarios
Process Rules
📊 Business Logic Narrative
When the process 'Handle SCAC Unknown Scenarios' is invoked, and assuming that cargo records were found using car id only search and scac information may be unknown, when the system processes the found cargo records, the desired outcome is that the system handles scac unknown scenarios and prepares cargo for ccn key renumbering.
💻 Technical Criteria
Given Cargo records were found using car ID only search and SCAC information may be unknown
When The system processes the found cargo records
Then The system handles SCAC unknown scenarios and prepares cargo for CCN key renumbering
R-GCX016E-cbl-00574 Perform US-CCN Key Renumbering
Action Rules
📊 Business Logic Narrative
When the process 'Perform US-CCN Key Renumbering' is invoked, and assuming that cargo records require ccn key renumbering due to scac unknown scenarios, when the system performs us-ccn key renumbering process, the desired outcome is that the cargo records are updated with proper ccn keys for accurate cargo tracking.
💻 Technical Criteria
Given Cargo records require CCN key renumbering due to SCAC unknown scenarios
When The system performs US-CCN key renumbering process
Then The cargo records are updated with proper CCN keys for accurate cargo tracking
R-GCX016E-cbl-00583 Track Maximum Sequence Numbers
Computation Rules
📊 Business Logic Narrative
When the process 'Track Maximum Sequence Numbers' is invoked, and assuming that status arrays are populated from database segments, when the system processes sequence numbers, the desired outcome is that the maximum sequence number is tracked for future segment creation.
💻 Technical Criteria
Given Status arrays are populated from database segments
When The system processes sequence numbers
Then The maximum sequence number is tracked for future segment creation
R-GCX016E-cbl-02959 Track Maximum Sequence Number
Computation Rules
📊 Business Logic Narrative
When the process 'Track Maximum Sequence Number' is invoked, and assuming that status segments are being processed from the database, when each segment is converted to array format, the desired outcome is that the system tracks and updates the maximum sequence number encountered.
💻 Technical Criteria
Given Status segments are being processed from the database
When Each segment is converted to array format
Then The system tracks and updates the maximum sequence number encountered
R-GCX016E-cbl-03222 Valid Segment Format?
Decision Rules
📊 Business Logic Narrative
When the process 'Valid Segment Format?' is invoked, and assuming that the s09 segment format structure has been examined, when the system evaluates format validity, the desired outcome is that if format is valid, proceed to sequence number verification, otherwise log format error and attempt reconstruction.
💻 Technical Criteria
Given The S09 segment format structure has been examined
When The system evaluates format validity
Then If format is valid, proceed to sequence number verification, otherwise log format error and attempt reconstruction
R-GCX016E-cbl-03223 Verify Sequence Numbers
Validation Rules
📊 Business Logic Narrative
When the process 'Verify Sequence Numbers' is invoked, and assuming that an s09 segment with valid format structure, when the system checks sequence numbers within the segment, the desired outcome is that sequence numbers are verified for proper ordering and valid ranges.
💻 Technical Criteria
Given An S09 segment with valid format structure
When The system checks sequence numbers within the segment
Then Sequence numbers are verified for proper ordering and valid ranges
R-GCX016E-cbl-03224 Sequence Numbers Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Sequence Numbers Valid?' is invoked, and assuming that sequence numbers in s09 segment have been verified, when the system evaluates sequence number validity, the desired outcome is that if sequence numbers are valid, proceed to data integrity check, otherwise log sequence error and correct numbering.
💻 Technical Criteria
Given Sequence numbers in S09 segment have been verified
When The system evaluates sequence number validity
Then If sequence numbers are valid, proceed to data integrity check, otherwise log sequence error and correct numbering
R-GCX016E-cbl-03225 Check Data Integrity Fields
Validation Rules
📊 Business Logic Narrative
When the process 'Check Data Integrity Fields' is invoked, and assuming that an s09 segment with valid format and sequence numbers, when the system examines data integrity fields, the desired outcome is that data integrity is validated against consistency and completeness requirements.
💻 Technical Criteria
Given An S09 segment with valid format and sequence numbers
When The system examines data integrity fields
Then Data integrity is validated against consistency and completeness requirements
R-GCX016E-cbl-03227 Initialize Status Array from Valid Segment
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Status Array from Valid Segment' is invoked, and assuming that a valid s09 segment with proper format, sequence numbers, and data integrity, when the system initializes the status array, the desired outcome is that status array is populated with disposition codes and status information from the segment.
💻 Technical Criteria
Given A valid S09 segment with proper format, sequence numbers, and data integrity
When The system initializes the status array
Then Status array is populated with disposition codes and status information from the segment
R-GCX016E-cbl-03228 Track Maximum Sequence Fetched
Process Rules
📊 Business Logic Narrative
When the process 'Track Maximum Sequence Fetched' is invoked, and assuming that status array has been initialized from valid s09 segment, when the system processes sequence numbers, the desired outcome is that the maximum sequence number encountered is recorded for future reference.
💻 Technical Criteria
Given Status array has been initialized from valid S09 segment
When The system processes sequence numbers
Then The maximum sequence number encountered is recorded for future reference
R-GCX016E-cbl-03235 Log Sequence Number Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Sequence Number Error', assuming that sequence number validation has failed, when the system detects invalid sequence numbers, the desired outcome is that sequence number error is logged and correction procedures are initiated.
💻 Technical Criteria
EXCLUDING Sequence number validation has failed
When The system detects invalid sequence numbers
Then Sequence number error is logged and correction procedures are initiated
R-GCX016E-cbl-03236 Correct Sequence Numbering
Process Rules
📊 Business Logic Narrative
When the process 'Correct Sequence Numbering' is invoked, and assuming that invalid sequence numbers have been detected and logged, when the system applies sequence number corrections, the desired outcome is that sequence numbers are corrected and processing continues to data integrity check.
💻 Technical Criteria
Given Invalid sequence numbers have been detected and logged
When The system applies sequence number corrections
Then Sequence numbers are corrected and processing continues to data integrity check
R-GCX016E-cbl-03385 Extract Sequence Number from Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Sequence Number from Segment' is invoked, and assuming that a valid status segment is being processed, when the system extracts the sequence number from the segment, the desired outcome is that the system should identify and capture the sequence number for proper array ordering.
💻 Technical Criteria
Given A valid status segment is being processed
When The system extracts the sequence number from the segment
Then The system should identify and capture the sequence number for proper array ordering
R-GCX016E-cbl-03386 Populate Array Entry with Segment Data
Process Rules
📊 Business Logic Narrative
When the process 'Populate Array Entry with Segment Data' is invoked, and assuming that a valid status segment with extracted sequence number is available, when the system populates the array entry with segment data, the desired outcome is that the system should transfer all relevant status information from the segment into the appropriate array position.
💻 Technical Criteria
Given A valid status segment with extracted sequence number is available
When The system populates the array entry with segment data
Then The system should transfer all relevant status information from the segment into the appropriate array position
R-GCX016E-cbl-03387 Track Maximum Sequence Number
Process Rules
📊 Business Logic Narrative
When the process 'Track Maximum Sequence Number' is invoked, and assuming that status segments are being processed with sequence numbers, when the system tracks the maximum sequence number, the desired outcome is that the system should maintain the highest sequence number encountered for array boundary management.
💻 Technical Criteria
Given Status segments are being processed with sequence numbers
When The system tracks the maximum sequence number
Then The system should maintain the highest sequence number encountered for array boundary management
R-GCX016E-cbl-03495 Validate Data Consistency
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Data Consistency' is invoked, and assuming that s09 segment has complete and valid fields, when the system validates data consistency across segment fields, the desired outcome is that all data values must be consistent and logically coherent to proceed to sequence number validation.
💻 Technical Criteria
Given S09 segment has complete and valid fields
When The system validates data consistency across segment fields
Then All data values must be consistent and logically coherent to proceed to sequence number validation
R-GCX016E-cbl-03496 Data Consistent?
Decision Rules
📊 Business Logic Narrative
When the process 'Data Consistent?' is invoked, and assuming that s09 segment data consistency has been validated, when the system evaluates data consistency, the desired outcome is that if data is consistent, proceed to sequence number validation, otherwise log validation error.
💻 Technical Criteria
Given S09 segment data consistency has been validated
When The system evaluates data consistency
Then If data is consistent, proceed to sequence number validation, otherwise log validation error
R-GCX016E-cbl-03497 Validate Sequence Numbers
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Sequence Numbers' is invoked, and assuming that s09 segment has consistent data values, when the system validates sequence numbers, the desired outcome is that sequence numbers must be properly ordered and within valid ranges to proceed to status code validation.
💻 Technical Criteria
Given S09 segment has consistent data values
When The system validates sequence numbers
Then Sequence numbers must be properly ordered and within valid ranges to proceed to status code validation
R-GCX016E-cbl-03498 Sequences Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Sequences Valid?' is invoked, and assuming that s09 segment sequence numbers have been validated, when the system evaluates sequence validity, the desired outcome is that if sequences are valid, proceed to status code validation, otherwise log validation error.
💻 Technical Criteria
Given S09 segment sequence numbers have been validated
When The system evaluates sequence validity
Then If sequences are valid, proceed to status code validation, otherwise log validation error
R-GCX016E-cbl-03499 Validate Status Code Values
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Status Code Values' is invoked, and assuming that s09 segment has valid sequence numbers, when the system validates status code values, the desired outcome is that all status codes must be valid and recognized to proceed to segment approval.
💻 Technical Criteria
Given S09 segment has valid sequence numbers
When The system validates status code values
Then All status codes must be valid and recognized to proceed to segment approval
R-GCX016E-cbl-02981 Set Segment Sequence Number
Computation Rules
📊 Business Logic Narrative
When the process 'Set Segment Sequence Number' is invoked, and assuming that database segment is being prepared for storage, when sequence number assignment is performed, the desired outcome is that segment receives correct sequence number for database ordering.
💻 Technical Criteria
Given Database segment is being prepared for storage
When Sequence number assignment is performed
Then Segment receives correct sequence number for database ordering
R-GCX016E-cbl-00598 Disposition Code Match?
Decision Rules
📊 Business Logic Narrative
When the process 'Disposition Code Match?' is invoked, and assuming that a new disposition code and an existing status array entry, when the system compares the disposition code values, the desired outcome is that if the disposition codes match exactly, proceed to sequence number validation, otherwise continue to next array entry.
💻 Technical Criteria
Given A new disposition code and an existing status array entry
When The system compares the disposition code values
Then If the disposition codes match exactly, proceed to sequence number validation, otherwise continue to next array entry
R-GCX016E-cbl-00599 Same Sequence Number?
Validation Rules
📊 Business Logic Narrative
When the process 'Same Sequence Number?' is invoked, and assuming that two disposition codes that match and their respective sequence numbers, when the system compares the sequence numbers of the matching disposition codes, the desired outcome is that if sequence numbers are identical, mark as exact duplicate found, otherwise check date/time stamps for partial match.
💻 Technical Criteria
Given Two disposition codes that match and their respective sequence numbers
When The system compares the sequence numbers of the matching disposition codes
Then If sequence numbers are identical, mark as exact duplicate found, otherwise check date/time stamps for partial match
R-GCX016E-cbl-00600 Same Date/Time?
Validation Rules
📊 Business Logic Narrative
When the process 'Same Date/Time?' is invoked, and assuming that two matching disposition codes with different sequence numbers and their date/time stamps, when the system compares the date and time stamp values, the desired outcome is that if date/time stamps are identical, mark as duplicate with different time, otherwise continue search process.
💻 Technical Criteria
Given Two matching disposition codes with different sequence numbers and their date/time stamps
When The system compares the date and time stamp values
Then If date/time stamps are identical, mark as duplicate with different time, otherwise continue search process
R-GCX016E-cbl-00603 Log Duplicate Information
Process Rules
📊 Business Logic Narrative
When the process 'Log Duplicate Information' is invoked, and assuming that a confirmed duplicate disposition code with its details, when the system needs to record the duplicate detection event, the desired outcome is that log the duplicate disposition code information including sequence numbers, date/time stamps, and duplicate type for audit trail.
💻 Technical Criteria
Given A confirmed duplicate disposition code with its details
When The system needs to record the duplicate detection event
Then Log the duplicate disposition code information including sequence numbers, date/time stamps, and duplicate type for audit trail
R-GCX016E-cbl-00608 Update Status Array Sequence Numbers
Process Rules
📊 Business Logic Narrative
When the process 'Update Status Array Sequence Numbers' is invoked, and assuming that disposition codes have been removed from the cargo status array, when the removal process is complete and gaps exist in the sequence numbering, the desired outcome is that the system renumbers all remaining disposition codes in sequential order and maintains proper array indexing.
💻 Technical Criteria
Given Disposition codes have been removed from the cargo status array
When The removal process is complete AND gaps exist in the sequence numbering
Then The system renumbers all remaining disposition codes in sequential order AND maintains proper array indexing
R-GCX016E-cbl-00611 Validate Status Array Integrity
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Status Array Integrity' is invoked, and assuming that counterpart disposition codes have been removed from the status array, when the removal and reorganization process is complete, the desired outcome is that the system validates that no conflicting codes remain and all sequence numbers are properly ordered and the array structure is consistent.
💻 Technical Criteria
Given Counterpart disposition codes have been removed from the status array
When The removal and reorganization process is complete
Then The system validates that no conflicting codes remain AND all sequence numbers are properly ordered AND the array structure is consistent
R-GCX016E-cbl-00616 Add Manual Release Code to Status Array
Action Rules
📊 Business Logic Narrative
When the process 'Add Manual Release Code to Status Array' is invoked, and assuming that counterpart hold codes have been removed and no duplicates exist, when the system processes the manual release code, the desired outcome is that the manual release code is added to the cargo's status array with appropriate sequence number.
💻 Technical Criteria
Given Counterpart hold codes have been removed and no duplicates exist
When The system processes the manual release code
Then The manual release code is added to the cargo's status array with appropriate sequence number
R-GCX016E-cbl-00628 Locate Disposition Code Position
Process Rules
📊 Business Logic Narrative
When the process 'Locate Disposition Code Position' is invoked, and assuming that a disposition code that exists in the cargo status array, when the system searches through the status array entries, the desired outcome is that the system must locate the exact array position and sequence number of the target disposition code.
💻 Technical Criteria
Given A disposition code that exists in the cargo status array
When The system searches through the status array entries
Then The system must locate the exact array position and sequence number of the target disposition code
R-GCX016E-cbl-00650 Add Hold Code to Status Array
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Add Hold Code to Status Array', assuming that a hold disposition code is validated and not a duplicate, when the system processes the hold code addition, the desired outcome is that the hold code is added to the status array with sequence number, entry number, quantity, location, and date/time information.
💻 Technical Criteria
EXCLUDING A hold disposition code is validated and not a duplicate
When The system processes the hold code addition
Then The hold code is added to the status array with sequence number, entry number, quantity, location, and date/time information
R-GCX016E-cbl-00651 Add Release Code to Status Array
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Add Release Code to Status Array', assuming that a release disposition code is validated and not a duplicate, when the system processes the release code addition, the desired outcome is that the release code is added to the status array with sequence number, entry number, release quantity, location, and date/time information.
💻 Technical Criteria
EXCLUDING A release disposition code is validated and not a duplicate
When The system processes the release code addition
Then The release code is added to the status array with sequence number, entry number, release quantity, location, and date/time information
R-GCX016E-cbl-00665 Update Status Array Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Update Status Array Sequence' is invoked, and assuming that hold or release codes have been added or removed from the status array, when the system updates status array sequencing, the desired outcome is that all status array entries are renumbered with proper sequence numbers and the array count is updated.
💻 Technical Criteria
Given Hold or release codes have been added or removed from the status array
When The system updates status array sequencing
Then All status array entries are renumbered with proper sequence numbers and the array count is updated
R-GCX016E-cbl-00724 Multiple Cargo Records with Same Car/Waybill?
Decision Rules
📊 Business Logic Narrative
When the process 'Multiple Cargo Records with Same Car/Waybill?' is invoked, and assuming that destination index has been cleared for the cargo, when system checks for related cargo records, the desired outcome is that system identifies if multiple cargo records exist with the same car id and waybill number and processes them as a batch if found, otherwise processes single cargo.
💻 Technical Criteria
Given Destination index has been cleared for the cargo
When System checks for related cargo records
Then System identifies if multiple cargo records exist with the same car ID and waybill number and processes them as a batch if found, otherwise processes single cargo
R-GCX016E-cbl-00725 Process All Related Cargo Records
Process Rules
📊 Business Logic Narrative
When the process 'Process All Related Cargo Records' is invoked, and assuming that multiple cargo records with same car id and waybill have been identified, when batch processing is initiated, the desired outcome is that system applies the same arrival cancellation processing to all related cargo records with matching car id and waybill number.
💻 Technical Criteria
Given Multiple cargo records with same car ID and waybill have been identified
When Batch processing is initiated
Then System applies the same arrival cancellation processing to all related cargo records with matching car ID and waybill number
R-GCX016E-cbl-00726 Verify All Records Updated
Validation Rules
📊 Business Logic Narrative
When the process 'Verify All Records Updated' is invoked, and assuming that all related cargo records have been processed for arrival cancellation, when verification process is executed, the desired outcome is that system confirms that all cargo records with matching car id and waybill have been successfully updated with cancellation changes.
💻 Technical Criteria
Given All related cargo records have been processed for arrival cancellation
When Verification process is executed
Then System confirms that all cargo records with matching car ID and waybill have been successfully updated with cancellation changes
R-GCX016E-cbl-00772 Include Equipment Details
Process Rules
📊 Business Logic Narrative
When the process 'Include Equipment Details' is invoked, and assuming that hold notification message formatting has begun, when the system accesses gcsusrt cargo root for equipment details, the desired outcome is that car id, waybill number, and equipment type information are included in the notification.
💻 Technical Criteria
Given Hold notification message formatting has begun
When The system accesses GCSUSRT cargo root for equipment details
Then Car ID, waybill number, and equipment type information are included in the notification
R-GCX016E-cbl-00774 Include Waybill Number
Process Rules
📊 Business Logic Narrative
When the process 'Include Waybill Number' is invoked, and assuming that car id has been formatted for the notification, when the system processes waybill information, the desired outcome is that waybill number is included in the notification message for cargo identification.
💻 Technical Criteria
Given Car ID has been formatted for the notification
When The system processes waybill information
Then Waybill number is included in the notification message for cargo identification
R-GCX016E-cbl-00775 Add Cargo Identification
Process Rules
📊 Business Logic Narrative
When the process 'Add Cargo Identification' is invoked, and assuming that equipment details have been included in the notification, when the system processes cargo identification data, the desired outcome is that us-ccn, cargo description, and quantity information are added to the notification.
💻 Technical Criteria
Given Equipment details have been included in the notification
When The system processes cargo identification data
Then US-CCN, cargo description, and quantity information are added to the notification
R-GCX016E-cbl-00776 Format US-CCN
Computation Rules
📊 Business Logic Narrative
When the process 'Format US-CCN' is invoked, and assuming that cargo identification is being added to the notification, when the system processes us-ccn information, the desired outcome is that us-ccn is formatted according to standard format and included in the message.
💻 Technical Criteria
Given Cargo identification is being added to the notification
When The system processes US-CCN information
Then US-CCN is formatted according to standard format and included in the message
R-GCX016E-cbl-03413 Update Status Array with Final Codes
Action Rules
📊 Business Logic Narrative
When the process 'Update Status Array with Final Codes' is invoked, and assuming that final disposition codes are validated and compliance is confirmed, when status array update is executed, the desired outcome is that the system updates the s09 status array with final disposition codes including sequence numbers and occurrence tracking.
💻 Technical Criteria
Given Final disposition codes are validated and compliance is confirmed
When Status array update is executed
Then The system updates the S09 status array with final disposition codes including sequence numbers and occurrence tracking
R-GCX016E-cbl-00883 Include Cargo Details in Message
Process Rules
📊 Business Logic Narrative
When the process 'Include Cargo Details in Message' is invoked, and assuming that notification message is being formatted, when cargo details are added to the message, the desired outcome is that the system includes cargo ccn, car id, waybill number, and quantity information in the notification.
💻 Technical Criteria
Given Notification message is being formatted
When Cargo details are added to the message
Then The system includes cargo CCN, car ID, waybill number, and quantity information in the notification
R-GCX016E-cbl-00921 Update Multi-Cargo Records with Same Car/Waybill
Process Rules
📊 Business Logic Narrative
When the process 'Update Multi-Cargo Records with Same Car/Waybill' is invoked, and assuming that primary cargo record has been updated and logged, when multiple cargos exist with the same car id and waybill combination, the desired outcome is that all related cargo records with matching car id and waybill are updated with consistent status information.
💻 Technical Criteria
Given Primary cargo record has been updated and logged
When Multiple cargos exist with the same car ID and waybill combination
Then All related cargo records with matching car ID and waybill are updated with consistent status information
R-GCX016E-cbl-00922 Start Multi-Cargo Processing by Car/Waybill
Process Rules
📊 Business Logic Narrative
When the process 'Start Multi-Cargo Processing by Car/Waybill' is invoked, and assuming that a cargo record with car id and waybill number exists in the system, when multi-cargo processing is triggered for car/waybill combination, the desired outcome is that system begins coordinated processing of all related cargo records.
💻 Technical Criteria
Given A cargo record with car ID and waybill number exists in the system
When Multi-cargo processing is triggered for car/waybill combination
Then System begins coordinated processing of all related cargo records
R-GCX016E-cbl-00923 Retrieve First Cargo Record by Car ID and Waybill
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve First Cargo Record by Car ID and Waybill' is invoked, and assuming that car id and waybill number are provided for cargo lookup, when system searches for cargo records with matching car id and waybill, the desired outcome is that first matching cargo record is retrieved for processing.
💻 Technical Criteria
Given Car ID and waybill number are provided for cargo lookup
When System searches for cargo records with matching car ID and waybill
Then First matching cargo record is retrieved for processing
R-GCX016E-cbl-00924 Cargo Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Cargo Record Found?' is invoked, and assuming that a search for cargo records by car id and waybill has been performed, when system evaluates the search results, the desired outcome is that processing continues if cargo record found, otherwise processing terminates.
💻 Technical Criteria
Given A search for cargo records by car ID and waybill has been performed
When System evaluates the search results
Then Processing continues if cargo record found, otherwise processing terminates
R-GCX016E-cbl-00933 Retrieve Next Cargo Record with Same Car/Waybill
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Next Cargo Record with Same Car/Waybill' is invoked, and assuming that current cargo record processing is complete and no holds prevent continuation, when system searches for additional cargo records with same car id and waybill, the desired outcome is that next matching cargo record is retrieved for processing.
💻 Technical Criteria
Given Current cargo record processing is complete and no holds prevent continuation
When System searches for additional cargo records with same car ID and waybill
Then Next matching cargo record is retrieved for processing
R-GCX016E-cbl-00934 More Records with Same Car/Waybill?
Validation Rules
📊 Business Logic Narrative
When the process 'More Records with Same Car/Waybill?' is invoked, and assuming that a search for additional cargo records with same car id and waybill has been performed, when system evaluates search results for more records, the desired outcome is that if more records exist, continue processing; otherwise proceed to release verification.
💻 Technical Criteria
Given A search for additional cargo records with same car ID and waybill has been performed
When System evaluates search results for more records
Then If more records exist, continue processing; otherwise proceed to release verification
R-GCX016E-cbl-00935 Verify Release Status Across All Records
Validation Rules
📊 Business Logic Narrative
When the process 'Verify Release Status Across All Records' is invoked, and assuming that all cargo records with same car id and waybill have been processed, when system verifies release status across all related records, the desired outcome is that release status is verified for coordinated notification and database updates.
💻 Technical Criteria
Given All cargo records with same car ID and waybill have been processed
When System verifies release status across all related records
Then Release status is verified for coordinated notification and database updates
R-GCX016E-cbl-00937 Generate Comprehensive Release Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Comprehensive Release Notification' is invoked, and assuming that all cargo records with same car id and waybill are in released status, when comprehensive release notification is triggered, the desired outcome is that complete release notification is generated for all stakeholders.
💻 Technical Criteria
Given All cargo records with same car ID and waybill are in released status
When Comprehensive release notification is triggered
Then Complete release notification is generated for all stakeholders
R-GCX016E-cbl-00940 End Multi-Cargo Processing
Process Rules
📊 Business Logic Narrative
When the process 'End Multi-Cargo Processing' is invoked, and assuming that all cargo records have been processed and database updates completed, when multi-cargo processing reaches completion, the desired outcome is that processing terminates successfully for the car/waybill group.
💻 Technical Criteria
Given All cargo records have been processed and database updates completed
When Multi-cargo processing reaches completion
Then Processing terminates successfully for the car/waybill group
R-GCX016E-cbl-00954 Check Multiple Records with Same Car/Waybill
Validation Rules
📊 Business Logic Narrative
When the process 'Check Multiple Records with Same Car/Waybill' is invoked, and assuming that a cargo record has been processed for individual analysis, when the system searches for other cargo records with matching car id and waybill number, the desired outcome is that the system determines if the cargo is part of a single record or multiple records with the same car/waybill combination.
💻 Technical Criteria
Given A cargo record has been processed for individual analysis
When The system searches for other cargo records with matching car ID and waybill number
Then The system determines if the cargo is part of a single record or multiple records with the same car/waybill combination
R-GCX016E-cbl-00955 Analyze All Related Records
Process Rules
📊 Business Logic Narrative
When the process 'Analyze All Related Records' is invoked, and assuming that multiple cargo records exist with the same car id and waybill number, when the system processes each related cargo record for status and hold conditions, the desired outcome is that all related cargo records are analyzed collectively to determine the overall shipment status.
💻 Technical Criteria
Given Multiple cargo records exist with the same car ID and waybill number
When The system processes each related cargo record for status and hold conditions
Then All related cargo records are analyzed collectively to determine the overall shipment status
R-GCX016E-cbl-00960 All Records with Same Car/Waybill Released?
Decision Rules
📊 Business Logic Narrative
When the process 'All Records with Same Car/Waybill Released?' is invoked, and assuming that multiple cargo records exist with the same car id and waybill number, when the system evaluates release status for notification preparation, the desired outcome is that all related cargo records must be in released status to continue with release notification, otherwise the process terminates.
💻 Technical Criteria
Given Multiple cargo records exist with the same car ID and waybill number
When The system evaluates release status for notification preparation
Then All related cargo records must be in released status to continue with release notification, otherwise the process terminates
R-GCX016E-cbl-00979 Format Cargo Details
Process Rules
📊 Business Logic Narrative
When the process 'Format Cargo Details' is invoked, and assuming that an export notification message with equipment information and cargo record with complete details, when the system formats cargo details for the export message, the desired outcome is that the system includes formatted ccn, waybill, origin, destination, and commodity information in the export notification.
💻 Technical Criteria
Given An export notification message with equipment information and cargo record with complete details
When The system formats cargo details for the export message
Then The system includes formatted CCN, waybill, origin, destination, and commodity information in the export notification
R-GCX016E-cbl-00995 Check Multi-Cargo Records
Decision Rules
📊 Business Logic Narrative
When the process 'Check Multi-Cargo Records' is invoked, and assuming that a cargo arrival is being processed, when the system checks for related cargo records, the desired outcome is that the system identifies if there are multiple cargo records with the same car id and waybill that require coordinated processing.
💻 Technical Criteria
Given A cargo arrival is being processed
When The system checks for related cargo records
Then The system identifies if there are multiple cargo records with the same car ID and waybill that require coordinated processing
R-GCX016E-cbl-00996 Same Car/Waybill Records?
Decision Rules
📊 Business Logic Narrative
When the process 'Same Car/Waybill Records?' is invoked, and assuming that multiple cargo records exist in the system, when the system compares car id and waybill information, the desired outcome is that the system identifies records with matching car id and waybill numbers that require coordinated arrival processing.
💻 Technical Criteria
Given Multiple cargo records exist in the system
When The system compares car ID and waybill information
Then The system identifies records with matching car ID and waybill numbers that require coordinated arrival processing
R-GCX016E-cbl-00997 Process All Related Records
Process Rules
📊 Business Logic Narrative
When the process 'Process All Related Records' is invoked, and assuming that multiple cargo records share the same car id and waybill, when an arrival event is processed for one record, the desired outcome is that the system processes arrival status for all related records with the same car id and waybill.
💻 Technical Criteria
Given Multiple cargo records share the same car ID and waybill
When An arrival event is processed for one record
Then The system processes arrival status for all related records with the same car ID and waybill
R-GCX016E-cbl-01109 Retrieve Cargo Information
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Cargo Information' is invoked, and assuming that a cargo record exists in the system with valid equipment and manifest information, when the system prepares to format a merlin message for cargo disposition processing, the desired outcome is that the system retrieves and formats the car id, waybill number, us-ccn, and associated cargo identification details for message content.
💻 Technical Criteria
Given A cargo record exists in the system with valid equipment and manifest information
When The system prepares to format a Merlin message for cargo disposition processing
Then The system retrieves and formats the car ID, waybill number, US-CCN, and associated cargo identification details for message content
R-GCX016E-cbl-03029 Format Car ID and Waybill Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Car ID and Waybill Information' is invoked, and assuming that equipment details are available with car id and waybill information, when the system formats message content, the desired outcome is that car id and waybill information are formatted according to merlin message standards.
💻 Technical Criteria
Given Equipment details are available with car ID and waybill information
When The system formats message content
Then Car ID and waybill information are formatted according to Merlin message standards
R-GCX016E-cbl-03030 Add US-CCN Information
Process Rules
📊 Business Logic Narrative
When the process 'Add US-CCN Information' is invoked, and assuming that a cargo record contains us-ccn information, when the system assembles merlin message content, the desired outcome is that us-ccn information is included in the message.
💻 Technical Criteria
Given A cargo record contains US-CCN information
When The system assembles Merlin message content
Then US-CCN information is included in the message
R-GCX016E-cbl-01127 Include Processing Details
Process Rules
📊 Business Logic Narrative
When the process 'Include Processing Details' is invoked, and assuming that a bond creation notification message is being prepared with validated bond information, when the system adds processing details including car identification, waybill numbers, us ccn, and processing timestamps, the desired outcome is that the notification message contains complete processing context information for the bond creation request.
💻 Technical Criteria
Given A bond creation notification message is being prepared with validated bond information
When The system adds processing details including car identification, waybill numbers, US CCN, and processing timestamps
Then The notification message contains complete processing context information for the bond creation request
R-GCX016E-cbl-01214 Build Comprehensive Email Content
Process Rules
📊 Business Logic Narrative
When the process 'Build Comprehensive Email Content' is invoked, and assuming that a valid email address has been found for the freight forwarder, when the system builds the email notification content, the desired outcome is that the system creates comprehensive email content including equipment information, waybill details, ccn information, content description, origin/destination stations, cih disposition information, and processing timestamps.
💻 Technical Criteria
Given A valid email address has been found for the freight forwarder
When The system builds the email notification content
Then The system creates comprehensive email content including equipment information, waybill details, CCN information, content description, origin/destination stations, CIH disposition information, and processing timestamps
R-GCX016E-cbl-01216 Include Waybill and CCN Details
Process Rules
📊 Business Logic Narrative
When the process 'Include Waybill and CCN Details' is invoked, and assuming that equipment information has been included in the email content, when the system processes waybill and ccn information, the desired outcome is that the system includes waybill number and ccn details in the email notification content.
💻 Technical Criteria
Given Equipment information has been included in the email content
When The system processes waybill and CCN information
Then The system includes waybill number and CCN details in the email notification content
R-GCX016E-cbl-01217 Include Content Description
Process Rules
📊 Business Logic Narrative
When the process 'Include Content Description' is invoked, and assuming that waybill and ccn details have been included in the email content, when the system processes cargo content description data, the desired outcome is that the system includes detailed cargo content description in the email notification.
💻 Technical Criteria
Given Waybill and CCN details have been included in the email content
When The system processes cargo content description data
Then The system includes detailed cargo content description in the email notification
R-GCX016E-cbl-03066 Retrieve Waybill Number
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Waybill Number' is invoked, and assuming that a cargo record contains waybill information, when the system processes cargo information for email content, the desired outcome is that the waybill number is retrieved from the cargo record.
💻 Technical Criteria
Given A cargo record contains waybill information
When The system processes cargo information for email content
Then The waybill number is retrieved from the cargo record
R-GCX016E-cbl-03067 Get US-CCN Information
Action Rules
📊 Business Logic Narrative
When the process 'Get US-CCN Information' is invoked, and assuming that a cargo record contains us-ccn data, when the system processes cargo identification information, the desired outcome is that us-ccn information is retrieved from the cargo record.
💻 Technical Criteria
Given A cargo record contains US-CCN data
When The system processes cargo identification information
Then US-CCN information is retrieved from the cargo record
R-GCX016E-cbl-03078 Add Cargo Information Section
Process Rules
📊 Business Logic Narrative
When the process 'Add Cargo Information Section' is invoked, and assuming that equipment details section has been added and cargo information is available, when the system adds cargo information to email content, the desired outcome is that cargo information section is added with waybill, us-ccn, and content description.
💻 Technical Criteria
Given Equipment details section has been added and cargo information is available
When The system adds cargo information to email content
Then Cargo information section is added with waybill, US-CCN, and content description
R-GCX016E-cbl-01248 Include Waybill and CCN Details
Process Rules
📊 Business Logic Narrative
When the process 'Include Waybill and CCN Details' is invoked, and assuming that waybill and ccn information exists for the cargo, when creating debug log entries, the desired outcome is that the system includes waybill number and ccn details for cargo identification.
💻 Technical Criteria
Given Waybill and CCN information exists for the cargo
When Creating debug log entries
Then The system includes waybill number and CCN details for cargo identification
R-GCX016E-cbl-01308 Set Car ID and Waybill
Process Rules
📊 Business Logic Narrative
When the process 'Set Car ID and Waybill' is invoked, and assuming that quantity information has been set in the n7 segment, when the system sets car id and waybill, the desired outcome is that the system assigns car identification number and waybill reference to the n7 segment.
💻 Technical Criteria
Given Quantity information has been set in the N7 segment
When The system sets car ID and waybill
Then The system assigns car identification number and waybill reference to the N7 segment
R-GCX016E-cbl-01335 Extract Waybill Number
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Waybill Number' is invoked, and assuming that cargo data contains waybill information, when waybill number extraction is performed, the desired outcome is that the waybill number is retrieved and made available for report formatting.
💻 Technical Criteria
Given Cargo data contains waybill information
When Waybill number extraction is performed
Then The waybill number is retrieved and made available for report formatting
R-GCX016E-cbl-01336 Extract US-CCN
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract US-CCN' is invoked, and assuming that cargo data contains us customs control number information, when us-ccn extraction is performed, the desired outcome is that the us-ccn is retrieved and made available for report formatting.
💻 Technical Criteria
Given Cargo data contains US Customs Control Number information
When US-CCN extraction is performed
Then The US-CCN is retrieved and made available for report formatting
R-GCX016E-cbl-01446 Identify Lead Manifest CCN
Process Rules
📊 Business Logic Narrative
When the process 'Identify Lead Manifest CCN' is invoked, and assuming that a multi-manifest scenario has been identified, when the system needs to process follower manifests, the desired outcome is that the lead manifest ccn is identified and stored for comparison with follower manifest ccns.
💻 Technical Criteria
Given A multi-manifest scenario has been identified
When The system needs to process follower manifests
Then The lead manifest CCN is identified and stored for comparison with follower manifest CCNs
R-GCX016E-cbl-01447 Identify US CCN Key
Process Rules
📊 Business Logic Narrative
When the process 'Identify US CCN Key' is invoked, and assuming that lead manifest ccn has been identified, when the system prepares to compare manifests, the desired outcome is that the us ccn key is extracted and prepared for comparison with the lead manifest ccn.
💻 Technical Criteria
Given Lead manifest CCN has been identified
When The system prepares to compare manifests
Then The US CCN key is extracted and prepared for comparison with the lead manifest CCN
R-GCX016E-cbl-01448 Lead Manifest CCN ≠ US CCN Key?
Decision Rules
📊 Business Logic Narrative
When the process 'Lead Manifest CCN ≠ US CCN Key?' is invoked, and assuming that both lead manifest ccn and us ccn key have been identified, when the system compares the lead manifest ccn with the us ccn key, the desired outcome is that if the ccns are different, follower manifest processing is initiated; if they are the same, no additional processing is required.
💻 Technical Criteria
Given Both lead manifest CCN and US CCN key have been identified
When The system compares the lead manifest CCN with the US CCN key
Then If the CCNs are different, follower manifest processing is initiated; if they are the same, no additional processing is required
R-GCX016E-cbl-01449 Prepare 350 Special Action Message
Process Rules
📊 Business Logic Narrative
When the process 'Prepare 350 Special Action Message' is invoked, and assuming that lead manifest ccn differs from us ccn key, when the system prepares to spawn a follower manifest transaction, the desired outcome is that a special action message with action code 350 is prepared for the gct0162e transaction.
💻 Technical Criteria
Given Lead manifest CCN differs from US CCN key
When The system prepares to spawn a follower manifest transaction
Then A special action message with action code 350 is prepared for the GCT0162E transaction
R-GCX016E-cbl-01458 No Transaction Spawning Required
Process Rules
📊 Business Logic Narrative
When the process 'No Transaction Spawning Required' is invoked, and assuming that either no multi-manifest scenario exists or lead manifest ccn equals us ccn key, when the system determines that no follower manifest processing is needed, the desired outcome is that no transaction spawning occurs and processing continues with the normal flow.
💻 Technical Criteria
Given Either no multi-manifest scenario exists or lead manifest CCN equals US CCN key
When The system determines that no follower manifest processing is needed
Then No transaction spawning occurs and processing continues with the normal flow
R-GCX016E-cbl-01685 Remove Previous Proceed Code
Action Rules
📊 Business Logic Narrative
When the process 'Remove Previous Proceed Code' is invoked, and assuming that a matching proceed disposition code has been identified in the cargo's disposition history, when the cancel disposition processing requires removal of the previous code, the desired outcome is that remove the proceed code from the disposition array and update the array sequence numbers accordingly.
💻 Technical Criteria
Given A matching proceed disposition code has been identified in the cargo's disposition history
When The cancel disposition processing requires removal of the previous code
Then Remove the proceed code from the disposition array and update the array sequence numbers accordingly
R-GCX016E-cbl-01689 US CCN Key Available?
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'US CCN Key Available?', assuming that cargo has not been found via primary search methods, when the system checks for us ccn key availability in the cargo record, the desired outcome is that if us ccn key exists and is not empty, proceed with us ccn search; otherwise generate cargo not found error.
💻 Technical Criteria
EXCLUDING Cargo has not been found via primary search methods
When The system checks for US CCN key availability in the cargo record
Then If US CCN key exists and is not empty, proceed with US CCN search; otherwise generate cargo not found error
R-GCX016E-cbl-01690 Extract US CCN from Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Extract US CCN from Cargo Record' is invoked, and assuming that a valid cargo record exists and us ccn key is available, when the system extracts the us ccn value from the cargo record, the desired outcome is that the us ccn value is retrieved and prepared for formatting.
💻 Technical Criteria
Given A valid cargo record exists and US CCN key is available
When The system extracts the US CCN value from the cargo record
Then The US CCN value is retrieved and prepared for formatting
R-GCX016E-cbl-01691 Format US CCN Key for Search
Process Rules
📊 Business Logic Narrative
When the process 'Format US CCN Key for Search' is invoked, and assuming that us ccn has been extracted from the cargo record, when the system formats the us ccn into a search key, the desired outcome is that the us ccn is properly formatted according to database key requirements.
💻 Technical Criteria
Given US CCN has been extracted from the cargo record
When The system formats the US CCN into a search key
Then The US CCN is properly formatted according to database key requirements
R-GCX016E-cbl-01692 Search Cargo Database by US CCN Key
Action Rules
📊 Business Logic Narrative
When the process 'Search Cargo Database by US CCN Key' is invoked, and assuming that us ccn key has been properly formatted for search, when the system searches the cargo database using the us ccn key, the desired outcome is that database search is executed against gcsusrt using the us ccn key.
💻 Technical Criteria
Given US CCN key has been properly formatted for search
When The system searches the cargo database using the US CCN key
Then Database search is executed against GCSUSRT using the US CCN key
R-GCX016E-cbl-01693 Cargo Found by US CCN?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Found by US CCN?' is invoked, and assuming that database search by us ccn has been completed, when the system evaluates the search results, the desired outcome is that if cargo record is found, proceed with record retrieval; otherwise generate cargo not found error.
💻 Technical Criteria
Given Database search by US CCN has been completed
When The system evaluates the search results
Then If cargo record is found, proceed with record retrieval; otherwise generate cargo not found error
R-GCX016E-cbl-01694 Retrieve Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Cargo Record' is invoked, and assuming that cargo has been found by us ccn search, when the system retrieves the cargo record from gcsusrt, the desired outcome is that complete cargo record is loaded for further processing.
💻 Technical Criteria
Given Cargo has been found by US CCN search
When The system retrieves the cargo record from GCSUSRT
Then Complete cargo record is loaded for further processing
R-GCX016E-cbl-01700 Generate Cargo Not Found Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Cargo Not Found Error', assuming that us ccn key is not available, cargo is not found by us ccn search, or cargo record validation fails, when the system generates a cargo not found error, the desired outcome is that error is generated indicating cargo could not be located for processing.
💻 Technical Criteria
EXCLUDING US CCN key is not available, cargo is not found by US CCN search, or cargo record validation fails
When The system generates a cargo not found error
Then Error is generated indicating cargo could not be located for processing
R-GCX016E-cbl-01708 Update Cargo Status Arrays
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status Arrays' is invoked, and assuming that all bond information has been cleared from the cargo record, when the system updates the cargo status arrays, the desired outcome is that the status array is updated with disposition code 95 and appropriate sequence numbers to track the bond cancellation.
💻 Technical Criteria
Given All bond information has been cleared from the cargo record
When The system updates the cargo status arrays
Then The status array is updated with disposition code 95 and appropriate sequence numbers to track the bond cancellation
R-GCX016E-cbl-01746 Lead Manifest CCN differs from US CCN Key?
Decision Rules
📊 Business Logic Narrative
When the process 'Lead Manifest CCN differs from US CCN Key?' is invoked, and assuming that a lead manifest with an associated ccn and a current us ccn key are available, when the system compares the lead manifest ccn with the us ccn key, the desired outcome is that if the lead manifest ccn differs from the us ccn key, proceed with follower manifest processing, otherwise complete multi-manifest processing.
💻 Technical Criteria
Given A lead manifest with an associated CCN and a current US CCN key are available
When The system compares the lead manifest CCN with the US CCN key
Then If the lead manifest CCN differs from the US CCN key, proceed with follower manifest processing, otherwise complete multi-manifest processing
R-GCX016E-cbl-01775 Extract Waybill Number from Input Message
Process Rules
📊 Business Logic Narrative
When the process 'Extract Waybill Number from Input Message' is invoked, and assuming that an input message containing waybill number information is received, when the system processes the message to extract waybill number, the desired outcome is that the waybill number is extracted and prepared for use in database search key construction.
💻 Technical Criteria
Given An input message containing waybill number information is received
When The system processes the message to extract waybill number
Then The waybill number is extracted and prepared for use in database search key construction
R-GCX016E-cbl-01777 Construct Car/Waybill Search Key
Process Rules
📊 Business Logic Narrative
When the process 'Construct Car/Waybill Search Key' is invoked, and assuming that a formatted car id and extracted waybill number are available, when the system constructs the combined search key, the desired outcome is that a composite car/waybill search key is created for database query operations.
💻 Technical Criteria
Given A formatted car ID and extracted waybill number are available
When The system constructs the combined search key
Then A composite car/waybill search key is created for database query operations
R-GCX016E-cbl-01778 Access GCSUSRT Database
Action Rules
📊 Business Logic Narrative
When the process 'Access GCSUSRT Database' is invoked, and assuming that a car/waybill search key has been constructed, when the system accesses the gcsusrt database, the desired outcome is that database connection is established and ready for cargo record search operations.
💻 Technical Criteria
Given A car/waybill search key has been constructed
When The system accesses the GCSUSRT database
Then Database connection is established and ready for cargo record search operations
R-GCX016E-cbl-01779 First Record Found?
Decision Rules
📊 Business Logic Narrative
When the process 'First Record Found?' is invoked, and assuming that the gcsusrt database has been accessed with a car/waybill search key, when the system searches for the first matching cargo record, the desired outcome is that the system determines whether a matching cargo record exists or not.
💻 Technical Criteria
Given The GCSUSRT database has been accessed with a car/waybill search key
When The system searches for the first matching cargo record
Then The system determines whether a matching cargo record exists or not
R-GCX016E-cbl-01788 Set No Records Found Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set No Records Found Flag' is invoked, and assuming that the database search has been completed, when no cargo records match the car/waybill search criteria, the desired outcome is that the no records found flag is set to indicate unsuccessful search results.
💻 Technical Criteria
Given The database search has been completed
When No cargo records match the car/waybill search criteria
Then The no records found flag is set to indicate unsuccessful search results
R-GCX016E-cbl-01790 CPRS Cargo Found in System?
Validation Rules
📊 Business Logic Narrative
When the process 'CPRS Cargo Found in System?' is invoked, and assuming that a cprs cargo lookup request with car id and waybill information, when the system searches for existing cprs cargo records using the car id and waybill as search criteria, the desired outcome is that the system returns whether the cprs cargo record exists or not in the database.
💻 Technical Criteria
Given A CPRS cargo lookup request with car ID and waybill information
When The system searches for existing CPRS cargo records using the car ID and waybill as search criteria
Then The system returns whether the CPRS cargo record exists or not in the database
R-GCX016E-cbl-01804 Foreign Bill Not Found in System
Validation Rules
📊 Business Logic Narrative
When the process 'Foreign Bill Not Found in System' is invoked, and assuming that a foreign bill of lading number is provided in the x4 segment, when the system searches the cargo database for the bill of lading, the desired outcome is that the system confirms the bill does not exist and proceeds with new cargo creation.
💻 Technical Criteria
Given A foreign bill of lading number is provided in the X4 segment
When The system searches the cargo database for the bill of lading
Then The system confirms the bill does not exist and proceeds with new cargo creation
R-GCX016E-cbl-01916 Combine Car ID and Waybill as Search Key
Process Rules
📊 Business Logic Narrative
When the process 'Combine Car ID and Waybill as Search Key' is invoked, and assuming that a formatted car id and a waybill number are available, when the system prepares to search for cargo records, the desired outcome is that the system combines car id and waybill into a single composite search key.
💻 Technical Criteria
Given A formatted car ID and a waybill number are available
When The system prepares to search for cargo records
Then The system combines car ID and waybill into a single composite search key
R-GCX016E-cbl-01917 Call GCCUSIO2 Database Lookup
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCUSIO2 Database Lookup' is invoked, and assuming that a composite search key containing car id and waybill is prepared, when the system needs to retrieve cargo records from the database, the desired outcome is that the system calls gccusio2 service with the search key to perform the database lookup.
💻 Technical Criteria
Given A composite search key containing car ID and waybill is prepared
When The system needs to retrieve cargo records from the database
Then The system calls GCCUSIO2 service with the search key to perform the database lookup
R-GCX016E-cbl-01918 Cargo Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Cargo Record Found?' is invoked, and assuming that a database lookup has been performed using car id and waybill search key, when the system evaluates the lookup results, the desired outcome is that the system determines if at least one matching cargo record was found and proceeds accordingly.
💻 Technical Criteria
Given A database lookup has been performed using car ID and waybill search key
When The system evaluates the lookup results
Then The system determines if at least one matching cargo record was found and proceeds accordingly
R-GCX016E-cbl-01920 Check for Additional Records
Decision Rules
📊 Business Logic Narrative
When the process 'Check for Additional Records' is invoked, and assuming that the first cargo record has been retrieved successfully, when the system evaluates the complete result set, the desired outcome is that the system checks if more records exist with the same car id and waybill combination.
💻 Technical Criteria
Given The first cargo record has been retrieved successfully
When The system evaluates the complete result set
Then The system checks if more records exist with the same car ID and waybill combination
R-GCX016E-cbl-01921 More Records with Same Car/Waybill?
Decision Rules
📊 Business Logic Narrative
When the process 'More Records with Same Car/Waybill?' is invoked, and assuming that at least one cargo record has been processed, when the system checks for additional matching records, the desired outcome is that the system determines if more records with identical car id and waybill exist and routes processing accordingly.
💻 Technical Criteria
Given At least one cargo record has been processed
When The system checks for additional matching records
Then The system determines if more records with identical car ID and waybill exist and routes processing accordingly
R-GCX016E-cbl-01922 Retrieve Subsequent Records
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Subsequent Records' is invoked, and assuming that additional cargo records exist with the same car id and waybill, when the system continues processing the record set, the desired outcome is that the system retrieves the next cargo record in the sequence.
💻 Technical Criteria
Given Additional cargo records exist with the same car ID and waybill
When The system continues processing the record set
Then The system retrieves the next cargo record in the sequence
R-GCX016E-cbl-01927 Complete Record Set Retrieved
Process Rules
📊 Business Logic Narrative
When the process 'Complete Record Set Retrieved' is invoked, and assuming that all available cargo records with matching car id and waybill have been evaluated, when no more records remain to be processed, the desired outcome is that the system confirms that the complete record set has been retrieved and processed.
💻 Technical Criteria
Given All available cargo records with matching car ID and waybill have been evaluated
When No more records remain to be processed
Then The system confirms that the complete record set has been retrieved and processed
R-GCX016E-cbl-01936 Assign US-CCN Key
Process Rules
📊 Business Logic Narrative
When the process 'Assign US-CCN Key' is invoked, and assuming that car id has been formatted according to cprs standards, when the system assigns a us-ccn key to the cargo record, the desired outcome is that the system should generate or assign a unique us cargo control number that serves as the primary key for the cargo record.
💻 Technical Criteria
Given Car ID has been formatted according to CPRS standards
When The system assigns a US-CCN key to the cargo record
Then The system should generate or assign a unique US Cargo Control Number that serves as the primary key for the cargo record
R-GCX016E-cbl-01937 Set Cargo Status to New
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Cargo Status to New' is invoked, and assuming that us-ccn key has been assigned to the cargo record, when the system sets the initial cargo status, the desired outcome is that the system should set the cargo status to 'new' to indicate this is a newly created cargo record awaiting processing.
💻 Technical Criteria
Given US-CCN key has been assigned to the cargo record
When The system sets the initial cargo status
Then The system should set the cargo status to 'New' to indicate this is a newly created cargo record awaiting processing
R-GCX016E-cbl-01958 SCAC Unknown?
Decision Rules
📊 Business Logic Narrative
When the process 'SCAC Unknown?' is invoked, and assuming that a scac code has been retrieved from the cargo record, when the system evaluates the scac code status, the desired outcome is that the system determines if the scac is unknown and requires us-ccn key renumbering.
💻 Technical Criteria
Given A SCAC code has been retrieved from the cargo record
When The system evaluates the SCAC code status
Then The system determines if the SCAC is unknown and requires US-CCN key renumbering
R-GCX016E-cbl-01959 Perform US-CCN Key Renumbering
Action Rules
📊 Business Logic Narrative
When the process 'Perform US-CCN Key Renumbering' is invoked, and assuming that a cargo record has been found but scac is marked as unknown, when the system performs us-ccn key renumbering, the desired outcome is that the system updates the us-ccn key index to create a new searchable key.
💻 Technical Criteria
Given A cargo record has been found but SCAC is marked as unknown
When The system performs US-CCN key renumbering
Then The system updates the US-CCN key index to create a new searchable key
R-GCX016E-cbl-01960 Search Again with New Key
Action Rules
📊 Business Logic Narrative
When the process 'Search Again with New Key' is invoked, and assuming that us-ccn key renumbering has been completed, when the system searches for cargo using the new key, the desired outcome is that the system queries the cargo database with the renumbered us-ccn key.
💻 Technical Criteria
Given US-CCN key renumbering has been completed
When The system searches for cargo using the new key
Then The system queries the cargo database with the renumbered US-CCN key
R-GCX016E-cbl-01968 Set Car ID and US-CCN Keys
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Car ID and US-CCN Keys' is invoked, and assuming that a cargo requires status segment retrieval, when the system prepares to query status segments, the desired outcome is that the car id and us-ccn keys are set to identify the specific cargo.
💻 Technical Criteria
Given A cargo requires status segment retrieval
When The system prepares to query status segments
Then The Car ID and US-CCN keys are set to identify the specific cargo
R-GCX016E-cbl-01969 Call GCCUSIO2 to Retrieve S09 Segments
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCUSIO2 to Retrieve S09 Segments' is invoked, and assuming that car id and us-ccn keys are properly set, when the system needs to retrieve cargo status segments, the desired outcome is that gccusio2 program is called to fetch s09 segments from gcsuss09 database.
💻 Technical Criteria
Given Car ID and US-CCN keys are properly set
When The system needs to retrieve cargo status segments
Then GCCUSIO2 program is called to fetch S09 segments from GCSUSS09 database
R-GCX016E-cbl-01974 Track Maximum Sequence Numbers
Computation Rules
📊 Business Logic Narrative
When the process 'Track Maximum Sequence Numbers' is invoked, and assuming that status segments are being processed with sequence numbers, when the system encounters sequence numbers in the segments, the desired outcome is that the maximum sequence numbers are tracked and stored for future reference.
💻 Technical Criteria
Given Status segments are being processed with sequence numbers
When The system encounters sequence numbers in the segments
Then The maximum sequence numbers are tracked and stored for future reference
R-GCX016E-cbl-01985 Track Maximum Sequence Number
Process Rules
📊 Business Logic Narrative
When the process 'Track Maximum Sequence Number' is invoked, and assuming that a status segment with a sequence number is being processed, when the sequence number is compared to the current maximum, the desired outcome is that if the current sequence number is higher than the tracked maximum, update the maximum sequence number.
💻 Technical Criteria
Given A status segment with a sequence number is being processed
When The sequence number is compared to the current maximum
Then If the current sequence number is higher than the tracked maximum, update the maximum sequence number
R-GCX016E-cbl-01987 Update Maximum Sequences Fetched
Process Rules
📊 Business Logic Narrative
When the process 'Update Maximum Sequences Fetched' is invoked, and assuming that all status segments for a cargo have been processed, when the population process is completing, the desired outcome is that the maximum sequences fetched counter is updated with the highest sequence number processed.
💻 Technical Criteria
Given All status segments for a cargo have been processed
When The population process is completing
Then The maximum sequences fetched counter is updated with the highest sequence number processed
R-GCX016E-cbl-01992 Prepare Database Segment
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Database Segment' is invoked, and assuming that status array data has been converted to database format and car id updates have been applied if applicable, when the system prepares the final database segment for storage, the desired outcome is that format the segment with proper sequence numbers, status codes, quantities, and cargo identification for database replacement operation.
💻 Technical Criteria
Given Status array data has been converted to database format and car ID updates have been applied if applicable
When The system prepares the final database segment for storage
Then Format the segment with proper sequence numbers, status codes, quantities, and cargo identification for database replacement operation
R-GCX016E-cbl-02047 Update Status Array Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Update Status Array Sequence' is invoked, and assuming that a disposition code has been removed from the status array, when the status array structure needs to be maintained, the desired outcome is that the system updates the array sequence numbers and reorganizes the remaining codes to maintain proper array structure.
💻 Technical Criteria
Given A disposition code has been removed from the status array
When The status array structure needs to be maintained
Then The system updates the array sequence numbers and reorganizes the remaining codes to maintain proper array structure
R-GCX016E-cbl-02057 Update Array Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Update Array Sequence' is invoked, and assuming that a status array with a newly inserted status information code, when the system updates the array sequence numbers, the desired outcome is that all sequence numbers are properly maintained to reflect the current array state.
💻 Technical Criteria
Given A status array with a newly inserted status information code
When The system updates the array sequence numbers
Then All sequence numbers are properly maintained to reflect the current array state
R-GCX016E-cbl-02067 Update Array Sequence Numbers
Process Rules
📊 Business Logic Narrative
When the process 'Update Array Sequence Numbers' is invoked, and assuming that a disposition code has been removed from the status array, when the system updates the array structure, the desired outcome is that all remaining disposition codes must have their sequence numbers updated to maintain proper ordering.
💻 Technical Criteria
Given A disposition code has been removed from the status array
When The system updates the array structure
Then All remaining disposition codes must have their sequence numbers updated to maintain proper ordering
R-GCX016E-cbl-02081 Add New Release Disposition Code to Status Array
Process Rules
📊 Business Logic Narrative
When the process 'Add New Release Disposition Code to Status Array' is invoked, and assuming that the new release disposition code has been validated as correct, when the status array has been cleared of conflicting codes, the desired outcome is that the system must add the new release disposition code to the status array with appropriate sequence number and occurrence data.
💻 Technical Criteria
Given The new release disposition code has been validated as correct
When The status array has been cleared of conflicting codes
Then The system must add the new release disposition code to the status array with appropriate sequence number and occurrence data
R-GCX016E-cbl-02082 Update Status Array Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Update Status Array Sequence' is invoked, and assuming that a new release disposition code has been added to the status array, when the status array structure needs to be maintained, the desired outcome is that the system must update sequence numbers and occurrence counts to maintain proper status array integrity.
💻 Technical Criteria
Given A new release disposition code has been added to the status array
When The status array structure needs to be maintained
Then The system must update sequence numbers and occurrence counts to maintain proper status array integrity
R-GCX016E-cbl-02092 Add Manual Release Disposition Code
Process Rules
📊 Business Logic Narrative
When the process 'Add Manual Release Disposition Code' is invoked, and assuming that the cargo status array has been cleared of conflicting codes, when a manual release is being applied, the desired outcome is that the system adds the manual release disposition code (mrl) to the status array with appropriate sequence number and metadata.
💻 Technical Criteria
Given The cargo status array has been cleared of conflicting codes
When A manual release is being applied
Then The system adds the manual release disposition code (MRL) to the status array with appropriate sequence number and metadata
R-GCX016E-cbl-02093 Update Status Array Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Update Status Array Sequence' is invoked, and assuming that disposition codes have been added or removed from the cargo status array, when the manual release processing updates the array, the desired outcome is that the system updates sequence numbers to maintain proper ordering and removes any gaps in the sequence.
💻 Technical Criteria
Given Disposition codes have been added or removed from the cargo status array
When The manual release processing updates the array
Then The system updates sequence numbers to maintain proper ordering and removes any gaps in the sequence
R-GCX016E-cbl-02137 Update Array Sequence Numbers
Process Rules
📊 Business Logic Narrative
When the process 'Update Array Sequence Numbers' is invoked, and assuming that the cargo status array has been reorganized after removing conflicting codes, when the system updates sequence numbers, the desired outcome is that the system assigns consecutive sequence numbers to all remaining disposition codes in the array starting from 1.
💻 Technical Criteria
Given The cargo status array has been reorganized after removing conflicting codes
When The system updates sequence numbers
Then The system assigns consecutive sequence numbers to all remaining disposition codes in the array starting from 1
R-GCX016E-cbl-02138 Validate Array Integrity
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Array Integrity' is invoked, and assuming that the cargo status array has been modified through counterpart code removal and reorganization, when the system validates array integrity, the desired outcome is that the system confirms that all remaining disposition codes are valid and sequence numbers are consecutive and no business rule conflicts remain in the array.
💻 Technical Criteria
Given The cargo status array has been modified through counterpart code removal and reorganization
When The system validates array integrity
Then The system confirms that all remaining disposition codes are valid AND sequence numbers are consecutive AND no business rule conflicts remain in the array
R-GCX016E-cbl-02143 Track Maximum Sequences Fetched
Computation Rules
📊 Business Logic Narrative
When the process 'Track Maximum Sequences Fetched' is invoked, and assuming that status segments are populated from database with various sequence numbers, when the system processes all retrieved segments, the desired outcome is that the system identifies and stores the maximum sequence number found across all status arrays for future sequencing.
💻 Technical Criteria
Given Status segments are populated from database with various sequence numbers
When The system processes all retrieved segments
Then The system identifies and stores the maximum sequence number found across all status arrays for future sequencing
R-GCX016E-cbl-02146 Find Insertion Point for Proper Sequencing
Process Rules
📊 Business Logic Narrative
When the process 'Find Insertion Point for Proper Sequencing' is invoked, and assuming that a new disposition code needs to be added to status arrays and no duplicates exist, when the system needs to insert the disposition code, the desired outcome is that the system finds the appropriate insertion point to maintain proper sequence numbering and array organization.
💻 Technical Criteria
Given A new disposition code needs to be added to status arrays and no duplicates exist
When The system needs to insert the disposition code
Then The system finds the appropriate insertion point to maintain proper sequence numbering and array organization
R-GCX016E-cbl-02151 Validate Array Sequence Numbers
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Array Sequence Numbers' is invoked, and assuming that status arrays have been modified through insertion and removal operations, when the system validates the array integrity, the desired outcome is that the system verifies that sequence numbers are properly ordered and consistent across all status array entries.
💻 Technical Criteria
Given Status arrays have been modified through insertion and removal operations
When The system validates the array integrity
Then The system verifies that sequence numbers are properly ordered and consistent across all status array entries
R-GCX016E-cbl-02152 Update Maximum Sequence Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Update Maximum Sequence Counter' is invoked, and assuming that status arrays have been modified and sequence numbers validated, when the system completes array processing, the desired outcome is that the system updates the maximum sequence counter to reflect the highest sequence number currently in use.
💻 Technical Criteria
Given Status arrays have been modified and sequence numbers validated
When The system completes array processing
Then The system updates the maximum sequence counter to reflect the highest sequence number currently in use
R-GCX016E-cbl-02181 Include Waybill Information
Process Rules
📊 Business Logic Narrative
When the process 'Include Waybill Information' is invoked, and assuming that equipment information has been included in the hold notification, when the system includes waybill information, the desired outcome is that the system adds waybill details from cargo data including waybill number, shipment references, and related shipping documentation information to the hold notification.
💻 Technical Criteria
Given Equipment information has been included in the hold notification
When The system includes waybill information
Then The system adds waybill details from cargo data including waybill number, shipment references, and related shipping documentation information to the hold notification
R-GCX016E-cbl-02182 Include CCN Information
Process Rules
📊 Business Logic Narrative
When the process 'Include CCN Information' is invoked, and assuming that waybill information has been included in the hold notification, when the system includes ccn information, the desired outcome is that the system adds cargo control number (ccn) details including us ccn, canadian ccn if applicable, and related manifest information to the hold notification.
💻 Technical Criteria
Given Waybill information has been included in the hold notification
When The system includes CCN information
Then The system adds Cargo Control Number (CCN) details including US CCN, Canadian CCN if applicable, and related manifest information to the hold notification
R-GCX016E-cbl-02183 Add Location Context
Process Rules
📊 Business Logic Narrative
When the process 'Add Location Context' is invoked, and assuming that ccn information has been included in the hold notification, when the system adds location context, the desired outcome is that the system includes location context from retrieved location information including origin location, destination location, current location, border crossing points, and relevant geographic identifiers.
💻 Technical Criteria
Given CCN information has been included in the hold notification
When The system adds location context
Then The system includes location context from retrieved location information including origin location, destination location, current location, border crossing points, and relevant geographic identifiers
R-GCX016E-cbl-02185 Create Detailed Hold Message
Process Rules
📊 Business Logic Narrative
When the process 'Create Detailed Hold Message' is invoked, and assuming that all hold notification components (equipment, waybill, ccn, location, disposition codes) have been gathered, when the system creates the detailed hold message, the desired outcome is that the system assembles all information into a structured, comprehensive hold message with proper formatting, business terminology, and complete cargo context for effective business communication.
💻 Technical Criteria
Given All hold notification components (equipment, waybill, CCN, location, disposition codes) have been gathered
When The system creates the detailed hold message
Then The system assembles all information into a structured, comprehensive hold message with proper formatting, business terminology, and complete cargo context for effective business communication
R-GCX016E-cbl-02370 Retrieve First Cargo Record by Car ID and Waybill
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve First Cargo Record by Car ID and Waybill' is invoked, and assuming that a car id and waybill number combination exists from previous n7 segment processing, when the system needs to process multiple cargo records with the same car and waybill, the desired outcome is that the system retrieves the first cargo record matching the car id and waybill combination from the us cargo root segments.
💻 Technical Criteria
Given A car ID and waybill number combination exists from previous N7 segment processing
When The system needs to process multiple cargo records with the same car and waybill
Then The system retrieves the first cargo record matching the car ID and waybill combination from the US cargo root segments
R-GCX016E-cbl-02371 Cargo Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Cargo Record Found?' is invoked, and assuming that a search has been performed for cargo records by car id and waybill, when the system evaluates the search results, the desired outcome is that if a cargo record is found, continue with individual cargo processing, otherwise end the multi-cargo processing.
💻 Technical Criteria
Given A search has been performed for cargo records by car ID and waybill
When The system evaluates the search results
Then If a cargo record is found, continue with individual cargo processing, otherwise end the multi-cargo processing
R-GCX016E-cbl-02372 Process Individual Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Process Individual Cargo Record' is invoked, and assuming that a cargo record has been retrieved with matching car id and waybill, when the system processes the individual cargo record, the desired outcome is that the system applies the current disposition code processing logic to the cargo record.
💻 Technical Criteria
Given A cargo record has been retrieved with matching car ID and waybill
When The system processes the individual cargo record
Then The system applies the current disposition code processing logic to the cargo record
R-GCX016E-cbl-02374 Check for Additional Cargo Records with Same Car/Waybill
Process Rules
📊 Business Logic Narrative
When the process 'Check for Additional Cargo Records with Same Car/Waybill' is invoked, and assuming that one cargo record has been processed for a car id and waybill combination, when the system checks for additional records, the desired outcome is that the system searches the cargo database for other records with the same car id and waybill combination.
💻 Technical Criteria
Given One cargo record has been processed for a car ID and waybill combination
When The system checks for additional records
Then The system searches the cargo database for other records with the same car ID and waybill combination
R-GCX016E-cbl-02375 More Records with Same Car/Waybill?
Decision Rules
📊 Business Logic Narrative
When the process 'More Records with Same Car/Waybill?' is invoked, and assuming that a search has been performed for additional cargo records with the same car id and waybill, when the system evaluates the search results, the desired outcome is that if more records are found, retrieve the next record for processing, otherwise proceed to release status verification.
💻 Technical Criteria
Given A search has been performed for additional cargo records with the same car ID and waybill
When The system evaluates the search results
Then If more records are found, retrieve the next record for processing, otherwise proceed to release status verification
R-GCX016E-cbl-02376 Retrieve Next Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Next Cargo Record' is invoked, and assuming that additional cargo records exist with the same car id and waybill combination, when the system retrieves the next record, the desired outcome is that the system fetches the next cargo record from the us cargo root segments for processing.
💻 Technical Criteria
Given Additional cargo records exist with the same car ID and waybill combination
When The system retrieves the next record
Then The system fetches the next cargo record from the US cargo root segments for processing
R-GCX016E-cbl-02377 Verify Release Status Across All Records
Validation Rules
📊 Business Logic Narrative
When the process 'Verify Release Status Across All Records' is invoked, and assuming that all cargo records with the same car id and waybill have been processed, when the system verifies release status across all records, the desired outcome is that the system examines the release status of each processed cargo record to determine overall release state.
💻 Technical Criteria
Given All cargo records with the same car ID and waybill have been processed
When The system verifies release status across all records
Then The system examines the release status of each processed cargo record to determine overall release state
R-GCX016E-cbl-02378 All Records Have Same Release Status?
Decision Rules
📊 Business Logic Narrative
When the process 'All Records Have Same Release Status?' is invoked, and assuming that release status has been verified across all cargo records with the same car id and waybill, when the system evaluates status consistency, the desired outcome is that if all records have the same release status, generate comprehensive release notification, otherwise proceed to create merlin notifications for status changes.
💻 Technical Criteria
Given Release status has been verified across all cargo records with the same car ID and waybill
When The system evaluates status consistency
Then If all records have the same release status, generate comprehensive release notification, otherwise proceed to create Merlin notifications for status changes
R-GCX016E-cbl-02379 Generate Comprehensive Release Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Comprehensive Release Notification' is invoked, and assuming that all cargo records with the same car id and waybill have consistent release status, when the system generates release notification, the desired outcome is that the system creates a comprehensive release notification covering all related cargo records.
💻 Technical Criteria
Given All cargo records with the same car ID and waybill have consistent release status
When The system generates release notification
Then The system creates a comprehensive release notification covering all related cargo records
R-GCX016E-cbl-02382 Create Merlin Notification for Status Changes
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Create Merlin Notification for Status Changes', assuming that cargo records with the same car id and waybill do not have consistent release status or arrival notifications have been processed, when the system creates merlin notifications, the desired outcome is that the system generates appropriate merlin messages for each cargo status change including disposition code details and cargo information.
💻 Technical Criteria
EXCLUDING Cargo records with the same car ID and waybill do not have consistent release status OR arrival notifications have been processed
When The system creates Merlin notifications
Then The system generates appropriate Merlin messages for each cargo status change including disposition code details and cargo information
R-GCX016E-cbl-02383 Update Final Status for All Related Records
Action Rules
📊 Business Logic Narrative
When the process 'Update Final Status for All Related Records' is invoked, and assuming that all notifications have been generated for cargo records with the same car id and waybill, when the system updates final status, the desired outcome is that the system commits all status changes and disposition code updates to all related cargo records in the database.
💻 Technical Criteria
Given All notifications have been generated for cargo records with the same car ID and waybill
When The system updates final status
Then The system commits all status changes and disposition code updates to all related cargo records in the database
R-GCX016E-cbl-03096 Retrieve All Cargo Records with Same Car ID and Waybill
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve All Cargo Records with Same Car ID and Waybill' is invoked, and assuming that a car id and waybill number are provided for verification, when the system searches for related cargo records, the desired outcome is that all cargo records with matching car id and waybill number are retrieved from the cargo database.
💻 Technical Criteria
Given A car ID and waybill number are provided for verification
When The system searches for related cargo records
Then All cargo records with matching car ID and waybill number are retrieved from the cargo database
R-GCX016E-cbl-03097 More Records Found?
Decision Rules
📊 Business Logic Narrative
When the process 'More Records Found?' is invoked, and assuming that a search for cargo records with matching car id and waybill has been performed, when the system checks for additional unprocessed records, the desired outcome is that if more records exist, continue processing individual records, otherwise proceed to status comparison.
💻 Technical Criteria
Given A search for cargo records with matching car ID and waybill has been performed
When The system checks for additional unprocessed records
Then If more records exist, continue processing individual records, otherwise proceed to status comparison
R-GCX016E-cbl-02384 Retrieve All Cargo Records with Same Car ID and Waybill
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve All Cargo Records with Same Car ID and Waybill' is invoked, and assuming that a cargo record exists with a specific car id and waybill number, when the system initiates cargo release verification process, the desired outcome is that all cargo records matching the same car id and waybill combination are retrieved for processing.
💻 Technical Criteria
Given A cargo record exists with a specific car ID and waybill number
When The system initiates cargo release verification process
Then All cargo records matching the same car ID and waybill combination are retrieved for processing
R-GCX016E-cbl-02396 All Records Released?
Decision Rules
📊 Business Logic Narrative
When the process 'All Records Released?' is invoked, and assuming that all cargo records in the car/waybill group have been individually analyzed, when the system evaluates the collective release status, the desired outcome is that if all records are released, proceed to generate comprehensive release notification; if any records remain held, end the release verification process.
💻 Technical Criteria
Given All cargo records in the car/waybill group have been individually analyzed
When The system evaluates the collective release status
Then If all records are released, proceed to generate comprehensive release notification; if any records remain held, end the release verification process
R-GCX016E-cbl-02397 Generate Comprehensive Release Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Comprehensive Release Notification' is invoked, and assuming that all cargo records with the same car id and waybill are confirmed as released, when the system generates release notification, the desired outcome is that a comprehensive release notification is created containing all relevant cargo and release information.
💻 Technical Criteria
Given All cargo records with the same car ID and waybill are confirmed as released
When The system generates release notification
Then A comprehensive release notification is created containing all relevant cargo and release information
R-GCX016E-cbl-02398 Format Release Message with Equipment Details
Process Rules
📊 Business Logic Narrative
When the process 'Format Release Message with Equipment Details' is invoked, and assuming that a comprehensive release notification is being created, when the system formats the release message, the desired outcome is that the message includes car id, waybill number, equipment type, and other relevant equipment identification details.
💻 Technical Criteria
Given A comprehensive release notification is being created
When The system formats the release message
Then The message includes car ID, waybill number, equipment type, and other relevant equipment identification details
R-GCX016E-cbl-02419 Foreign Bill Not Found in System
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Foreign Bill Not Found in System', assuming that a foreign bill of lading number is being processed, when the system searches for the bill and it is not found in the existing cargo database, the desired outcome is that the system should trigger the new cargo record creation process.
💻 Technical Criteria
EXCLUDING A foreign bill of lading number is being processed
When The system searches for the bill and it is not found in the existing cargo database
Then The system should trigger the new cargo record creation process
R-GCX016E-cbl-02423 Build Foreign Manifest from M10 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Build Foreign Manifest from M10 Segment' is invoked, and assuming that a new foreign cargo record is being created and m10 segment data is available, when the system processes the m10 segment information, the desired outcome is that the system should create a foreign manifest record with vessel name, manifest number, and related m10 segment data.
💻 Technical Criteria
Given A new foreign cargo record is being created and M10 segment data is available
When The system processes the M10 segment information
Then The system should create a foreign manifest record with vessel name, manifest number, and related M10 segment data
R-GCX016E-cbl-03118 Extract Cargo Data from X4 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Cargo Data from X4 Segment' is invoked, and assuming that an x4 segment containing cargo disposition data is available, when the system processes the x4 segment for foreign cargo setup, the desired outcome is that cargo data including waybill number, quantities, and disposition information are extracted for cargo record population.
💻 Technical Criteria
Given An X4 segment containing cargo disposition data is available
When The system processes the X4 segment for foreign cargo setup
Then Cargo data including waybill number, quantities, and disposition information are extracted for cargo record population
R-GCX016E-cbl-03119 Set Waybill Number and Quantities
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Waybill Number and Quantities' is invoked, and assuming that cargo data has been extracted from x4 segment, when the system processes waybill and quantity information, the desired outcome is that waybill number and cargo quantities are assigned to the appropriate fields in the cargo record.
💻 Technical Criteria
Given Cargo data has been extracted from X4 segment
When The system processes waybill and quantity information
Then Waybill number and cargo quantities are assigned to the appropriate fields in the cargo record
R-GCX016E-cbl-03457 Extract Manifest Number
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Manifest Number' is invoked, and assuming that port information has been mapped from m10 segment, when the system processes the manifest number field from m10 segment, the desired outcome is that the manifest number is extracted and prepared for foreign manifest structure.
💻 Technical Criteria
Given Port information has been mapped from M10 segment
When The system processes the manifest number field from M10 segment
Then The manifest number is extracted and prepared for foreign manifest structure
R-GCX016E-cbl-03458 Map Date Information
Definitional Rules
📊 Business Logic Narrative
When the process 'Map Date Information' is invoked, and assuming that manifest number has been extracted from m10 segment, when the system processes date fields from m10 segment, the desired outcome is that arrival and departure dates are mapped to the foreign manifest structure with proper formatting.
💻 Technical Criteria
Given Manifest number has been extracted from M10 segment
When The system processes date fields from M10 segment
Then Arrival and departure dates are mapped to the foreign manifest structure with proper formatting
R-GCX016E-cbl-02463 Add Car ID and Waybill Details
Process Rules
📊 Business Logic Narrative
When the process 'Add Car ID and Waybill Details' is invoked, and assuming that equipment information has been formatted in the merlin message, when car id and waybill details are available for the cargo, the desired outcome is that the system adds the car id and waybill number to the message content.
💻 Technical Criteria
Given Equipment information has been formatted in the Merlin message
When Car ID and waybill details are available for the cargo
Then The system adds the car ID and waybill number to the message content
R-GCX016E-cbl-02464 Include US-CCN Information
Process Rules
📊 Business Logic Narrative
When the process 'Include US-CCN Information' is invoked, and assuming that car id and waybill details have been added to the message, when us-ccn information is available for the cargo, the desired outcome is that the system includes the us-ccn in the message for customs tracking purposes.
💻 Technical Criteria
Given Car ID and waybill details have been added to the message
When US-CCN information is available for the cargo
Then The system includes the US-CCN in the message for customs tracking purposes
R-GCX016E-cbl-02465 Format Disposition Code Details
Process Rules
📊 Business Logic Narrative
When the process 'Format Disposition Code Details' is invoked, and assuming that us-ccn information has been included in the message, when a disposition code has been processed for the cargo, the desired outcome is that the system formats the disposition code and related details into the message.
💻 Technical Criteria
Given US-CCN information has been included in the message
When A disposition code has been processed for the cargo
Then The system formats the disposition code and related details into the message
R-GCX016E-cbl-02570 Add Car ID and Waybill Details
Computation Rules
📊 Business Logic Narrative
When the process 'Add Car ID and Waybill Details' is invoked, and assuming that car id and waybill information are available in the cargo record, when building comprehensive merlin message content, the desired outcome is that car id and waybill details are added to the message with proper formatting.
💻 Technical Criteria
Given Car ID and waybill information are available in the cargo record
When Building comprehensive Merlin message content
Then Car ID and waybill details are added to the message with proper formatting
R-GCX016E-cbl-02571 Include US-CCN Information
Computation Rules
📊 Business Logic Narrative
When the process 'Include US-CCN Information' is invoked, and assuming that us-ccn exists for the cargo being processed, when creating merlin notification message, the desired outcome is that us-ccn information is included in the message for cargo identification purposes.
💻 Technical Criteria
Given US-CCN exists for the cargo being processed
When Creating Merlin notification message
Then US-CCN information is included in the message for cargo identification purposes
R-GCX016E-cbl-02685 Include Waybill and CCN Details
Process Rules
📊 Business Logic Narrative
When the process 'Include Waybill and CCN Details' is invoked, and assuming that equipment information has been included in the email content, when the system processes waybill and ccn information for email inclusion, the desired outcome is that the system adds waybill numbers and ccn details to the email notification content.
💻 Technical Criteria
Given Equipment information has been included in the email content
When The system processes waybill and CCN information for email inclusion
Then The system adds waybill numbers and CCN details to the email notification content
R-GCX016E-cbl-02686 Include Content Description
Process Rules
📊 Business Logic Narrative
When the process 'Include Content Description' is invoked, and assuming that waybill and ccn details have been included in the email content, when the system processes cargo content description for email inclusion, the desired outcome is that the system adds detailed cargo content description to the email notification.
💻 Technical Criteria
Given Waybill and CCN details have been included in the email content
When The system processes cargo content description for email inclusion
Then The system adds detailed cargo content description to the email notification
R-GCX016E-cbl-02697 Prepare Email Message Content
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Email Message Content' is invoked, and assuming that a freight forwarder disposition code requires email notification and cargo information is available, when the system prepares the email message content, the desired outcome is that the email message includes cargo details (ccn, waybill, car id), equipment information, origin/destination data, consignee information, and disposition code messages.
💻 Technical Criteria
Given A freight forwarder disposition code requires email notification and cargo information is available
When The system prepares the email message content
Then The email message includes cargo details (CCN, waybill, car ID), equipment information, origin/destination data, consignee information, and disposition code messages
R-GCX016E-cbl-02711 Create Debug Information Header
Process Rules
📊 Business Logic Narrative
When the process 'Create Debug Information Header' is invoked, and assuming that a cargo status processing event requires debug logging, when the system initiates debug information capture, the desired outcome is that a debug header is created with cargo identification details including equipment id, waybill number, and us-ccn.
💻 Technical Criteria
Given A cargo status processing event requires debug logging
When The system initiates debug information capture
Then A debug header is created with cargo identification details including equipment ID, waybill number, and US-CCN
R-GCX016E-cbl-02761 Format Waybill Number
Process Rules
📊 Business Logic Narrative
When the process 'Format Waybill Number' is invoked, and assuming that a cargo record contains waybill number information, when the system processes waybill data for merlin reporting, the desired outcome is that the waybill number is formatted according to report requirements.
💻 Technical Criteria
Given A cargo record contains waybill number information
When The system processes waybill data for Merlin reporting
Then The waybill number is formatted according to report requirements
R-GCX016E-cbl-02762 Format US-CCN Information
Process Rules
📊 Business Logic Narrative
When the process 'Format US-CCN Information' is invoked, and assuming that a cargo record contains us-ccn information, when the system processes ccn data for merlin reporting, the desired outcome is that the us-ccn is formatted according to report standards.
💻 Technical Criteria
Given A cargo record contains US-CCN information
When The system processes CCN data for Merlin reporting
Then The US-CCN is formatted according to report standards
R-GCX016E-cbl-02795 Set Waybill Information in N7
Action Rules
📊 Business Logic Narrative
When the process 'Set Waybill Information in N7' is invoked, and assuming that an n7 segment is being populated and waybill data is available, when the system processes waybill information for the cargo, the desired outcome is that waybill information is populated into the n7 segment.
💻 Technical Criteria
Given An N7 segment is being populated and waybill data is available
When The system processes waybill information for the cargo
Then Waybill information is populated into the N7 segment
R-GCX016E-cbl-02825 Format Waybill Number
Computation Rules
📊 Business Logic Narrative
When the process 'Format Waybill Number' is invoked, and assuming that a cargo record contains waybill number information, when the waybill number formatting process is executed, the desired outcome is that the waybill number is formatted for consistent display in the report.
💻 Technical Criteria
Given A cargo record contains waybill number information
When The waybill number formatting process is executed
Then The waybill number is formatted for consistent display in the report
R-GCX016E-cbl-02826 Format US-CCN
Computation Rules
📊 Business Logic Narrative
When the process 'Format US-CCN' is invoked, and assuming that a cargo record contains us-ccn information, when the us-ccn formatting process is executed, the desired outcome is that the us-ccn is formatted with proper structure for report display.
💻 Technical Criteria
Given A cargo record contains US-CCN information
When The US-CCN formatting process is executed
Then The US-CCN is formatted with proper structure for report display
💰 Bond & Financial Auth 189 logic blocks
R-GCX016E-cbl-00035 25:In-Bond Broker Processing
Action Rules
📊 Business Logic Narrative
When the process '25:In-Bond Broker Processing' is invoked, and assuming that disposition code requires in-bond processing, when entry number and broker information are provided, the desired outcome is that update broker entry numbers with validation and set in-bond information for entry types 61, 62, 63, 69.
💻 Technical Criteria
Given Disposition code requires in-bond processing
When Entry number and broker information are provided
Then Update broker entry numbers with validation and set in-bond information for entry types 61, 62, 63, 69
R-GCX016E-cbl-00049 77:Comprehensive Merlin Message Formatting
Action Rules
📊 Business Logic Narrative
When the process '77:Comprehensive Merlin Message Formatting' is invoked, and assuming that k1 segment contains cp rail identifiers, when k1 segment contains 'director of customs, cp rail' or 'canadian pacific limited' or 'canadian pacific railway co', the desired outcome is that create broker bond creation message for cp rail.
💻 Technical Criteria
Given K1 segment contains CP Rail identifiers
When K1 segment contains 'DIRECTOR OF CUSTOMS, CP RAIL' or 'CANADIAN PACIFIC LIMITED' or 'CANADIAN PACIFIC RAILWAY CO'
Then Create broker bond creation message for CP Rail
R-GCX016E-cbl-03140 Canadian Border Crossing?
Decision Rules
📊 Business Logic Narrative
When the process 'Canadian Border Crossing?' is invoked, and assuming that cprs cross-border validation has been completed, when the system evaluates routing information to determine border crossing requirements, the desired outcome is that the system identifies canadian border crossings and routes to appropriate location mapping or proceeds to bond information processing.
💻 Technical Criteria
Given CPRS cross-border validation has been completed
When The system evaluates routing information to determine border crossing requirements
Then The system identifies Canadian border crossings and routes to appropriate location mapping or proceeds to bond information processing
R-GCX016E-cbl-03142 Validate CPRS Routing Rules
Validation Rules
📊 Business Logic Narrative
When the process 'Validate CPRS Routing Rules' is invoked, and assuming that us port to canadian location mapping has been completed, when the system validates routing against cprs routing rules and cross-border requirements, the desired outcome is that the system confirms routing compliance and proceeds to bond information processing.
💻 Technical Criteria
Given US port to Canadian location mapping has been completed
When The system validates routing against CPRS routing rules and cross-border requirements
Then The system confirms routing compliance and proceeds to bond information processing
R-GCX016E-cbl-03145 Generate K1 Bond Creation Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate K1 Bond Creation Message' is invoked, and assuming that canadian pacific railway bond has been configured, when the system generates bond creation messaging, the desired outcome is that the system creates k1 segment messages documenting the bond creation for canadian pacific railway operations.
💻 Technical Criteria
Given Canadian Pacific Railway bond has been configured
When The system generates bond creation messaging
Then The system creates K1 segment messages documenting the bond creation for Canadian Pacific Railway operations
R-GCX016E-cbl-00310 Create Merlin Notification for Bond
Action Rules
📊 Business Logic Narrative
When the process 'Create Merlin Notification for Bond' is invoked, and assuming that bond processing summary has been generated, when the system creates merlin notifications for the bond processing, the desired outcome is that appropriate merlin messages are generated and routed to relevant parties regarding the bond processing results.
💻 Technical Criteria
Given Bond processing summary has been generated
When The system creates Merlin notifications for the bond processing
Then Appropriate Merlin messages are generated and routed to relevant parties regarding the bond processing results
R-GCX016E-cbl-02885 Extract Bond Number from Message
Validation Rules
📊 Business Logic Narrative
When the process 'Extract Bond Number from Message' is invoked, and assuming that an incoming message contains bond number information, when the system processes the message to extract the bond number, the desired outcome is that the bond number is extracted and validated for proper format.
💻 Technical Criteria
Given An incoming message contains bond number information
When The system processes the message to extract the bond number
Then The bond number is extracted and validated for proper format
R-GCX016E-cbl-02886 Bond Number Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Bond Number Valid?' is invoked, and assuming that a bond number has been extracted from the message, when the system validates the bond number format, the desired outcome is that the bond number is accepted if it meets format requirements, otherwise processing is terminated with error.
💻 Technical Criteria
Given A bond number has been extracted from the message
When The system validates the bond number format
Then The bond number is accepted if it meets format requirements, otherwise processing is terminated with error
R-GCX016E-cbl-02890 Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Record Found?' is invoked, and assuming that a database lookup has been performed for a bond number, when the system checks the lookup results, the desired outcome is that processing continues if records are found, otherwise a bond not found error is generated.
💻 Technical Criteria
Given A database lookup has been performed for a bond number
When The system checks the lookup results
Then Processing continues if records are found, otherwise a bond not found error is generated
R-GCX016E-cbl-03190 Validate Against In-Bond Control Numbers
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Against In-Bond Control Numbers' is invoked, and assuming that an entry number has passed broker entry validation, when the system validates against in-bond control numbers, the desired outcome is that the entry number must also be valid against in-bond control number records.
💻 Technical Criteria
Given An entry number has passed broker entry validation
When The system validates against in-bond control numbers
Then The entry number must also be valid against in-bond control number records
R-GCX016E-cbl-03194 Set Master In-Bond Flag for Code 61
Action Rules
📊 Business Logic Narrative
When the process 'Set Master In-Bond Flag for Code 61' is invoked, and assuming that a valid entry with entry type code 61, when the system processes the entry type code, the desired outcome is that set the master in-bond flag to indicate this is a master in-bond entry.
💻 Technical Criteria
Given A valid entry with entry type code 61
When The system processes the entry type code
Then Set the master in-bond flag to indicate this is a master in-bond entry
R-GCX016E-cbl-03195 Set Master In-Bond Flag for Code 62
Action Rules
📊 Business Logic Narrative
When the process 'Set Master In-Bond Flag for Code 62' is invoked, and assuming that a valid entry with entry type code 62, when the system processes the entry type code, the desired outcome is that set the master in-bond flag to indicate this is a master in-bond entry.
💻 Technical Criteria
Given A valid entry with entry type code 62
When The system processes the entry type code
Then Set the master in-bond flag to indicate this is a master in-bond entry
R-GCX016E-cbl-03196 Set Master In-Bond Flag for Code 63
Action Rules
📊 Business Logic Narrative
When the process 'Set Master In-Bond Flag for Code 63' is invoked, and assuming that a valid entry with entry type code 63, when the system processes the entry type code, the desired outcome is that set the master in-bond flag to indicate this is a master in-bond entry.
💻 Technical Criteria
Given A valid entry with entry type code 63
When The system processes the entry type code
Then Set the master in-bond flag to indicate this is a master in-bond entry
R-GCX016E-cbl-03197 Set Master In-Bond Flag for Code 69
Action Rules
📊 Business Logic Narrative
When the process 'Set Master In-Bond Flag for Code 69' is invoked, and assuming that a valid entry with entry type code 69, when the system processes the entry type code, the desired outcome is that set the master in-bond flag to indicate this is a master in-bond entry.
💻 Technical Criteria
Given A valid entry with entry type code 69
When The system processes the entry type code
Then Set the master in-bond flag to indicate this is a master in-bond entry
R-GCX016E-cbl-03198 Process Standard Entry Type
Process Rules
📊 Business Logic Narrative
When the process 'Process Standard Entry Type' is invoked, and assuming that a valid entry with entry type code other than 61, 62, 63, or 69, when the system processes the entry type code, the desired outcome is that apply standard entry type processing without setting master in-bond flags.
💻 Technical Criteria
Given A valid entry with entry type code other than 61, 62, 63, or 69
When The system processes the entry type code
Then Apply standard entry type processing without setting master in-bond flags
R-GCX016E-cbl-03199 Update Broker Bond Information
Action Rules
📊 Business Logic Narrative
When the process 'Update Broker Bond Information' is invoked, and assuming that entry type processing has been completed, when the system updates broker bond information, the desired outcome is that update broker bond records with current entry information and bond details.
💻 Technical Criteria
Given Entry type processing has been completed
When The system updates broker bond information
Then Update broker bond records with current entry information and bond details
R-GCX016E-cbl-03200 CPRS Bond Processing Required?
Decision Rules
📊 Business Logic Narrative
When the process 'CPRS Bond Processing Required?' is invoked, and assuming that broker bond information has been updated, when the system checks for cprs bond processing requirements, the desired outcome is that if cprs bond processing is required, proceed with cprs bond assignment; otherwise, proceed to bond owner information.
💻 Technical Criteria
Given Broker bond information has been updated
When The system checks for CPRS bond processing requirements
Then If CPRS bond processing is required, proceed with CPRS bond assignment; otherwise, proceed to bond owner information
R-GCX016E-cbl-03201 Handle CPRS Bond Assignment
Action Rules
📊 Business Logic Narrative
When the process 'Handle CPRS Bond Assignment' is invoked, and assuming that cprs bond processing is required, when the system processes cprs bond assignment, the desired outcome is that assign appropriate cprs bond information and update bond records accordingly.
💻 Technical Criteria
Given CPRS bond processing is required
When The system processes CPRS bond assignment
Then Assign appropriate CPRS bond information and update bond records accordingly
R-GCX016E-cbl-03202 Update Broker QP Information
Action Rules
📊 Business Logic Narrative
When the process 'Update Broker QP Information' is invoked, and assuming that cprs bond assignment has been completed, when the system updates broker qp information, the desired outcome is that update broker qualified person information with current bond and entry details.
💻 Technical Criteria
Given CPRS bond assignment has been completed
When The system updates broker QP information
Then Update broker qualified person information with current bond and entry details
R-GCX016E-cbl-03203 Set Bond Owner Information
Action Rules
📊 Business Logic Narrative
When the process 'Set Bond Owner Information' is invoked, and assuming that all bond processing steps have been completed, when the system sets bond owner information, the desired outcome is that establish bond ownership details and finalize bond assignment for the entry.
💻 Technical Criteria
Given All bond processing steps have been completed
When The system sets bond owner information
Then Establish bond ownership details and finalize bond assignment for the entry
R-GCX016E-cbl-03205 Complete In-Bond Entry Processing
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Complete In-Bond Entry Processing', assuming that all in-bond entry processing steps have been completed successfully or entry number was not present, when the system finalizes in-bond entry processing, the desired outcome is that complete the in-bond entry processing and proceed to next processing stage.
💻 Technical Criteria
EXCLUDING All in-bond entry processing steps have been completed successfully or entry number was not present
When The system finalizes in-bond entry processing
Then Complete the in-bond entry processing and proceed to next processing stage
R-GCX016E-cbl-03360 Code Found in Table?
Validation Rules
📊 Business Logic Narrative
When the process 'Code Found in Table?' is invoked, and assuming that an edi entry type code has been searched in the conversion table, when the system evaluates whether the code was found in the lookup table, the desired outcome is that if code is found, retrieve the internal system value, otherwise generate an error message for invalid code.
💻 Technical Criteria
Given An EDI entry type code has been searched in the conversion table
When The system evaluates whether the code was found in the lookup table
Then If code is found, retrieve the internal system value, otherwise generate an error message for invalid code
R-GCX016E-cbl-03361 Retrieve Internal System Value
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Internal System Value' is invoked, and assuming that the edi entry type code is found in the conversion lookup table, when the system retrieves the corresponding internal value from the same array position, the desired outcome is that the internal system entry type value is obtained for further processing.
💻 Technical Criteria
Given The EDI entry type code is found in the conversion lookup table
When The system retrieves the corresponding internal value from the same array position
Then The internal system entry type value is obtained for further processing
R-GCX016E-cbl-03362 Border Crossing Code?
Decision Rules
📊 Business Logic Narrative
When the process 'Border Crossing Code?' is invoked, and assuming that an internal system entry type value has been retrieved from the conversion table, when the system evaluates whether the entry type code indicates a border crossing, the desired outcome is that if it is a border crossing code, apply special border crossing logic, otherwise proceed with standard in-bond flag processing.
💻 Technical Criteria
Given An internal system entry type value has been retrieved from the conversion table
When The system evaluates whether the entry type code indicates a border crossing
Then If it is a border crossing code, apply special border crossing logic, otherwise proceed with standard in-bond flag processing
R-GCX016E-cbl-00335 Validate DC95 in Disposition Code Table
Validation Rules
📊 Business Logic Narrative
When the process 'Validate DC95 in Disposition Code Table' is invoked, and assuming that a disposition code 95 is being processed for bond cancellation, when the system looks up dc95 in the disposition code table, the desired outcome is that the system confirms dc95 is a valid disposition code or generates an error if not found.
💻 Technical Criteria
Given A disposition code 95 is being processed for bond cancellation
When The system looks up DC95 in the disposition code table
Then The system confirms DC95 is a valid disposition code or generates an error if not found
R-GCX016E-cbl-00341 Reset In-Bond Entry Status
Action Rules
📊 Business Logic Narrative
When the process 'Reset In-Bond Entry Status' is invoked, and assuming that a disposition code 95 is being processed for bond cancellation, when the system resets bond information, the desired outcome is that the in-bond entry status is reset to indicate no active bond.
💻 Technical Criteria
Given A disposition code 95 is being processed for bond cancellation
When The system resets bond information
Then The in-bond entry status is reset to indicate no active bond
R-GCX016E-cbl-00344 Generate Merlin Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Merlin Notification' is invoked, and assuming that a disposition code 95 has been processed and bond cancellation completed, when the system generates notifications, the desired outcome is that a merlin notification is generated to inform relevant parties of the bond cancellation.
💻 Technical Criteria
Given A disposition code 95 has been processed and bond cancellation completed
When The system generates notifications
Then A Merlin notification is generated to inform relevant parties of the bond cancellation
R-GCX016E-cbl-00348 Entry Number Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Entry Number Valid?' is invoked, and assuming that an in-bond entry number has been submitted for validation, when the validation process completes, the desired outcome is that the system either accepts the entry number for further processing or rejects it with error handling.
💻 Technical Criteria
Given An in-bond entry number has been submitted for validation
When The validation process completes
Then The system either accepts the entry number for further processing or rejects it with error handling
R-GCX016E-cbl-00350 Validate Against In-Bond Control Numbers
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Against In-Bond Control Numbers' is invoked, and assuming that the entry number has passed broker validation, when the system validates against in-bond control numbers, the desired outcome is that the entry number is confirmed to match in-bond control number requirements.
💻 Technical Criteria
Given The entry number has passed broker validation
When The system validates against in-bond control numbers
Then The entry number is confirmed to match in-bond control number requirements
R-GCX016E-cbl-00353 134: Master In-Bond Flag Setting for Code 61
Process Rules
📊 Business Logic Narrative
When the process '134: Master In-Bond Flag Setting for Code 61' is invoked, and assuming that the entry type code is determined to be 61, when the system processes the in-bond flag setting, the desired outcome is that master in-bond flags are set according to entry type 61 business rules.
💻 Technical Criteria
Given The entry type code is determined to be 61
When The system processes the in-bond flag setting
Then Master in-bond flags are set according to entry type 61 business rules
R-GCX016E-cbl-00354 134: Master In-Bond Flag Setting for Code 62
Process Rules
📊 Business Logic Narrative
When the process '134: Master In-Bond Flag Setting for Code 62' is invoked, and assuming that the entry type code is determined to be 62, when the system processes the in-bond flag setting, the desired outcome is that master in-bond flags are set according to entry type 62 business rules.
💻 Technical Criteria
Given The entry type code is determined to be 62
When The system processes the in-bond flag setting
Then Master in-bond flags are set according to entry type 62 business rules
R-GCX016E-cbl-00355 134: Master In-Bond Flag Setting for Code 63
Process Rules
📊 Business Logic Narrative
When the process '134: Master In-Bond Flag Setting for Code 63' is invoked, and assuming that the entry type code is determined to be 63, when the system processes the in-bond flag setting, the desired outcome is that master in-bond flags are set according to entry type 63 business rules.
💻 Technical Criteria
Given The entry type code is determined to be 63
When The system processes the in-bond flag setting
Then Master in-bond flags are set according to entry type 63 business rules
R-GCX016E-cbl-00356 134: Master In-Bond Flag Setting for Code 69
Process Rules
📊 Business Logic Narrative
When the process '134: Master In-Bond Flag Setting for Code 69' is invoked, and assuming that the entry type code is determined to be 69, when the system processes the in-bond flag setting, the desired outcome is that master in-bond flags are set according to entry type 69 business rules.
💻 Technical Criteria
Given The entry type code is determined to be 69
When The system processes the in-bond flag setting
Then Master in-bond flags are set according to entry type 69 business rules
R-GCX016E-cbl-00357 Process Other Entry Type Codes
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Process Other Entry Type Codes', assuming that the entry type code is not 61, 62, 63, or 69, when the system processes the other entry type, the desired outcome is that standard in-bond processing rules are applied for the non-specific entry type.
💻 Technical Criteria
EXCLUDING The entry type code is not 61, 62, 63, or 69
When The system processes the other entry type
Then Standard in-bond processing rules are applied for the non-specific entry type
R-GCX016E-cbl-00365 Entry Type = 61, 62, 63, or 69?
Decision Rules
📊 Business Logic Narrative
When the process 'Entry Type = 61, 62, 63, or 69?' is invoked, and assuming that an internal entry type code has been successfully set, when the system checks if the entry type is 61, 62, 63, or 69, the desired outcome is that if entry type matches in-bond codes, set master in-bond flag; otherwise proceed to border crossing check.
💻 Technical Criteria
Given An internal entry type code has been successfully set
When The system checks if the entry type is 61, 62, 63, or 69
Then If entry type matches in-bond codes, set master in-bond flag; otherwise proceed to border crossing check
R-GCX016E-cbl-00366 Set Master In-Bond Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Master In-Bond Flag' is invoked, and assuming that the entry type code is identified as 61, 62, 63, or 69, when the system processes the in-bond entry type, the desired outcome is that set the master in-bond flag to indicate special in-bond processing is required.
💻 Technical Criteria
Given The entry type code is identified as 61, 62, 63, or 69
When The system processes the in-bond entry type
Then Set the master in-bond flag to indicate special in-bond processing is required
R-GCX016E-cbl-00448 Extract Bond Number from Message
Validation Rules
📊 Business Logic Narrative
When the process 'Extract Bond Number from Message' is invoked, and assuming that an incoming message contains bond number information in the message structure, when the system processes the message to extract the bond number, the desired outcome is that the bond number is extracted from the message and made available for validation.
💻 Technical Criteria
Given An incoming message contains bond number information in the message structure
When The system processes the message to extract the bond number
Then The bond number is extracted from the message and made available for validation
R-GCX016E-cbl-00449 Bond Number Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Bond Number Valid?' is invoked, and assuming that a bond number has been extracted from the message, when the system validates the bond number format and content, the desired outcome is that if the bond number is valid, processing continues; if invalid, an error is generated.
💻 Technical Criteria
Given A bond number has been extracted from the message
When The system validates the bond number format and content
Then If the bond number is valid, processing continues; if invalid, an error is generated
R-GCX016E-cbl-00457 More Records with Same Bond?
Decision Rules
📊 Business Logic Narrative
When the process 'More Records with Same Bond?' is invoked, and assuming that additional record check has been performed, when the system evaluates if more records exist with the same bond number, the desired outcome is that if more records exist, they are retrieved; if no more records, processing continues with current records.
💻 Technical Criteria
Given Additional record check has been performed
When The system evaluates if more records exist with the same bond number
Then If more records exist, they are retrieved; if no more records, processing continues with current records
R-GCX016E-cbl-00463 Log Bond Lookup Failure
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Bond Lookup Failure', assuming that a bond not found error has been generated, when the system handles the error condition, the desired outcome is that the bond lookup failure is logged with relevant details for audit purposes.
💻 Technical Criteria
EXCLUDING A bond not found error has been generated
When The system handles the error condition
Then The bond lookup failure is logged with relevant details for audit purposes
R-GCX016E-cbl-00464 Continue with Next Message
Process Rules
📊 Business Logic Narrative
When the process 'Continue with Next Message' is invoked, and assuming that bond lookup failure has been logged, when the system completes error handling for the current message, the desired outcome is that processing continues with the next available message in the queue.
💻 Technical Criteria
Given Bond lookup failure has been logged
When The system completes error handling for the current message
Then Processing continues with the next available message in the queue
R-GCX016E-cbl-00524 Special K1 Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Special K1 Type?' is invoked, and assuming that a k1 message is associated with a disposition code, when the system evaluates k1 content for special processing requirements, the desired outcome is that the k1 message is classified as either requiring special bond creation processing or standard remark processing.
💻 Technical Criteria
Given A K1 message is associated with a disposition code
When The system evaluates K1 content for special processing requirements
Then The K1 message is classified as either requiring special bond creation processing or standard remark processing
R-GCX016E-cbl-00525 Canadian Pacific Railway Bond Creation
Action Rules
📊 Business Logic Narrative
When the process 'Canadian Pacific Railway Bond Creation' is invoked, and assuming that a k1 message contains canadian pacific railway identifiers such as 'director of customs, cp rail', 'canadian pacific limited', or 'canadian pacific railway co', when the system processes the special k1 type, the desired outcome is that a broker bond creation message is generated for canadian pacific railway processing.
💻 Technical Criteria
Given A K1 message contains Canadian Pacific Railway identifiers such as 'DIRECTOR OF CUSTOMS, CP RAIL', 'CANADIAN PACIFIC LIMITED', or 'CANADIAN PACIFIC RAILWAY CO'
When The system processes the special K1 type
Then A broker bond creation message is generated for Canadian Pacific Railway processing
R-GCX016E-cbl-00526 Standard K1 Remark
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Standard K1 Remark', assuming that a k1 message does not require special bond creation processing, when the system processes the k1 message type, the desired outcome is that the k1 message is processed as a standard remark for inclusion in notifications.
💻 Technical Criteria
EXCLUDING A K1 message does not require special bond creation processing
When The system processes the K1 message type
Then The K1 message is processed as a standard remark for inclusion in notifications
R-GCX016E-cbl-00527 Add to Merlin Message
Process Rules
📊 Business Logic Narrative
When the process 'Add to Merlin Message' is invoked, and assuming that a k1 message has been processed as either special bond creation or standard remark, when the system prepares merlin notifications, the desired outcome is that the k1 message content is added to appropriate merlin messages for distribution.
💻 Technical Criteria
Given A K1 message has been processed as either special bond creation or standard remark
When The system prepares Merlin notifications
Then The K1 message content is added to appropriate Merlin messages for distribution
R-GCX016E-cbl-03233 Recovery Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'Recovery Successful?' is invoked, and assuming that segment reconstruction has been attempted, when the system evaluates reconstruction results, the desired outcome is that if reconstruction successful, proceed to sequence verification, otherwise use default segment values.
💻 Technical Criteria
Given Segment reconstruction has been attempted
When The system evaluates reconstruction results
Then If reconstruction successful, proceed to sequence verification, otherwise use default segment values
R-GCX016E-cbl-03234 Use Default Segment Values
Process Rules
📊 Business Logic Narrative
When the process 'Use Default Segment Values' is invoked, and assuming that segment reconstruction has failed, when the system cannot recover valid segment data, the desired outcome is that default segment values are applied and validation is marked as failed.
💻 Technical Criteria
Given Segment reconstruction has failed
When The system cannot recover valid segment data
Then Default segment values are applied and validation is marked as failed
R-GCX016E-cbl-03509 Format Error Message with Code Details
Process Rules
📊 Business Logic Narrative
When the process 'Format Error Message with Code Details' is invoked, and assuming that an unknown disposition code has been detected, when the system formats the error message, the desired outcome is that the error message includes the invalid disposition code value and descriptive details about the error.
💻 Technical Criteria
Given An unknown disposition code has been detected
When The system formats the error message
Then The error message includes the invalid disposition code value and descriptive details about the error
R-GCX016E-cbl-00674 Process Broker Bond Information
Process Rules
📊 Business Logic Narrative
When the process 'Process Broker Bond Information' is invoked, and assuming that bond assignment has been created or updated, when the system processes broker bond information, the desired outcome is that broker details are validated and associated with the bond assignment.
💻 Technical Criteria
Given Bond assignment has been created or updated
When The system processes broker bond information
Then Broker details are validated and associated with the bond assignment
R-GCX016E-cbl-00675 Broker Information Available?
Decision Rules
📊 Business Logic Narrative
When the process 'Broker Information Available?' is invoked, and assuming that broker bond information processing has started, when the system checks for available broker information in the broker table, the desired outcome is that if broker information exists, assign broker to bond, otherwise set default broker information.
💻 Technical Criteria
Given Broker bond information processing has started
When The system checks for available broker information in the broker table
Then If broker information exists, assign broker to bond, otherwise set default broker information
R-GCX016E-cbl-00676 Assign Broker to Bond
Action Rules
📊 Business Logic Narrative
When the process 'Assign Broker to Bond' is invoked, and assuming that broker information is available for the bond, when the system assigns the broker to the bond, the desired outcome is that broker id, name, and contact information are associated with the bond record.
💻 Technical Criteria
Given Broker information is available for the bond
When The system assigns the broker to the bond
Then Broker ID, name, and contact information are associated with the bond record
R-GCX016E-cbl-00677 Set Default Broker Information
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Default Broker Information', assuming that broker information is not available for the bond, when the system sets default broker information, the desired outcome is that default broker id and standard broker information are assigned to the bond.
💻 Technical Criteria
EXCLUDING Broker information is not available for the bond
When The system sets default broker information
Then Default broker ID and standard broker information are assigned to the bond
R-GCX016E-cbl-00678 Update Bond Owner Information
Action Rules
📊 Business Logic Narrative
When the process 'Update Bond Owner Information' is invoked, and assuming that broker has been assigned to the bond or default broker information has been set, when the system updates bond owner information, the desired outcome is that bond owner details are updated with current broker information and ownership status.
💻 Technical Criteria
Given Broker has been assigned to the bond or default broker information has been set
When The system updates bond owner information
Then Bond owner details are updated with current broker information and ownership status
R-GCX016E-cbl-00680 Set CPRS Bond Flags
Action Rules
📊 Business Logic Narrative
When the process 'Set CPRS Bond Flags' is invoked, and assuming that previous bond data has been cleared, when the system sets cprs bond flags, the desired outcome is that cprs-specific flags are set to indicate bond type, processing status, and special handling requirements.
💻 Technical Criteria
Given Previous bond data has been cleared
When The system sets CPRS bond flags
Then CPRS-specific flags are set to indicate bond type, processing status, and special handling requirements
R-GCX016E-cbl-00681 Log Bond Assignment Action
Action Rules
📊 Business Logic Narrative
When the process 'Log Bond Assignment Action' is invoked, and assuming that cprs bond flags have been set, when the system logs the bond assignment action, the desired outcome is that bond assignment details, timestamp, and processing information are recorded in the status segments.
💻 Technical Criteria
Given CPRS bond flags have been set
When The system logs the bond assignment action
Then Bond assignment details, timestamp, and processing information are recorded in the status segments
R-GCX016E-cbl-00683 Send K1 Message for Bond Creation
Action Rules
📊 Business Logic Narrative
When the process 'Send K1 Message for Bond Creation' is invoked, and assuming that bond creation notification has been generated, when the system sends k1 message for bond creation, the desired outcome is that k1 message with bond creation details is transmitted to the appropriate recipients.
💻 Technical Criteria
Given Bond creation notification has been generated
When The system sends K1 message for bond creation
Then K1 message with bond creation details is transmitted to the appropriate recipients
R-GCX016E-cbl-00758 Format Before/After Quantity Comparison
Action Rules
📊 Business Logic Narrative
When the process 'Format Before/After Quantity Comparison' is invoked, and assuming that quantity impact has been calculated, when formatting information for notifications, the desired outcome is that before and after quantity values are formatted for comparison display.
💻 Technical Criteria
Given Quantity impact has been calculated
When Formatting information for notifications
Then Before and after quantity values are formatted for comparison display
R-GCX016E-cbl-00759 Log Quantity Change in Audit Trail
Action Rules
📊 Business Logic Narrative
When the process 'Log Quantity Change in Audit Trail' is invoked, and assuming that quantity comparison has been formatted, when recording the transaction, the desired outcome is that the quantity change is logged in the audit trail with before/after values and disposition code information.
💻 Technical Criteria
Given Quantity comparison has been formatted
When Recording the transaction
Then The quantity change is logged in the audit trail with before/after values and disposition code information
R-GCX016E-cbl-00827 Evaluate Proceed Conditions
Decision Rules
📊 Business Logic Narrative
When the process 'Evaluate Proceed Conditions' is invoked, and assuming that a proceed status flag has been set or release evaluation is complete, when the system evaluates proceed-specific business conditions (in-bond requirements, entry type validation), the desired outcome is that proceed conditions are assessed to determine if in-bond proceed business flag should be activated.
💻 Technical Criteria
Given A proceed status flag has been set or release evaluation is complete
When The system evaluates proceed-specific business conditions (in-bond requirements, entry type validation)
Then Proceed conditions are assessed to determine if in-bond proceed business flag should be activated
R-GCX016E-cbl-03402 Apply Proceed Code Hierarchy
Policy Rules
📊 Business Logic Narrative
When the process 'Apply Proceed Code Hierarchy' is invoked, and assuming that a disposition code is classified as a proceed code type, when regulatory hierarchy processing is applied, the desired outcome is that the system applies proceed-specific precedence rules including in-bond processing requirements and entry type validations.
💻 Technical Criteria
Given A disposition code is classified as a Proceed Code type
When Regulatory hierarchy processing is applied
Then The system applies proceed-specific precedence rules including in-bond processing requirements and entry type validations
R-GCX016E-cbl-01031 Transport Type Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Transport Type Valid?' is invoked, and assuming that a transport type has been extracted from the m10 segment, when the system validates the transport type against acceptable values, the desired outcome is that the transport type is determined to be valid if it matches recognized transportation modes, otherwise it is invalid.
💻 Technical Criteria
Given A transport type has been extracted from the M10 segment
When The system validates the transport type against acceptable values
Then The transport type is determined to be valid if it matches recognized transportation modes, otherwise it is invalid
R-GCX016E-cbl-01036 Populate Vessel Name Field
Process Rules
📊 Business Logic Narrative
When the process 'Populate Vessel Name Field' is invoked, and assuming that vessel details have been extracted from the input segment, when the system populates the vessel name field in the m10 segment, the desired outcome is that the vessel name field is set with the extracted vessel name value.
💻 Technical Criteria
Given Vessel details have been extracted from the input segment
When The system populates the vessel name field in the M10 segment
Then The vessel name field is set with the extracted vessel name value
R-GCX016E-cbl-01037 Populate Transport Mode Field
Process Rules
📊 Business Logic Narrative
When the process 'Populate Transport Mode Field' is invoked, and assuming that a valid or default transport type has been determined, when the system populates the transport mode field in the m10 segment, the desired outcome is that the transport mode field is set with the validated transport type value.
💻 Technical Criteria
Given A valid or default transport type has been determined
When The system populates the transport mode field in the M10 segment
Then The transport mode field is set with the validated transport type value
R-GCX016E-cbl-01038 Populate Country of Origin Field
Process Rules
📊 Business Logic Narrative
When the process 'Populate Country of Origin Field' is invoked, and assuming that a valid or default country code has been determined, when the system populates the country of origin field in the m10 segment, the desired outcome is that the country of origin field is set with the validated country code value.
💻 Technical Criteria
Given A valid or default country code has been determined
When The system populates the country of origin field in the M10 segment
Then The country of origin field is set with the validated country code value
R-GCX016E-cbl-01039 Populate SCAC Field
Process Rules
📊 Business Logic Narrative
When the process 'Populate SCAC Field' is invoked, and assuming that a valid or default scac code has been determined, when the system populates the scac field in the m10 segment, the desired outcome is that the scac field is set with the validated scac code value.
💻 Technical Criteria
Given A valid or default SCAC code has been determined
When The system populates the SCAC field in the M10 segment
Then The SCAC field is set with the validated SCAC code value
R-GCX016E-cbl-01115 Bond Creation Scenario?
Decision Rules
📊 Business Logic Narrative
When the process 'Bond Creation Scenario?' is invoked, and assuming that k1 segment comments contain canadian pacific railway identifiers, when the system checks for bond creation scenarios during message formatting, the desired outcome is that the system identifies cp rail transactions by detecting 'director of customs, cp rail', 'canadian pacific limited', or 'canadian pacific railway co' in k1 comments.
💻 Technical Criteria
Given K1 segment comments contain Canadian Pacific Railway identifiers
When The system checks for bond creation scenarios during message formatting
Then The system identifies CP Rail transactions by detecting 'DIRECTOR OF CUSTOMS, CP RAIL', 'CANADIAN PACIFIC LIMITED', or 'CANADIAN PACIFIC RAILWAY CO' in K1 comments
R-GCX016E-cbl-01116 Format Canadian Pacific Railway Bond Creation Message
Process Rules
📊 Business Logic Narrative
When the process 'Format Canadian Pacific Railway Bond Creation Message' is invoked, and assuming that a canadian pacific railway transaction has been identified requiring bond creation messaging, when the system formats the cp rail bond creation message, the desired outcome is that the system creates a broker bond creation message with cp rail specific formatting and routing information.
💻 Technical Criteria
Given A Canadian Pacific Railway transaction has been identified requiring bond creation messaging
When The system formats the CP Rail bond creation message
Then The system creates a broker bond creation message with CP Rail specific formatting and routing information
R-GCX016E-cbl-03042 Bond Creation Scenario?
Decision Rules
📊 Business Logic Narrative
When the process 'Bond Creation Scenario?' is invoked, and assuming that k1 segment comments are being processed, when the system evaluates bond creation conditions, the desired outcome is that processing is routed to bond creation if cp rail identifiers are found, otherwise continues to date/time processing.
💻 Technical Criteria
Given K1 segment comments are being processed
When The system evaluates bond creation conditions
Then Processing is routed to bond creation if CP Rail identifiers are found, otherwise continues to date/time processing
R-GCX016E-cbl-03043 Process Canadian Pacific Railway Bond Creation
Process Rules
📊 Business Logic Narrative
When the process 'Process Canadian Pacific Railway Bond Creation' is invoked, and assuming that cp rail identifiers are detected in k1 comments, when the system processes bond creation scenario, the desired outcome is that special canadian pacific railway bond creation processing is performed.
💻 Technical Criteria
Given CP Rail identifiers are detected in K1 comments
When The system processes bond creation scenario
Then Special Canadian Pacific Railway bond creation processing is performed
R-GCX016E-cbl-03044 Add Bond Creation Notification
Process Rules
📊 Business Logic Narrative
When the process 'Add Bond Creation Notification' is invoked, and assuming that canadian pacific railway bond creation has been processed, when the system adds notification content, the desired outcome is that bond creation notification is added to the merlin message.
💻 Technical Criteria
Given Canadian Pacific Railway bond creation has been processed
When The system adds notification content
Then Bond creation notification is added to the Merlin message
R-GCX016E-cbl-03280 Canadian Pacific Railway Bond Creation
Decision Rules
📊 Business Logic Narrative
When the process 'Canadian Pacific Railway Bond Creation' is invoked, and assuming that a k1 comment has been classified as special comment type, when the comment content contains 'director of customs, cp rail' or 'canadian pacific limited' or 'canadian pacific railway co', the desired outcome is that the system triggers canadian pacific railway bond creation processing and generates appropriate broker bond messages.
💻 Technical Criteria
Given A K1 comment has been classified as special comment type
When The comment content contains 'DIRECTOR OF CUSTOMS, CP RAIL' or 'CANADIAN PACIFIC LIMITED' or 'CANADIAN PACIFIC RAILWAY CO'
Then The system triggers Canadian Pacific Railway bond creation processing and generates appropriate broker bond messages
R-GCX016E-cbl-03415 Identify as CPR Bond Creation Comment
Decision Rules
📊 Business Logic Narrative
When the process 'Identify as CPR Bond Creation Comment' is invoked, and assuming that a k1 segment comment is received for processing, when the comment text contains 'director of customs, cp rail' or 'canadian pacific limited' or 'canadian pacific railway co', the desired outcome is that the system identifies this as a cpr bond creation comment and sets the special comment flag for broker bond message generation.
💻 Technical Criteria
Given A K1 segment comment is received for processing
When The comment text contains 'DIRECTOR OF CUSTOMS, CP RAIL' OR 'CANADIAN PACIFIC LIMITED' OR 'CANADIAN PACIFIC RAILWAY CO'
Then The system identifies this as a CPR bond creation comment and sets the special comment flag for broker bond message generation
R-GCX016E-cbl-03416 Identify as Standard Comment
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Identify as Standard Comment', assuming that a k1 segment comment is received for processing, when the comment text does not contain any canadian pacific railway bond creation keywords, the desired outcome is that the system identifies this as a standard comment and sets the standard comment flag for regular comment processing.
💻 Technical Criteria
EXCLUDING A K1 segment comment is received for processing
When The comment text does not contain any Canadian Pacific Railway bond creation keywords
Then The system identifies this as a standard comment and sets the standard comment flag for regular comment processing
R-GCX016E-cbl-03418 Analyze Comment Content
Decision Rules
📊 Business Logic Narrative
When the process 'Analyze Comment Content' is invoked, and assuming that k1 comment text has been extracted, when the system analyzes the comment content for specific keywords, the desired outcome is that the system determines whether the comment requires special cpr bond processing or standard comment handling.
💻 Technical Criteria
Given K1 comment text has been extracted
When The system analyzes the comment content for specific keywords
Then The system determines whether the comment requires special CPR bond processing or standard comment handling
R-GCX016E-cbl-03419 Set Special Comment Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Special Comment Flag' is invoked, and assuming that a k1 comment has been identified as a cpr bond creation comment, when the system processes the comment classification, the desired outcome is that a special comment flag is set to indicate this comment requires broker bond message generation.
💻 Technical Criteria
Given A K1 comment has been identified as a CPR bond creation comment
When The system processes the comment classification
Then A special comment flag is set to indicate this comment requires broker bond message generation
R-GCX016E-cbl-03422 Route to Appropriate Handler
Action Rules
📊 Business Logic Narrative
When the process 'Route to Appropriate Handler' is invoked, and assuming that a k1 comment has been classified and stored with appropriate flags, when the system determines the next processing step, the desired outcome is that the comment is routed to either the cpr bond creation handler or the standard comment handler based on the classification flags.
💻 Technical Criteria
Given A K1 comment has been classified and stored with appropriate flags
When The system determines the next processing step
Then The comment is routed to either the CPR bond creation handler or the standard comment handler based on the classification flags
R-GCX016E-cbl-03530 Canadian Pacific Railway Bond Creation Pattern
Decision Rules
📊 Business Logic Narrative
When the process 'Canadian Pacific Railway Bond Creation Pattern' is invoked, and assuming that k1 segment comment text content is available for analysis, when the comment contains 'director of customs, cp rail' or 'canadian pacific limited' or 'canadian pacific railway co', the desired outcome is that the system identifies this as a canadian pacific railway bond creation pattern and sets the bond creation processing flag.
💻 Technical Criteria
Given K1 segment comment text content is available for analysis
When The comment contains 'DIRECTOR OF CUSTOMS, CP RAIL' OR 'CANADIAN PACIFIC LIMITED' OR 'CANADIAN PACIFIC RAILWAY CO'
Then The system identifies this as a Canadian Pacific Railway bond creation pattern and sets the bond creation processing flag
R-GCX016E-cbl-03534 Set Bond Creation Processing Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Bond Creation Processing Flag' is invoked, and assuming that canadian pacific railway bond creation pattern has been detected in the comment, when the system processes the pattern detection result, the desired outcome is that the bond creation processing flag is set to indicate special bond processing is required.
💻 Technical Criteria
Given Canadian Pacific Railway bond creation pattern has been detected in the comment
When The system processes the pattern detection result
Then The bond creation processing flag is set to indicate special bond processing is required
R-GCX016E-cbl-01122 Message Type Check
Decision Rules
📊 Business Logic Narrative
When the process 'Message Type Check' is invoked, and assuming that a k1 message segment is received for processing, when the system checks the k1 free-form text content for canadian pacific railway identifiers including 'director of customs, cp rail', 'canadian pacific limited', or 'canadian pacific railway co', the desired outcome is that the message is classified as a cp rail bond creation request and routed for specialized bond processing.
💻 Technical Criteria
Given A K1 message segment is received for processing
When The system checks the K1 free-form text content for Canadian Pacific Railway identifiers including 'DIRECTOR OF CUSTOMS, CP RAIL', 'CANADIAN PACIFIC LIMITED', or 'CANADIAN PACIFIC RAILWAY CO'
Then The message is classified as a CP Rail bond creation request and routed for specialized bond processing
R-GCX016E-cbl-01123 Extract K1 Free-Form Text
Process Rules
📊 Business Logic Narrative
When the process 'Extract K1 Free-Form Text' is invoked, and assuming that a k1 message segment identified as cp rail bond creation, when the system processes the k1 segment to extract free-form text content, the desired outcome is that the k1 text content is captured and made available for bond validation and notification formatting.
💻 Technical Criteria
Given A K1 message segment identified as CP Rail bond creation
When The system processes the K1 segment to extract free-form text content
Then The K1 text content is captured and made available for bond validation and notification formatting
R-GCX016E-cbl-01124 Validate Bond Creation Request
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Bond Creation Request' is invoked, and assuming that k1 text content has been extracted from a cp rail bond creation message, when the system validates the bond creation request against broker database information and business rules, the desired outcome is that the bond creation request is either approved for notification processing or rejected with appropriate error handling.
💻 Technical Criteria
Given K1 text content has been extracted from a CP Rail bond creation message
When The system validates the bond creation request against broker database information and business rules
Then The bond creation request is either approved for notification processing or rejected with appropriate error handling
R-GCX016E-cbl-01128 Create Comprehensive Merlin Message
Process Rules
📊 Business Logic Narrative
When the process 'Create Comprehensive Merlin Message' is invoked, and assuming that all bond creation notification components have been prepared including special comments and processing details, when the system assembles the comprehensive merlin message with all components properly formatted, the desired outcome is that a complete merlin message is created ready for routing to appropriate recipients.
💻 Technical Criteria
Given All bond creation notification components have been prepared including special comments and processing details
When The system assembles the comprehensive Merlin message with all components properly formatted
Then A complete Merlin message is created ready for routing to appropriate recipients
R-GCX016E-cbl-01129 Route to Appropriate Recipients
Action Rules
📊 Business Logic Narrative
When the process 'Route to Appropriate Recipients' is invoked, and assuming that a comprehensive bond creation merlin message has been created, when the system determines routing based on broker configuration and notification preferences, the desired outcome is that the message is routed to the appropriate recipients including brokers, customs officials, and system administrators.
💻 Technical Criteria
Given A comprehensive bond creation Merlin message has been created
When The system determines routing based on broker configuration and notification preferences
Then The message is routed to the appropriate recipients including brokers, customs officials, and system administrators
R-GCX016E-cbl-01130 Send Bond Creation Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send Bond Creation Notification' is invoked, and assuming that a bond creation notification message has been routed to appropriate recipients, when the system transmits the notification through the merlin messaging system, the desired outcome is that the bond creation notification is successfully delivered to all designated recipients.
💻 Technical Criteria
Given A bond creation notification message has been routed to appropriate recipients
When The system transmits the notification through the Merlin messaging system
Then The bond creation notification is successfully delivered to all designated recipients
R-GCX016E-cbl-01131 Log Bond Creation Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Bond Creation Action' is invoked, and assuming that a bond creation notification has been successfully transmitted, when the system logs the bond creation action with relevant details and timestamps, the desired outcome is that the bond creation action is recorded in the system audit trail for compliance and tracking purposes.
💻 Technical Criteria
Given A bond creation notification has been successfully transmitted
When The system logs the bond creation action with relevant details and timestamps
Then The bond creation action is recorded in the system audit trail for compliance and tracking purposes
R-GCX016E-cbl-01140 Format Before Quantity Display
Process Rules
📊 Business Logic Narrative
When the process 'Format Before Quantity Display' is invoked, and assuming that current release quantity value, when impact report formatting is performed, the desired outcome is that the current quantity is formatted for display as the 'before' value in the impact message.
💻 Technical Criteria
Given Current release quantity value
When Impact report formatting is performed
Then The current quantity is formatted for display as the 'before' value in the impact message
R-GCX016E-cbl-01141 Format After Quantity Display
Process Rules
📊 Business Logic Narrative
When the process 'Format After Quantity Display' is invoked, and assuming that calculated new release quantity value, when impact report formatting is performed, the desired outcome is that the new quantity is formatted for display as the 'after' value in the impact message.
💻 Technical Criteria
Given Calculated new release quantity value
When Impact report formatting is performed
Then The new quantity is formatted for display as the 'after' value in the impact message
R-GCX016E-cbl-01286 Initialize MQ Connection Parameters
Process Rules
📊 Business Logic Narrative
When the process 'Initialize MQ Connection Parameters' is invoked, and assuming that the system needs to connect to message queue services, when mq connection management process starts, the desired outcome is that all mq connection parameters are initialized to default values.
💻 Technical Criteria
Given The system needs to connect to message queue services
When MQ connection management process starts
Then All MQ connection parameters are initialized to default values
R-GCX016E-cbl-01367 Use Default System Date
Decision Rules
📊 Business Logic Narrative
When the process 'Use Default System Date' is invoked, and assuming that an invalid date has been detected during validation, when the system cannot process the provided date, the desired outcome is that the system uses the current system date as the default value for age calculation.
💻 Technical Criteria
Given An invalid date has been detected during validation
When The system cannot process the provided date
Then The system uses the current system date as the default value for age calculation
R-GCX016E-cbl-01370 Return Julian Date Value
Process Rules
📊 Business Logic Narrative
When the process 'Return Julian Date Value' is invoked, and assuming that julian date conversion and age calculation have been completed successfully, when the calling process requires the julian date result, the desired outcome is that the system returns the calculated julian date value for further processing.
💻 Technical Criteria
Given Julian date conversion and age calculation have been completed successfully
When The calling process requires the Julian date result
Then The system returns the calculated Julian date value for further processing
R-GCX016E-cbl-01372 Destination Index Management
Process Rules
📊 Business Logic Narrative
When the process 'Destination Index Management' is invoked, and assuming that julian date calculation has been completed, when the system needs to update destination information, the desired outcome is that the system uses the julian date result to manage destination index values.
💻 Technical Criteria
Given Julian date calculation has been completed
When The system needs to update destination information
Then The system uses the Julian date result to manage destination index values
R-GCX016E-cbl-01373 Bond Start Date Processing
Process Rules
📊 Business Logic Narrative
When the process 'Bond Start Date Processing' is invoked, and assuming that destination index management has been completed, when the system needs to process bond information, the desired outcome is that the system uses julian date calculations to determine bond start date processing requirements.
💻 Technical Criteria
Given Destination index management has been completed
When The system needs to process bond information
Then The system uses Julian date calculations to determine bond start date processing requirements
R-GCX016E-cbl-01382 Retrieve In-Bond Type Codes
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve In-Bond Type Codes' is invoked, and assuming that a valid shiproot record exists for the shipment, when the system processes shipment minimum information, the desired outcome is that the system should retrieve the applicable in-bond type codes from the shipment data.
💻 Technical Criteria
Given A valid shiproot record exists for the shipment
When The system processes shipment minimum information
Then The system should retrieve the applicable in-bond type codes from the shipment data
R-GCX016E-cbl-01383 Retrieve Entry Numbers
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Entry Numbers' is invoked, and assuming that a valid shiproot record exists and in-bond type codes are retrieved, when the system processes shipment minimum information, the desired outcome is that the system should retrieve all applicable entry numbers for the shipment.
💻 Technical Criteria
Given A valid shiproot record exists and in-bond type codes are retrieved
When The system processes shipment minimum information
Then The system should retrieve all applicable entry numbers for the shipment
R-GCX016E-cbl-01388 Populate In-Bond Type Codes in U1
Process Rules
📊 Business Logic Narrative
When the process 'Populate In-Bond Type Codes in U1' is invoked, and assuming that a u1 segment has been created and in-bond type codes are available, when the system populates the u1 segment with in-bond information, the desired outcome is that the system should insert all applicable in-bond type codes into the u1 segment.
💻 Technical Criteria
Given A U1 segment has been created and in-bond type codes are available
When The system populates the U1 segment with in-bond information
Then The system should insert all applicable in-bond type codes into the U1 segment
R-GCX016E-cbl-01389 Populate Entry Numbers in U1
Process Rules
📊 Business Logic Narrative
When the process 'Populate Entry Numbers in U1' is invoked, and assuming that in-bond type codes have been populated in the u1 segment and entry numbers are available, when the system populates entry number information, the desired outcome is that the system should insert all retrieved entry numbers into the appropriate fields of the u1 segment.
💻 Technical Criteria
Given In-bond type codes have been populated in the U1 segment and entry numbers are available
When The system populates entry number information
Then The system should insert all retrieved entry numbers into the appropriate fields of the U1 segment
R-GCX016E-cbl-01430 Format Reference Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Reference Information' is invoked, and assuming that reference numbers have been processed (either fda or general), when the system formats the reference information, the desired outcome is that reference information is formatted into standardized structure with proper qualifiers and values.
💻 Technical Criteria
Given Reference numbers have been processed (either FDA or general)
When The system formats the reference information
Then Reference information is formatted into standardized structure with proper qualifiers and values
R-GCX016E-cbl-01461 Table Lookup Error
Validation Rules
📊 Business Logic Narrative
When the process 'Table Lookup Error' is invoked, and assuming that a lookup is performed against reference tables (dc table, train list, broker table, etc.), when the lookup operation fails to find matching records or returns an error, the desired outcome is that generate appropriate error message, log the lookup failure, and continue processing with default values or error handling.
💻 Technical Criteria
Given A lookup is performed against reference tables (DC table, train list, broker table, etc.)
When The lookup operation fails to find matching records or returns an error
Then Generate appropriate error message, log the lookup failure, and continue processing with default values or error handling
R-GCX016E-cbl-01622 Extract Date from V9 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Date from V9 Segment' is invoked, and assuming that a v9 segment contains pod or aad event code, when the system processes the v9 segment for date information, the desired outcome is that the system extracts the date value from the v9 segment for validation.
💻 Technical Criteria
Given A V9 segment contains POD or AAD event code
When The system processes the V9 segment for date information
Then The system extracts the date value from the V9 segment for validation
R-GCX016E-cbl-01623 Date Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Date Valid?' is invoked, and assuming that a date has been extracted from the v9 segment, when the system validates the date format and value, the desired outcome is that the system determines if the date is valid for business processing or requires default system date.
💻 Technical Criteria
Given A date has been extracted from the V9 segment
When The system validates the date format and value
Then The system determines if the date is valid for business processing or requires default system date
R-GCX016E-cbl-01652 Special Bond Creation Message?
Decision Rules
📊 Business Logic Narrative
When the process 'Special Bond Creation Message?' is invoked, and assuming that k1 text is linked to train disposition code, when the system checks for canadian pacific railway identifiers including 'director of customs, cp rail', 'canadian pacific limited', or 'canadian pacific railway co', the desired outcome is that the system should identify if this is a special cpr bond creation message.
💻 Technical Criteria
Given K1 text is linked to train disposition code
When The system checks for Canadian Pacific Railway identifiers including 'DIRECTOR OF CUSTOMS, CP RAIL', 'CANADIAN PACIFIC LIMITED', or 'CANADIAN PACIFIC RAILWAY CO'
Then The system should identify if this is a special CPR bond creation message
R-GCX016E-cbl-01653 Process Canadian Pacific Railway Bond Creation
Action Rules
📊 Business Logic Narrative
When the process 'Process Canadian Pacific Railway Bond Creation' is invoked, and assuming that a canadian pacific railway bond creation message is detected, when the system processes the cpr-specific bond creation, the desired outcome is that the system should execute canadian pacific railway bond creation processing.
💻 Technical Criteria
Given A Canadian Pacific Railway bond creation message is detected
When The system processes the CPR-specific bond creation
Then The system should execute Canadian Pacific Railway bond creation processing
R-GCX016E-cbl-01654 Store K1 Text in Train Processing Context
Process Rules
📊 Business Logic Narrative
When the process 'Store K1 Text in Train Processing Context' is invoked, and assuming that k1 text processing is complete (either regular or cpr bond processing), when the system stores the k1 text information, the desired outcome is that the k1 text should be stored in the train processing context.
💻 Technical Criteria
Given K1 text processing is complete (either regular or CPR bond processing)
When The system stores the K1 text information
Then The K1 text should be stored in the train processing context
R-GCX016E-cbl-01673 Use Extracted Date
Decision Rules
📊 Business Logic Narrative
When the process 'Use Extracted Date' is invoked, and assuming that a disposition code date has been extracted from x4 segment and validated as correct, when the date validation passes, the desired outcome is that use the extracted date value for disposition code date/time processing.
💻 Technical Criteria
Given A disposition code date has been extracted from X4 segment and validated as correct
When The date validation passes
Then Use the extracted date value for disposition code date/time processing
R-GCX016E-cbl-01674 Default to System Date
Decision Rules
📊 Business Logic Narrative
When the process 'Default to System Date' is invoked, and assuming that a disposition code date has been extracted from x4 segment and is invalid or missing, when the date validation fails, the desired outcome is that use the current system date as the default value for disposition code processing.
💻 Technical Criteria
Given A disposition code date has been extracted from X4 segment and is invalid or missing
When The date validation fails
Then Use the current system date as the default value for disposition code processing
R-GCX016E-cbl-01675 Use Extracted Time
Decision Rules
📊 Business Logic Narrative
When the process 'Use Extracted Time' is invoked, and assuming that a disposition code time has been extracted from x4 segment and validated as correct, when the time validation passes, the desired outcome is that use the extracted time value for disposition code date/time processing.
💻 Technical Criteria
Given A disposition code time has been extracted from X4 segment and validated as correct
When The time validation passes
Then Use the extracted time value for disposition code date/time processing
R-GCX016E-cbl-01676 Default to System Time
Decision Rules
📊 Business Logic Narrative
When the process 'Default to System Time' is invoked, and assuming that a disposition code time has been extracted from x4 segment and is invalid or missing, when the time validation fails, the desired outcome is that use the current system time as the default value for disposition code processing.
💻 Technical Criteria
Given A disposition code time has been extracted from X4 segment and is invalid or missing
When The time validation fails
Then Use the current system time as the default value for disposition code processing
R-GCX016E-cbl-01679 Combine Date and Time
Computation Rules
📊 Business Logic Narrative
When the process 'Combine Date and Time' is invoked, and assuming that formatted date and time components for disposition code processing, when both date and time have been validated and formatted, the desired outcome is that combine the date and time into a single datetime value for storage and processing.
💻 Technical Criteria
Given Formatted date and time components for disposition code processing
When Both date and time have been validated and formatted
Then Combine the date and time into a single datetime value for storage and processing
R-GCX016E-cbl-01680 Store Formatted DateTime
Process Rules
📊 Business Logic Narrative
When the process 'Store Formatted DateTime' is invoked, and assuming that a combined datetime value from validated date and time components, when the datetime combination is complete, the desired outcome is that store the formatted datetime value in the appropriate field for disposition code processing.
💻 Technical Criteria
Given A combined datetime value from validated date and time components
When The datetime combination is complete
Then Store the formatted datetime value in the appropriate field for disposition code processing
R-GCX016E-cbl-01702 Validate DC95 in Disposition Code Table
Validation Rules
📊 Business Logic Narrative
When the process 'Validate DC95 in Disposition Code Table' is invoked, and assuming that a disposition code 95 is received for processing, when the system looks up disposition code 95 in the disposition code table, the desired outcome is that if dc95 is not found in the table, generate an error message and stop processing, otherwise continue with bond clearing process.
💻 Technical Criteria
Given A disposition code 95 is received for processing
When The system looks up disposition code 95 in the disposition code table
Then If DC95 is not found in the table, generate an error message and stop processing, otherwise continue with bond clearing process
R-GCX016E-cbl-01704 Clear M12 Bond Data
Action Rules
📊 Business Logic Narrative
When the process 'Clear M12 Bond Data' is invoked, and assuming that bol type code has been cleared and bond cancellation is in progress, when the system processes m12 bond data clearing, the desired outcome is that all m12 segment bond-related fields are cleared to their default values.
💻 Technical Criteria
Given BOL type code has been cleared and bond cancellation is in progress
When The system processes M12 bond data clearing
Then All M12 segment bond-related fields are cleared to their default values
R-GCX016E-cbl-01705 Clear Bond Number Index
Action Rules
📊 Business Logic Narrative
When the process 'Clear Bond Number Index' is invoked, and assuming that m12 bond data has been cleared and bond cancellation continues, when the system processes bond number index clearing, the desired outcome is that the bond number index field is set to zero to remove the bond reference.
💻 Technical Criteria
Given M12 bond data has been cleared and bond cancellation continues
When The system processes bond number index clearing
Then The bond number index field is set to zero to remove the bond reference
R-GCX016E-cbl-01706 Clear Broker QP Information
Action Rules
📊 Business Logic Narrative
When the process 'Clear Broker QP Information' is invoked, and assuming that bond number index has been cleared and bond cancellation processing continues, when the system processes broker qp information clearing, the desired outcome is that all broker qualification and permit fields are cleared to spaces or zero values.
💻 Technical Criteria
Given Bond number index has been cleared and bond cancellation processing continues
When The system processes broker QP information clearing
Then All broker qualification and permit fields are cleared to spaces or zero values
R-GCX016E-cbl-01707 Clear Bond Owner Information
Action Rules
📊 Business Logic Narrative
When the process 'Clear Bond Owner Information' is invoked, and assuming that broker qp information has been cleared and bond cancellation is proceeding, when the system processes bond owner information clearing, the desired outcome is that bond owner identification fields are cleared to remove ownership references.
💻 Technical Criteria
Given Broker QP information has been cleared and bond cancellation is proceeding
When The system processes bond owner information clearing
Then Bond owner identification fields are cleared to remove ownership references
R-GCX016E-cbl-01711 DC95 Not Found - Generate Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'DC95 Not Found - Generate Error', assuming that disposition code 95 is being validated against the disposition code table, when dc95 is not found in the disposition code table, the desired outcome is that generate an error message indicating invalid disposition code and terminate the bond cancellation process.
💻 Technical Criteria
EXCLUDING Disposition code 95 is being validated against the disposition code table
When DC95 is not found in the disposition code table
Then Generate an error message indicating invalid disposition code and terminate the bond cancellation process
R-GCX016E-cbl-01714 Convert EDI Entry Type Code to Internal System Value
Computation Rules
📊 Business Logic Narrative
When the process 'Convert EDI Entry Type Code to Internal System Value' is invoked, and assuming that an edi entry type code is received from the x4 segment, when the system processes the entry type code for internal use, the desired outcome is that convert the edi entry type code to the corresponding internal system value using entry type code lookup arrays.
💻 Technical Criteria
Given An EDI entry type code is received from the X4 segment
When The system processes the entry type code for internal use
Then Convert the EDI entry type code to the corresponding internal system value using entry type code lookup arrays
R-GCX016E-cbl-01715 Entry Type Code = 61, 62, 63, or 69?
Decision Rules
📊 Business Logic Narrative
When the process 'Entry Type Code = 61, 62, 63, or 69?' is invoked, and assuming that an entry type code has been converted to internal system value, when the system evaluates the entry type code for in-bond classification, the desired outcome is that if entry type code equals 61, 62, 63, or 69, classify as in-bond and set master in-bond flag, otherwise proceed with standard entry type processing.
💻 Technical Criteria
Given An entry type code has been converted to internal system value
When The system evaluates the entry type code for in-bond classification
Then If entry type code equals 61, 62, 63, or 69, classify as in-bond and set master in-bond flag, otherwise proceed with standard entry type processing
R-GCX016E-cbl-01764 More Records with Same Bond?
Decision Rules
📊 Business Logic Narrative
When the process 'More Records with Same Bond?' is invoked, and assuming that a search for subsequent records has been performed, when the system evaluates if more records exist with the same bond number, the desired outcome is that if additional records exist, continue processing the next record, otherwise complete the bond lookup process.
💻 Technical Criteria
Given A search for subsequent records has been performed
When The system evaluates if more records exist with the same bond number
Then If additional records exist, continue processing the next record, otherwise complete the bond lookup process
R-GCX016E-cbl-01772 Log Bond Lookup Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Bond Lookup Error', assuming that an error occurs during the bond lookup process, when the system encounters a database access error or invalid search condition, the desired outcome is that the error details must be logged and the system must prepare to return a 'no records found' status.
💻 Technical Criteria
EXCLUDING An error occurs during the bond lookup process
When The system encounters a database access error or invalid search condition
Then The error details must be logged and the system must prepare to return a 'No Records Found' status
R-GCX016E-cbl-01827 Validate DC95 Authorization
Authorization Rules
📊 Business Logic Narrative
When the process 'Validate DC95 Authorization' is invoked, and assuming that disposition code 95 has been identified for processing, when the system validates the authorization for dc95, the desired outcome is that the system should verify the disposition code is valid and authorized before proceeding with bond clearing.
💻 Technical Criteria
Given Disposition code 95 has been identified for processing
When The system validates the authorization for DC95
Then The system should verify the disposition code is valid and authorized before proceeding with bond clearing
R-GCX016E-cbl-01828 Clear BOL Type Code
Action Rules
📊 Business Logic Narrative
When the process 'Clear BOL Type Code' is invoked, and assuming that dc95 authorization has been validated, when the system processes bond information clearing, the desired outcome is that the bol type code field should be cleared or set to blank.
💻 Technical Criteria
Given DC95 authorization has been validated
When The system processes bond information clearing
Then The BOL type code field should be cleared or set to blank
R-GCX016E-cbl-01829 Clear M12 Data
Action Rules
📊 Business Logic Narrative
When the process 'Clear M12 Data' is invoked, and assuming that bol type code has been cleared, when the system continues bond information clearing, the desired outcome is that all m12 data fields should be cleared or reset to initial values.
💻 Technical Criteria
Given BOL type code has been cleared
When The system continues bond information clearing
Then All M12 data fields should be cleared or reset to initial values
R-GCX016E-cbl-01830 Clear Bond Number Index
Action Rules
📊 Business Logic Narrative
When the process 'Clear Bond Number Index' is invoked, and assuming that m12 data has been cleared, when the system processes bond number clearing, the desired outcome is that the bond number index field should be cleared or set to zero.
💻 Technical Criteria
Given M12 data has been cleared
When The system processes bond number clearing
Then The bond number index field should be cleared or set to zero
R-GCX016E-cbl-01831 Clear Broker QP Information
Action Rules
📊 Business Logic Narrative
When the process 'Clear Broker QP Information' is invoked, and assuming that bond number index has been cleared, when the system processes broker information clearing, the desired outcome is that all broker qp (qualified person) information fields should be cleared.
💻 Technical Criteria
Given Bond number index has been cleared
When The system processes broker information clearing
Then All broker QP (Qualified Person) information fields should be cleared
R-GCX016E-cbl-01832 Clear Bond Owner Information
Action Rules
📊 Business Logic Narrative
When the process 'Clear Bond Owner Information' is invoked, and assuming that broker qp information has been cleared, when the system processes bond owner clearing, the desired outcome is that all bond owner information fields should be cleared or reset.
💻 Technical Criteria
Given Broker QP information has been cleared
When The system processes bond owner clearing
Then All bond owner information fields should be cleared or reset
R-GCX016E-cbl-01833 Log Bond Clearing Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Bond Clearing Action' is invoked, and assuming that all bond information has been cleared, when the system completes bond clearing process, the desired outcome is that a log entry should be created documenting the bond clearing action with relevant details.
💻 Technical Criteria
Given All bond information has been cleared
When The system completes bond clearing process
Then A log entry should be created documenting the bond clearing action with relevant details
R-GCX016E-cbl-01839 Search In-Bond Control Numbers
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Search In-Bond Control Numbers', assuming that an entry number that was not found in broker entry numbers, when the system searches in-bond control numbers in the database, the desired outcome is that if in-bond control number is found, mark entry number as valid, otherwise continue to next validation step.
💻 Technical Criteria
EXCLUDING An entry number that was not found in broker entry numbers
When The system searches in-bond control numbers in the database
Then If in-bond control number is found, mark entry number as valid, otherwise continue to next validation step
R-GCX016E-cbl-01840 Check for Special V37 Entries
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Check for Special V37 Entries', assuming that an entry number that was not found in broker entry numbers or in-bond control numbers, when the system searches special v37 entries in the database, the desired outcome is that if v37 entry is found, mark entry number as valid, otherwise generate entry number error.
💻 Technical Criteria
EXCLUDING An entry number that was not found in broker entry numbers or in-bond control numbers
When The system searches special V37 entries in the database
Then If V37 entry is found, mark entry number as valid, otherwise generate entry number error
R-GCX016E-cbl-01841 Mark Entry Number as Valid
Process Rules
📊 Business Logic Narrative
When the process 'Mark Entry Number as Valid' is invoked, and assuming that an entry number that has been found in broker entry numbers, in-bond control numbers, or special v37 entries, when the system marks the entry number as valid, the desired outcome is that set in-bond processing flag, log entry number validation success, and continue with in-bond processing.
💻 Technical Criteria
Given An entry number that has been found in broker entry numbers, in-bond control numbers, or special V37 entries
When The system marks the entry number as valid
Then Set in-bond processing flag, log entry number validation success, and continue with in-bond processing
R-GCX016E-cbl-01842 Generate Entry Number Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Entry Number Error', assuming that an entry number that has invalid format or was not found in any validation databases, when the system generates entry number error, the desired outcome is that log entry number validation failure and skip in-bond processing.
💻 Technical Criteria
EXCLUDING An entry number that has invalid format or was not found in any validation databases
When The system generates entry number error
Then Log entry number validation failure and skip in-bond processing
R-GCX016E-cbl-01844 Broker Entry Number Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Broker Entry Number Found?' is invoked, and assuming that a broker entry number search result, when the system evaluates if broker entry number was found, the desired outcome is that if broker entry number is found, mark entry number as valid, otherwise search in-bond control numbers.
💻 Technical Criteria
Given A broker entry number search result
When The system evaluates if broker entry number was found
Then If broker entry number is found, mark entry number as valid, otherwise search in-bond control numbers
R-GCX016E-cbl-01845 In-Bond Control Number Found?
Decision Rules
📊 Business Logic Narrative
When the process 'In-Bond Control Number Found?' is invoked, and assuming that an in-bond control number search result, when the system evaluates if in-bond control number was found, the desired outcome is that if in-bond control number is found, mark entry number as valid, otherwise check for special v37 entries.
💻 Technical Criteria
Given An in-bond control number search result
When The system evaluates if in-bond control number was found
Then If in-bond control number is found, mark entry number as valid, otherwise check for special V37 entries
R-GCX016E-cbl-01848 Lookup Entry Type in Conversion Array
Action Rules
📊 Business Logic Narrative
When the process 'Lookup Entry Type in Conversion Array' is invoked, and assuming that an edi entry type code is present in the x4 segment, when the system searches the entry type conversion arrays for a matching edi code, the desired outcome is that return the corresponding internal system entry type value if found in the conversion arrays.
💻 Technical Criteria
Given An EDI entry type code is present in the X4 segment
When The system searches the entry type conversion arrays for a matching EDI code
Then Return the corresponding internal system entry type value if found in the conversion arrays
R-GCX016E-cbl-01849 Valid Entry Type Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid Entry Type Found?' is invoked, and assuming that entry type code lookup has been performed in conversion arrays, when the system evaluates the lookup result, the desired outcome is that if valid entry type found, proceed with conversion; if invalid, generate error; if not found, use default value.
💻 Technical Criteria
Given Entry type code lookup has been performed in conversion arrays
When The system evaluates the lookup result
Then If valid entry type found, proceed with conversion; if invalid, generate error; if not found, use default value
R-GCX016E-cbl-01850 Convert EDI Code to Internal System Value
Computation Rules
📊 Business Logic Narrative
When the process 'Convert EDI Code to Internal System Value' is invoked, and assuming that a valid entry type code has been found in the conversion arrays, when the system performs the conversion from edi format to internal format, the desired outcome is that the edi entry type code is converted to the corresponding internal system entry type value.
💻 Technical Criteria
Given A valid entry type code has been found in the conversion arrays
When The system performs the conversion from EDI format to internal format
Then The EDI entry type code is converted to the corresponding internal system entry type value
R-GCX016E-cbl-01851 Entry Type = 61, 62, 63, or 69?
Decision Rules
📊 Business Logic Narrative
When the process 'Entry Type = 61, 62, 63, or 69?' is invoked, and assuming that an entry type code has been successfully converted to internal system value, when the system checks if the entry type is 61, 62, 63, or 69, the desired outcome is that if entry type matches any of these values, set master in-bond flag; otherwise continue to border crossing check.
💻 Technical Criteria
Given An entry type code has been successfully converted to internal system value
When The system checks if the entry type is 61, 62, 63, or 69
Then If entry type matches any of these values, set master in-bond flag; otherwise continue to border crossing check
R-GCX016E-cbl-01852 Set Master In-Bond Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Master In-Bond Flag' is invoked, and assuming that the entry type is identified as 61, 62, 63, or 69, when the system processes the in-bond entry type, the desired outcome is that set the master in-bond flag to indicate special in-bond processing is required.
💻 Technical Criteria
Given The entry type is identified as 61, 62, 63, or 69
When The system processes the in-bond entry type
Then Set the master in-bond flag to indicate special in-bond processing is required
R-GCX016E-cbl-01864 Entry Type Code Present?
Validation Rules
📊 Business Logic Narrative
When the process 'Entry Type Code Present?' is invoked, and assuming that an x4 segment is being processed for master in-bond flag setting, when the system checks for the presence of an entry type code, the desired outcome is that if entry type code is present, retrieve and evaluate the code value, otherwise continue with standard entry processing.
💻 Technical Criteria
Given An X4 segment is being processed for master in-bond flag setting
When The system checks for the presence of an entry type code
Then If entry type code is present, retrieve and evaluate the code value, otherwise continue with standard entry processing
R-GCX016E-cbl-01865 Continue with Standard Entry Processing
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Continue with Standard Entry Processing', assuming that an x4 segment is being processed, when the entry type code is not present or the entry type code value is not 61, 62, 63, or 69, the desired outcome is that continue with standard entry processing without setting master in-bond flags.
💻 Technical Criteria
EXCLUDING An X4 segment is being processed
When The entry type code is not present or the entry type code value is not 61, 62, 63, or 69
Then Continue with standard entry processing without setting master in-bond flags
R-GCX016E-cbl-01906 More Records with Same Bond?
Decision Rules
📊 Business Logic Narrative
When the process 'More Records with Same Bond?' is invoked, and assuming that the system has checked for additional bond records, when multiple records exist for the same bond number, the desired outcome is that continue to retrieve and process the next record, otherwise complete the bond index retrieval process.
💻 Technical Criteria
Given The system has checked for additional bond records
When Multiple records exist for the same bond number
Then Continue to retrieve and process the next record, otherwise complete the bond index retrieval process
R-GCX016E-cbl-01999 Clear Database Segment Work Area
Process Rules
📊 Business Logic Narrative
When the process 'Clear Database Segment Work Area' is invoked, and assuming that a database segment work area exists, when the system prepares to process status array entries, the desired outcome is that all fields in the database segment work area are cleared to initial values.
💻 Technical Criteria
Given A database segment work area exists
When The system prepares to process status array entries
Then All fields in the database segment work area are cleared to initial values
R-GCX016E-cbl-02034 Handle Hold Code Duplicate
Process Rules
📊 Business Logic Narrative
When the process 'Handle Hold Code Duplicate' is invoked, and assuming that a duplicate disposition code is identified as a hold code type, when the system processes the duplicate hold code, the desired outcome is that the system updates the existing entry's date and time information with the most recent values.
💻 Technical Criteria
Given A duplicate disposition code is identified as a Hold Code type
When The system processes the duplicate hold code
Then The system updates the existing entry's date and time information with the most recent values
R-GCX016E-cbl-02035 Handle Release Code Duplicate
Process Rules
📊 Business Logic Narrative
When the process 'Handle Release Code Duplicate' is invoked, and assuming that a duplicate disposition code is identified as a release code type, when the system processes the duplicate release code, the desired outcome is that the system updates the existing entry's date and time information with the most recent values.
💻 Technical Criteria
Given A duplicate disposition code is identified as a Release Code type
When The system processes the duplicate release code
Then The system updates the existing entry's date and time information with the most recent values
R-GCX016E-cbl-02195 Check In-Bond Entry Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check In-Bond Entry Status' is invoked, and assuming that proceed disposition codes are present in the status array, when the system validates in-bond requirements, the desired outcome is that in-bond entry status is verified as valid for proceed processing.
💻 Technical Criteria
Given Proceed disposition codes are present in the status array
When The system validates in-bond requirements
Then In-bond entry status is verified as valid for proceed processing
R-GCX016E-cbl-02201 Apply Business Rule Priority
Policy Rules
📊 Business Logic Narrative
When the process 'Apply Business Rule Priority' is invoked, and assuming that multiple conflicting disposition codes exist in the status array, when the system applies business rule priority, the desired outcome is that disposition codes are prioritized with hold taking priority over release, manual release overriding system hold, proceed requiring valid in-bond, and export requiring port validation.
💻 Technical Criteria
Given Multiple conflicting disposition codes exist in the status array
When The system applies business rule priority
Then Disposition codes are prioritized with hold taking priority over release, manual release overriding system hold, proceed requiring valid in-bond, and export requiring port validation
R-GCX016E-cbl-02219 Validate Entry Number Against Existing Records
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Entry Number Against Existing Records' is invoked, and assuming that bond processing is complete or no bond information is available, when the system validates the entry number, the desired outcome is that the entry number is checked against existing broker entry number records to ensure validity.
💻 Technical Criteria
Given Bond processing is complete or no bond information is available
When The system validates the entry number
Then The entry number is checked against existing broker entry number records to ensure validity
R-GCX016E-cbl-02221 Convert EDI Entry Type Codes to Internal Values
Computation Rules
📊 Business Logic Narrative
When the process 'Convert EDI Entry Type Codes to Internal Values' is invoked, and assuming that in-bond control number has been processed, when edi entry type codes need to be converted, the desired outcome is that edi entry type codes are converted to corresponding internal system values for processing.
💻 Technical Criteria
Given In-bond control number has been processed
When EDI entry type codes need to be converted
Then EDI entry type codes are converted to corresponding internal system values for processing
R-GCX016E-cbl-02241 Recalculate Bond Information
Computation Rules
📊 Business Logic Narrative
When the process 'Recalculate Bond Information' is invoked, and assuming that arrival status has been cancelled, when the system updates bond-related data, the desired outcome is that bond information is recalculated to reflect the cancelled arrival status.
💻 Technical Criteria
Given Arrival status has been cancelled
When The system updates bond-related data
Then Bond information is recalculated to reflect the cancelled arrival status
R-GCX016E-cbl-02287 Compare Previous vs Current Release Status
Decision Rules
📊 Business Logic Narrative
When the process 'Compare Previous vs Current Release Status' is invoked, and assuming that a release status change has been detected, when the system compares the specific release status values, the desired outcome is that the system identifies the exact nature of the release status change.
💻 Technical Criteria
Given A release status change has been detected
When The system compares the specific release status values
Then The system identifies the exact nature of the release status change
R-GCX016E-cbl-02318 Proceed Status Active?
Decision Rules
📊 Business Logic Narrative
When the process 'Proceed Status Active?' is invoked, and assuming that no hold status is active, when proceed status flag is active, the desired outcome is that check for in-bond entry conditions.
💻 Technical Criteria
Given No hold status is active
When Proceed status flag is active
Then Check for in-bond entry conditions
R-GCX016E-cbl-02319 In-Bond Entry Present?
Decision Rules
📊 Business Logic Narrative
When the process 'In-Bond Entry Present?' is invoked, and assuming that proceed status is active, when in-bond entry information is present and valid, the desired outcome is that set final status to proceed.
💻 Technical Criteria
Given Proceed status is active
When In-bond entry information is present and valid
Then Set final status to PROCEED
R-GCX016E-cbl-02359 Clear Current Destination Index
Process Rules
📊 Business Logic Narrative
When the process 'Clear Current Destination Index' is invoked, and assuming that previous bond data has been retrieved, when the system begins bond restoration, the desired outcome is that the system clears the current destination index field.
💻 Technical Criteria
Given Previous bond data has been retrieved
When The system begins bond restoration
Then The system clears the current destination index field
R-GCX016E-cbl-02360 Restore Bond Start Date
Process Rules
📊 Business Logic Narrative
When the process 'Restore Bond Start Date' is invoked, and assuming that the destination index has been cleared, when the system processes bond restoration, the desired outcome is that the system restores the bond start date from previous bond data.
💻 Technical Criteria
Given The destination index has been cleared
When The system processes bond restoration
Then The system restores the bond start date from previous bond data
R-GCX016E-cbl-02361 Set Bond Number Index
Process Rules
📊 Business Logic Narrative
When the process 'Set Bond Number Index' is invoked, and assuming that the bond start date has been restored, when the system continues bond restoration, the desired outcome is that the system sets the bond number index from the restored bond data.
💻 Technical Criteria
Given The bond start date has been restored
When The system continues bond restoration
Then The system sets the bond number index from the restored bond data
R-GCX016E-cbl-02362 Restore Broker QP Information
Process Rules
📊 Business Logic Narrative
When the process 'Restore Broker QP Information' is invoked, and assuming that the bond number index has been set, when the system processes broker information restoration, the desired outcome is that the system restores the broker qp information from bond data.
💻 Technical Criteria
Given The bond number index has been set
When The system processes broker information restoration
Then The system restores the broker QP information from bond data
R-GCX016E-cbl-02368 Log Bond Restoration Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Bond Restoration Action' is invoked, and assuming that the bond restoration flag has been set, when the system performs audit logging, the desired outcome is that the system logs the bond restoration action with relevant details.
💻 Technical Criteria
Given The bond restoration flag has been set
When The system performs audit logging
Then The system logs the bond restoration action with relevant details
R-GCX016E-cbl-03333 Set Default Values
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Default Values', assuming that some m10 segment data is invalid but not critical for processing, when the system sets default values, the desired outcome is that appropriate default values are assigned to non-critical fields to allow continued processing.
💻 Technical Criteria
EXCLUDING Some M10 segment data is invalid but not critical for processing
When The system sets default values
Then Appropriate default values are assigned to non-critical fields to allow continued processing
R-GCX016E-cbl-02440 Set Default SCAC Values
Decision Rules
📊 Business Logic Narrative
When the process 'Set Default SCAC Values' is invoked, and assuming that a scac code has been validated and found to be invalid or missing, when the scac validation fails during foreign manifest building, the desired outcome is that default scac values are applied to ensure manifest can be constructed.
💻 Technical Criteria
Given A SCAC code has been validated and found to be invalid or missing
When The SCAC validation fails during foreign manifest building
Then Default SCAC values are applied to ensure manifest can be constructed
R-GCX016E-cbl-02470 Show Before Quantity
Process Rules
📊 Business Logic Narrative
When the process 'Show Before Quantity' is invoked, and assuming that quantity impact message is being formatted, when before quantity information is available, the desired outcome is that the system includes the original quantity value in the impact message.
💻 Technical Criteria
Given Quantity impact message is being formatted
When Before quantity information is available
Then The system includes the original quantity value in the impact message
R-GCX016E-cbl-02471 Show After Quantity
Process Rules
📊 Business Logic Narrative
When the process 'Show After Quantity' is invoked, and assuming that before quantity has been shown in the impact message, when after quantity information is available, the desired outcome is that the system includes the resulting quantity value in the impact message.
💻 Technical Criteria
Given Before quantity has been shown in the impact message
When After quantity information is available
Then The system includes the resulting quantity value in the impact message
R-GCX016E-cbl-02481 Canadian Pacific Railway Bond?
Decision Rules
📊 Business Logic Narrative
When the process 'Canadian Pacific Railway Bond?' is invoked, and assuming that special comments have been processed, when the system evaluates bond creation requirements, the desired outcome is that the system determines if canadian pacific railway bond processing is involved.
💻 Technical Criteria
Given Special comments have been processed
When The system evaluates bond creation requirements
Then The system determines if Canadian Pacific Railway bond processing is involved
R-GCX016E-cbl-02482 Add CPR Bond Creation Notice
Process Rules
📊 Business Logic Narrative
When the process 'Add CPR Bond Creation Notice' is invoked, and assuming that canadian pacific railway bond processing is identified, when bond creation notice is required, the desired outcome is that the system adds cpr bond creation notification text to the message.
💻 Technical Criteria
Given Canadian Pacific Railway bond processing is identified
When Bond creation notice is required
Then The system adds CPR bond creation notification text to the message
R-GCX016E-cbl-02483 Format Date/Time Information
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Format Date/Time Information', assuming that cpr bond notice has been added or is not applicable, when date and time information needs to be formatted, the desired outcome is that the system formats relevant dates and times for inclusion in the message.
💻 Technical Criteria
EXCLUDING CPR bond notice has been added or is not applicable
When Date and time information needs to be formatted
Then The system formats relevant dates and times for inclusion in the message
R-GCX016E-cbl-02489 Identify Canadian Pacific Railway Bond Creation
Decision Rules
📊 Business Logic Narrative
When the process 'Identify Canadian Pacific Railway Bond Creation' is invoked, and assuming that a k1 free-form text segment is received, when the k1 segment contains 'director of customs, cp rail' or 'canadian pacific limited' or 'canadian pacific railway co', the desired outcome is that the message is identified as a canadian pacific railway bond creation request.
💻 Technical Criteria
Given A K1 free-form text segment is received
When The K1 segment contains 'DIRECTOR OF CUSTOMS, CP RAIL' OR 'CANADIAN PACIFIC LIMITED' OR 'CANADIAN PACIFIC RAILWAY CO'
Then The message is identified as a Canadian Pacific Railway bond creation request
R-GCX016E-cbl-02490 Extract Bond Information from K1 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Bond Information from K1 Segment' is invoked, and assuming that a k1 segment is identified as canadian pacific railway bond creation, when the system processes the k1 segment content, the desired outcome is that bond information including bond number, broker details, and creation request data is extracted from the free-form text.
💻 Technical Criteria
Given A K1 segment is identified as Canadian Pacific Railway bond creation
When The system processes the K1 segment content
Then Bond information including bond number, broker details, and creation request data is extracted from the free-form text
R-GCX016E-cbl-02491 Validate Bond Creation Request
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Bond Creation Request' is invoked, and assuming that bond information has been extracted from k1 segment, when the system validates the bond creation request, the desired outcome is that the bond information is verified for completeness and business rule compliance.
💻 Technical Criteria
Given Bond information has been extracted from K1 segment
When The system validates the bond creation request
Then The bond information is verified for completeness and business rule compliance
R-GCX016E-cbl-02492 Format Bond Creation Notification
Process Rules
📊 Business Logic Narrative
When the process 'Format Bond Creation Notification' is invoked, and assuming that valid bond information has been extracted and validated, when the system formats the bond creation notification, the desired outcome is that a structured notification message is created containing bond details, broker information, and creation timestamp.
💻 Technical Criteria
Given Valid bond information has been extracted and validated
When The system formats the bond creation notification
Then A structured notification message is created containing bond details, broker information, and creation timestamp
R-GCX016E-cbl-02493 Add Special Comments for CPR Bond
Process Rules
📊 Business Logic Narrative
When the process 'Add Special Comments for CPR Bond' is invoked, and assuming that a bond creation notification is being formatted for canadian pacific railway, when special comments are added to the message, the desired outcome is that cpr-specific identifiers and comments are included in the notification message.
💻 Technical Criteria
Given A bond creation notification is being formatted for Canadian Pacific Railway
When Special comments are added to the message
Then CPR-specific identifiers and comments are included in the notification message
R-GCX016E-cbl-02494 Include Bond Details in Message
Process Rules
📊 Business Logic Narrative
When the process 'Include Bond Details in Message' is invoked, and assuming that a bond creation notification message is being prepared, when bond details are included in the message, the desired outcome is that complete bond information including bond number, broker details, and creation context is added to the merlin message.
💻 Technical Criteria
Given A bond creation notification message is being prepared
When Bond details are included in the message
Then Complete bond information including bond number, broker details, and creation context is added to the Merlin message
R-GCX016E-cbl-02495 Create Comprehensive Merlin Notification
Action Rules
📊 Business Logic Narrative
When the process 'Create Comprehensive Merlin Notification' is invoked, and assuming that bond details and special comments have been prepared, when the comprehensive merlin notification is created, the desired outcome is that a complete notification message is generated with all bond creation information formatted for business user consumption.
💻 Technical Criteria
Given Bond details and special comments have been prepared
When The comprehensive Merlin notification is created
Then A complete notification message is generated with all bond creation information formatted for business user consumption
R-GCX016E-cbl-02497 Log Bond Creation Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Bond Creation Action' is invoked, and assuming that a bond creation notification has been routed to recipients, when the action is logged, the desired outcome is that bond creation notification details are recorded in the system log for audit and tracking purposes.
💻 Technical Criteria
Given A bond creation notification has been routed to recipients
When The action is logged
Then Bond creation notification details are recorded in the system log for audit and tracking purposes
R-GCX016E-cbl-02498 Generate Error Message for Invalid Bond
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error Message for Invalid Bond', assuming that bond information has been extracted from k1 segment, when bond validation fails due to incomplete or invalid information, the desired outcome is that an error message is generated indicating the specific validation failure and the bond creation request is rejected.
💻 Technical Criteria
EXCLUDING Bond information has been extracted from K1 segment
When Bond validation fails due to incomplete or invalid information
Then An error message is generated indicating the specific validation failure and the bond creation request is rejected
R-GCX016E-cbl-02522 Extract Location Identifier from M1203 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Location Identifier from M1203 Segment' is invoked, and assuming that a transit traffic request is received with m1203 segment data, when the system processes the m1203 segment, the desired outcome is that the location identifier is extracted from the m1203 segment for further processing.
💻 Technical Criteria
Given A transit traffic request is received with M1203 segment data
When The system processes the M1203 segment
Then The location identifier is extracted from the M1203 segment for further processing
R-GCX016E-cbl-02523 Validate Location Identifier Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Location Identifier Format' is invoked, and assuming that a location identifier has been extracted from m1203 segment, when the system validates the location identifier format, the desired outcome is that the location identifier is confirmed as valid or invalid based on format requirements.
💻 Technical Criteria
Given A location identifier has been extracted from M1203 segment
When The system validates the location identifier format
Then The location identifier is confirmed as valid or invalid based on format requirements
R-GCX016E-cbl-02575 Before/After Quantities Different?
Decision Rules
📊 Business Logic Narrative
When the process 'Before/After Quantities Different?' is invoked, and assuming that before and after quantity values have been calculated, when determining message content requirements, the desired outcome is that if quantities differ, quantity impact analysis is included; otherwise, it is omitted from the message.
💻 Technical Criteria
Given Before and after quantity values have been calculated
When Determining message content requirements
Then If quantities differ, quantity impact analysis is included; otherwise, it is omitted from the message
R-GCX016E-cbl-02585 Add Bond Creation Notification
Computation Rules
📊 Business Logic Narrative
When the process 'Add Bond Creation Notification' is invoked, and assuming that canadian pacific railway bond processing is identified, when special bond processing requirements are detected, the desired outcome is that bond creation notification is added to the merlin message for cp railway processing.
💻 Technical Criteria
Given Canadian Pacific Railway bond processing is identified
When Special bond processing requirements are detected
Then Bond creation notification is added to the Merlin message for CP Railway processing
R-GCX016E-cbl-02589 Message Type Check
Decision Rules
📊 Business Logic Narrative
When the process 'Message Type Check' is invoked, and assuming that a k1 segment message has been received, when the system checks the message content for cpr identifiers including 'director of customs, cp rail', 'canadian pacific limited', or 'canadian pacific railway co', the desired outcome is that the message is classified as cpr bond creation if any cpr identifier is found, otherwise it is processed as a regular k1 message.
💻 Technical Criteria
Given A K1 segment message has been received
When The system checks the message content for CPR identifiers including 'DIRECTOR OF CUSTOMS, CP RAIL', 'CANADIAN PACIFIC LIMITED', or 'CANADIAN PACIFIC RAILWAY CO'
Then The message is classified as CPR bond creation if any CPR identifier is found, otherwise it is processed as a regular K1 message
R-GCX016E-cbl-02590 Identify CPR Bond Creation
Process Rules
📊 Business Logic Narrative
When the process 'Identify CPR Bond Creation' is invoked, and assuming that a k1 segment message contains canadian pacific railway identifiers, when the system identifies the message as cpr bond creation type, the desired outcome is that the system initiates cpr-specific bond creation processing workflow.
💻 Technical Criteria
Given A K1 segment message contains Canadian Pacific Railway identifiers
When The system identifies the message as CPR bond creation type
Then The system initiates CPR-specific bond creation processing workflow
R-GCX016E-cbl-02592 Validate Bond Data
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Bond Data' is invoked, and assuming that bond information has been extracted from a cpr message, when the system validates the bond data for completeness and format compliance, the desired outcome is that the bond data is marked as valid if all required fields are present and properly formatted, otherwise validation fails.
💻 Technical Criteria
Given Bond information has been extracted from a CPR message
When The system validates the bond data for completeness and format compliance
Then The bond data is marked as valid if all required fields are present and properly formatted, otherwise validation fails
R-GCX016E-cbl-02593 Bond Creation Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Bond Creation Valid?' is invoked, and assuming that bond data validation has been completed, when the system evaluates if the bond creation meets all business requirements, the desired outcome is that bond creation is approved if validation passes and all business rules are satisfied, otherwise an error is generated.
💻 Technical Criteria
Given Bond data validation has been completed
When The system evaluates if the bond creation meets all business requirements
Then Bond creation is approved if validation passes and all business rules are satisfied, otherwise an error is generated
R-GCX016E-cbl-02595 Add Special Comments
Process Rules
📊 Business Logic Narrative
When the process 'Add Special Comments' is invoked, and assuming that a cpr bond notification message has been formatted, when the system processes special comments from k1 segments and other relevant sources, the desired outcome is that up to 3 lines of special comments and up to 4 lines of k1 comments are added to the notification message if available.
💻 Technical Criteria
Given A CPR bond notification message has been formatted
When The system processes special comments from K1 segments and other relevant sources
Then Up to 3 lines of special comments and up to 4 lines of K1 comments are added to the notification message if available
R-GCX016E-cbl-02596 Create Merlin Message
Action Rules
📊 Business Logic Narrative
When the process 'Create Merlin Message' is invoked, and assuming that cpr bond notification content has been prepared with special comments, when the system creates a merlin message for the bond notification, the desired outcome is that a properly formatted merlin message is created with cpr bond information, comments, and appropriate message headers.
💻 Technical Criteria
Given CPR bond notification content has been prepared with special comments
When The system creates a Merlin message for the bond notification
Then A properly formatted Merlin message is created with CPR bond information, comments, and appropriate message headers
R-GCX016E-cbl-02597 Route to Recipients
Decision Rules
📊 Business Logic Narrative
When the process 'Route to Recipients' is invoked, and assuming that a merlin message for cpr bond notification has been created, when the system determines routing based on freight forwarder setup and notification preferences, the desired outcome is that the message is routed to appropriate recipients including freight forwarders with internet capability or default merlin ids.
💻 Technical Criteria
Given A Merlin message for CPR bond notification has been created
When The system determines routing based on freight forwarder setup and notification preferences
Then The message is routed to appropriate recipients including freight forwarders with internet capability or default Merlin IDs
R-GCX016E-cbl-02598 Log Bond Creation Event
Process Rules
📊 Business Logic Narrative
When the process 'Log Bond Creation Event' is invoked, and assuming that cpr bond notification routing has been determined, when the system logs the bond creation event, the desired outcome is that an audit record is created capturing the bond creation details, timestamp, and processing status for tracking and compliance purposes.
💻 Technical Criteria
Given CPR bond notification routing has been determined
When The system logs the bond creation event
Then An audit record is created capturing the bond creation details, timestamp, and processing status for tracking and compliance purposes
R-GCX016E-cbl-02599 Send Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send Notification' is invoked, and assuming that cpr bond notification has been logged and routed, when the system attempts to deliver the notification, the desired outcome is that the notification is sent via email if freight forwarder has internet capability, otherwise sent to merlin system, with fallback to backup recipients if delivery fails.
💻 Technical Criteria
Given CPR bond notification has been logged and routed
When The system attempts to deliver the notification
Then The notification is sent via email if freight forwarder has internet capability, otherwise sent to Merlin system, with fallback to backup recipients if delivery fails
R-GCX016E-cbl-02600 Generate Error Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Error Message' is invoked, and assuming that cpr bond creation validation has failed or processing errors occurred, when the system generates an error response, the desired outcome is that an appropriate error message is created indicating the specific validation failure or processing issue for troubleshooting and correction.
💻 Technical Criteria
Given CPR bond creation validation has failed or processing errors occurred
When The system generates an error response
Then An appropriate error message is created indicating the specific validation failure or processing issue for troubleshooting and correction
R-GCX016E-cbl-02839 Shiproot Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Shiproot Found?' is invoked, and assuming that shiproot record validation has been performed, when the system evaluates the shiproot record existence result, the desired outcome is that if shiproot is found, proceed to retrieve in-bond type code; if not found, terminate the shipment minimum creation process.
💻 Technical Criteria
Given Shiproot record validation has been performed
When The system evaluates the shiproot record existence result
Then If shiproot is found, proceed to retrieve in-bond type code; if not found, terminate the shipment minimum creation process
R-GCX016E-cbl-02846 Populate In-Bond Type Code in U1
Action Rules
📊 Business Logic Narrative
When the process 'Populate In-Bond Type Code in U1' is invoked, and assuming that u1 segment has been created and in-bond type code is available, when the system populates in-bond type code in the u1 segment, the desired outcome is that the in-bond type code should be correctly populated in the appropriate field of the u1 segment.
💻 Technical Criteria
Given U1 segment has been created and in-bond type code is available
When The system populates in-bond type code in the U1 segment
Then The in-bond type code should be correctly populated in the appropriate field of the U1 segment
R-GCX016E-cbl-02847 Populate Entry Number in U1
Action Rules
📊 Business Logic Narrative
When the process 'Populate Entry Number in U1' is invoked, and assuming that in-bond type code has been populated in u1 segment and entry number information is available, when the system populates entry number in the u1 segment, the desired outcome is that entry number information should be correctly populated in the appropriate field of the u1 segment.
💻 Technical Criteria
Given In-bond type code has been populated in U1 segment and entry number information is available
When The system populates entry number in the U1 segment
Then Entry number information should be correctly populated in the appropriate field of the U1 segment
📍 Routing, Border & Port 361 logic blocks
R-GCX016E-cbl-00006 Message Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Message Type?' is invoked, and assuming that message array has been initialized, when message contains train-related segments (m10 with vessel/train info), the desired outcome is that route to train processing path.
💻 Technical Criteria
Given Message array has been initialized
When Message contains train-related segments (M10 with vessel/train info)
Then Route to train processing path
R-GCX016E-cbl-00052 85:CIH Hold Email Notification
Action Rules
📊 Business Logic Narrative
When the process '85:CIH Hold Email Notification' is invoked, and assuming that disposition code is freight forwarder type, when email notification is required and freight forwarder has internet capability, the desired outcome is that route email to freight forwarder email address, otherwise route to default merlin id.
💻 Technical Criteria
Given Disposition code is freight forwarder type
When Email notification is required and freight forwarder has internet capability
Then Route email to freight forwarder email address, otherwise route to default Merlin ID
R-GCX016E-cbl-00054 88:Merlin Message Distribution
Action Rules
📊 Business Logic Narrative
When the process '88:Merlin Message Distribution' is invoked, and assuming that merlin message is ready for distribution, when message type is error message, the desired outcome is that route to 'in' destination.
💻 Technical Criteria
Given Merlin message is ready for distribution
When Message type is error message
Then Route to 'IN' destination
R-GCX016E-cbl-00055 88:Merlin Message Distribution
Action Rules
📊 Business Logic Narrative
When the process '88:Merlin Message Distribution' is invoked, and assuming that merlin message is informational type, when info message routing is performed, the desired outcome is that route to 'in' plus sd segment merlin ids.
💻 Technical Criteria
Given Merlin message is informational type
When Info message routing is performed
Then Route to 'IN' plus SD segment Merlin IDs
R-GCX016E-cbl-00056 88:Merlin Message Distribution
Action Rules
📊 Business Logic Narrative
When the process '88:Merlin Message Distribution' is invoked, and assuming that merlin message is release type, when release message routing is performed, the desired outcome is that route to sd segment merlin ids only.
💻 Technical Criteria
Given Merlin message is release type
When Release message routing is performed
Then Route to SD segment Merlin IDs only
R-GCX016E-cbl-00057 88:Merlin Message Distribution
Action Rules
📊 Business Logic Narrative
When the process '88:Merlin Message Distribution' is invoked, and assuming that merlin message is unrelease type, when unrelease message routing is performed, the desired outcome is that route to om01247 plus sd cancel merlin ids.
💻 Technical Criteria
Given Merlin message is unrelease type
When Unrelease message routing is performed
Then Route to OM01247 plus SD cancel Merlin IDs
R-GCX016E-cbl-00059 88:Merlin Message Distribution
Action Rules
📊 Business Logic Narrative
When the process '88:Merlin Message Distribution' is invoked, and assuming that primary merlin id is invalid, when merlin id validation fails, the desired outcome is that reroute to om01247 with error notification.
💻 Technical Criteria
Given Primary Merlin ID is invalid
When Merlin ID validation fails
Then Reroute to OM01247 with error notification
R-GCX016E-cbl-00060 Check Message Type for GCW016
Decision Rules
📊 Business Logic Narrative
When the process 'Check Message Type for GCW016' is invoked, and assuming that a message is being processed for customs edi transactions, when the message id is gcw016, the desired outcome is that skip mq processing and use internal message structure directly.
💻 Technical Criteria
Given A message is being processed for customs EDI transactions
When The message ID is GCW016
Then Skip MQ processing and use internal message structure directly
R-GCX016E-cbl-00061 Establish MQ Connection
Action Rules
📊 Business Logic Narrative
When the process 'Establish MQ Connection' is invoked, and assuming that the system needs to retrieve customs messages from mq, when mq connection is initiated, the desired outcome is that connect to mq system and prepare for queue operations.
💻 Technical Criteria
Given The system needs to retrieve customs messages from MQ
When MQ connection is initiated
Then Connect to MQ system and prepare for queue operations
R-GCX016E-cbl-00062 Open GC350.EXP.INPUT Queue
Action Rules
📊 Business Logic Narrative
When the process 'Open GC350.EXP.INPUT Queue' is invoked, and assuming that mq connection is established, when queue open operation is requested for gc350.exp.input, the desired outcome is that open the queue for reading customs export messages.
💻 Technical Criteria
Given MQ connection is established
When Queue open operation is requested for GC350.EXP.INPUT
Then Open the queue for reading customs export messages
R-GCX016E-cbl-00064 Execute MQGET to Retrieve Message
Action Rules
📊 Business Logic Narrative
When the process 'Execute MQGET to Retrieve Message' is invoked, and assuming that the gc350.exp.input queue is open and accessible, when mqget operation is executed, the desired outcome is that retrieve the next available customs message from the queue.
💻 Technical Criteria
Given The GC350.EXP.INPUT queue is open and accessible
When MQGET operation is executed
Then Retrieve the next available customs message from the queue
R-GCX016E-cbl-00065 Message Available?
Decision Rules
📊 Business Logic Narrative
When the process 'Message Available?' is invoked, and assuming that mqget operation has been executed on the customs queue, when message completion code is evaluated, the desired outcome is that if completion code is ok, message is available; if reason code 2033, no message available; otherwise message error occurred.
💻 Technical Criteria
Given MQGET operation has been executed on the customs queue
When Message completion code is evaluated
Then If completion code is OK, message is available; if reason code 2033, no message available; otherwise message error occurred
R-GCX016E-cbl-00066 Backout Count Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Backout Count Valid?' is invoked, and assuming that a customs message is available from the queue, when message backout count is checked, the desired outcome is that if backout count is zero, message is good for processing; if backout count is not zero, skip the message.
💻 Technical Criteria
Given A customs message is available from the queue
When Message backout count is checked
Then If backout count is zero, message is good for processing; if backout count is not zero, skip the message
R-GCX016E-cbl-00067 Set Good Message Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Good Message Flag' is invoked, and assuming that a customs message is available and has valid backout count, when message validation is complete, the desired outcome is that set good message flag to indicate message is ready for processing.
💻 Technical Criteria
Given A customs message is available and has valid backout count
When Message validation is complete
Then Set good message flag to indicate message is ready for processing
R-GCX016E-cbl-00068 Set Skip Message Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Skip Message Flag' is invoked, and assuming that a customs message is available but has invalid backout count, when message backout count validation fails, the desired outcome is that set skip message flag to bypass processing of this message.
💻 Technical Criteria
Given A customs message is available but has invalid backout count
When Message backout count validation fails
Then Set skip message flag to bypass processing of this message
R-GCX016E-cbl-00069 Set Message Not Available Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Message Not Available Flag' is invoked, and assuming that mqget operation has been attempted on customs queue, when no message is available or queue open failed or message error occurred, the desired outcome is that set message not available flag to indicate no messages to process.
💻 Technical Criteria
Given MQGET operation has been attempted on customs queue
When No message is available or queue open failed or message error occurred
Then Set message not available flag to indicate no messages to process
R-GCX016E-cbl-02866 Execute MQGET to Retrieve Message from GC350.EXP.INPUT Queue
Action Rules
📊 Business Logic Narrative
When the process 'Execute MQGET to Retrieve Message from GC350.EXP.INPUT Queue' is invoked, and assuming that the system needs to process export messages, when a message retrieval request is initiated, the desired outcome is that the system executes mqget operation to retrieve the next available message from gc350.exp.input queue.
💻 Technical Criteria
Given The system needs to process export messages
When A message retrieval request is initiated
Then The system executes MQGET operation to retrieve the next available message from GC350.EXP.INPUT queue
R-GCX016E-cbl-03129 Train ID Contains CPRS Indicator?
Decision Rules
📊 Business Logic Narrative
When the process 'Train ID Contains CPRS Indicator?' is invoked, and assuming that a train record is being processed for arrival or departure, when the system evaluates the train id for cprs indicators or canadian pacific railway naming conventions, the desired outcome is that the system routes the train to cprs-specific processing if indicators are found, otherwise processes as regular train.
💻 Technical Criteria
Given A train record is being processed for arrival or departure
When The system evaluates the train ID for CPRS indicators or Canadian Pacific Railway naming conventions
Then The system routes the train to CPRS-specific processing if indicators are found, otherwise processes as regular train
R-GCX016E-cbl-00078 Train Found in System?
Decision Rules
📊 Business Logic Narrative
When the process 'Train Found in System?' is invoked, and assuming that a train id has been extracted from the m10 segment, when the system searches for the train in the gcwtl train list segments, the desired outcome is that the system determines if the train exists and routes processing accordingly.
💻 Technical Criteria
Given A train ID has been extracted from the M10 segment
When The system searches for the train in the GCWTL train list segments
Then The system determines if the train exists and routes processing accordingly
R-GCX016E-cbl-00097 Train ID Suffix Check
Decision Rules
📊 Business Logic Narrative
When the process 'Train ID Suffix Check' is invoked, and assuming that a train arrival event (pod/aad disposition code) is being processed, when the system examines the train id suffix, the desired outcome is that if the train id ends with suffix 't', classify as export manifest train, otherwise classify as import manifest train.
💻 Technical Criteria
Given A train arrival event (POD/AAD disposition code) is being processed
When The system examines the train ID suffix
Then If the train ID ends with suffix 'T', classify as export manifest train, otherwise classify as import manifest train
R-GCX016E-cbl-00098 Export Manifest Train - Suffix 'T'
Process Rules
📊 Business Logic Narrative
When the process 'Export Manifest Train - Suffix 'T'' is invoked, and assuming that a train has been classified as export manifest train (suffix 't'), when the train arrival processing begins, the desired outcome is that execute export manifest pre-arrival processing procedures.
💻 Technical Criteria
Given A train has been classified as export manifest train (suffix 'T')
When The train arrival processing begins
Then Execute export manifest pre-arrival processing procedures
R-GCX016E-cbl-00099 Import Manifest Train - No Suffix 'T'
Process Rules
📊 Business Logic Narrative
When the process 'Import Manifest Train - No Suffix 'T'' is invoked, and assuming that a train has been classified as import manifest train (no suffix 't'), when the train arrival processing begins, the desired outcome is that execute standard import manifest arrival processing procedures.
💻 Technical Criteria
Given A train has been classified as import manifest train (no suffix 'T')
When The train arrival processing begins
Then Execute standard import manifest arrival processing procedures
R-GCX016E-cbl-00100 Export Manifest Port Validation
Validation Rules
📊 Business Logic Narrative
When the process 'Export Manifest Port Validation' is invoked, and assuming that an export manifest train is being processed for arrival, when the system validates the port location, the desired outcome is that if the port is valid for export operations, proceed with export manifest arrival flag setting, otherwise redirect to import manifest processing.
💻 Technical Criteria
Given An export manifest train is being processed for arrival
When The system validates the port location
Then If the port is valid for export operations, proceed with export manifest arrival flag setting, otherwise redirect to import manifest processing
R-GCX016E-cbl-00101 Set Export Manifest Arrival Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Export Manifest Arrival Flag' is invoked, and assuming that an export manifest train has passed port validation, when the arrival processing continues, the desired outcome is that set the export manifest arrival flag to indicate successful export arrival.
💻 Technical Criteria
Given An export manifest train has passed port validation
When The arrival processing continues
Then Set the export manifest arrival flag to indicate successful export arrival
R-GCX016E-cbl-00102 Set Standard Arrival Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Standard Arrival Flag' is invoked, and assuming that a train is either an import manifest train or an export train that failed port validation, when the arrival processing continues, the desired outcome is that set the standard arrival flag to indicate train arrival.
💻 Technical Criteria
Given A train is either an import manifest train or an export train that failed port validation
When The arrival processing continues
Then Set the standard arrival flag to indicate train arrival
R-GCX016E-cbl-00103 Set Train Arrival Date from V9 Segment
Action Rules
📊 Business Logic Narrative
When the process 'Set Train Arrival Date from V9 Segment' is invoked, and assuming that a train arrival flag has been set (either export or standard), when the system processes the v9 segment containing arrival information, the desired outcome is that extract the arrival date from the v9 segment and assign it as the train's official arrival date.
💻 Technical Criteria
Given A train arrival flag has been set (either export or standard)
When The system processes the V9 segment containing arrival information
Then Extract the arrival date from the V9 segment and assign it as the train's official arrival date
R-GCX016E-cbl-00112 Is Train Export Manifest?
Decision Rules
📊 Business Logic Narrative
When the process 'Is Train Export Manifest?' is invoked, and assuming that a train record exists in the system, when the system needs to determine if it's an export manifest train, the desired outcome is that the system checks the train id suffix to identify export manifest trains.
💻 Technical Criteria
Given A train record exists in the system
When The system needs to determine if it's an export manifest train
Then The system checks the train ID suffix to identify export manifest trains
R-GCX016E-cbl-00113 Train ID ends with 'T'?
Validation Rules
📊 Business Logic Narrative
When the process 'Train ID ends with 'T'?' is invoked, and assuming that a train id is available for processing, when the system checks the train id suffix, the desired outcome is that if the train id ends with 't', it is classified as an export manifest train, otherwise it is processed as a regular train.
💻 Technical Criteria
Given A train ID is available for processing
When The system checks the train ID suffix
Then If the train ID ends with 'T', it is classified as an export manifest train, otherwise it is processed as a regular train
R-GCX016E-cbl-00114 Mark as Export Manifest Train
Action Rules
📊 Business Logic Narrative
When the process 'Mark as Export Manifest Train' is invoked, and assuming that a train has been identified as an export manifest train, when the system processes the train classification, the desired outcome is that the train is marked with export manifest status for subsequent processing.
💻 Technical Criteria
Given A train has been identified as an export manifest train
When The system processes the train classification
Then The train is marked with export manifest status for subsequent processing
R-GCX016E-cbl-00186 Send Seizure Notification to Customs
Action Rules
📊 Business Logic Narrative
When the process 'Send Seizure Notification to Customs' is invoked, and assuming that a merlin notification message has been generated for train seizure, when the system sends notifications to relevant parties, the desired outcome is that the system sends the seizure notification to customs authorities.
💻 Technical Criteria
Given A Merlin notification message has been generated for train seizure
When The system sends notifications to relevant parties
Then The system sends the seizure notification to customs authorities
R-GCX016E-cbl-00214 Set Train All Clear Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Train All Clear Status Flag' is invoked, and assuming that a valid train has been found in the system, when the cae disposition code is processed, the desired outcome is that the train all clear status flag is set to indicate the train is cleared for export.
💻 Technical Criteria
Given A valid train has been found in the system
When The CAE disposition code is processed
Then The train all clear status flag is set to indicate the train is cleared for export
R-GCX016E-cbl-00263 Train ID ends with 'T'?
Decision Rules
📊 Business Logic Narrative
When the process 'Train ID ends with 'T'?' is invoked, and assuming that a train arrival event is received with pod or aad disposition code and train id has been extracted from m10 vessel name segment, when the system checks the last character of the train id, the desired outcome is that if the train id ends with 't', identify as export manifest train, otherwise identify as import manifest train.
💻 Technical Criteria
Given A train arrival event is received with POD or AAD disposition code and train ID has been extracted from M10 vessel name segment
When The system checks the last character of the train ID
Then If the train ID ends with 'T', identify as export manifest train, otherwise identify as import manifest train
R-GCX016E-cbl-00264 Identify as Export Manifest Train
Process Rules
📊 Business Logic Narrative
When the process 'Identify as Export Manifest Train' is invoked, and assuming that train id ends with 't' indicating export manifest train, when the system processes the train identification, the desired outcome is that set train type as export manifest and proceed to port validation for export processing.
💻 Technical Criteria
Given Train ID ends with 'T' indicating export manifest train
When The system processes the train identification
Then Set train type as export manifest and proceed to port validation for export processing
R-GCX016E-cbl-00265 Identify as Import Manifest Train
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Identify as Import Manifest Train', assuming that train id does not end with 't', when the system processes the train identification, the desired outcome is that set train type as import manifest and route to standard import processing workflow.
💻 Technical Criteria
EXCLUDING Train ID does not end with 'T'
When The system processes the train identification
Then Set train type as import manifest and route to standard import processing workflow
R-GCX016E-cbl-00266 Port Designated for Export Manifests?
Validation Rules
📊 Business Logic Narrative
When the process 'Port Designated for Export Manifests?' is invoked, and assuming that export manifest train has been identified and arrival port has been extracted from p4 location segment, when the system validates the port designation, the desired outcome is that if port is designated for export manifests, proceed with export processing, otherwise route to standard import processing.
💻 Technical Criteria
Given Export manifest train has been identified and arrival port has been extracted from P4 location segment
When The system validates the port designation
Then If port is designated for export manifests, proceed with export processing, otherwise route to standard import processing
R-GCX016E-cbl-00267 Set Export Manifest Train Status
Action Rules
📊 Business Logic Narrative
When the process 'Set Export Manifest Train Status' is invoked, and assuming that export manifest train has been validated and port is designated for export processing, when the system processes the export manifest train arrival, the desired outcome is that set train status to export manifest arrived and prepare for subsequent processing steps.
💻 Technical Criteria
Given Export manifest train has been validated and port is designated for export processing
When The system processes the export manifest train arrival
Then Set train status to export manifest arrived and prepare for subsequent processing steps
R-GCX016E-cbl-00268 Update Train Arrival Date from V9 Segment
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Arrival Date from V9 Segment' is invoked, and assuming that export manifest train status has been set and v9 segment contains arrival date/time information, when the system processes the arrival date update, the desired outcome is that extract and record the arrival date and time from v9 segment into the train record.
💻 Technical Criteria
Given Export manifest train status has been set and V9 segment contains arrival date/time information
When The system processes the arrival date update
Then Extract and record the arrival date and time from V9 segment into the train record
R-GCX016E-cbl-00269 Log Export Manifest Train Arrival
Action Rules
📊 Business Logic Narrative
When the process 'Log Export Manifest Train Arrival' is invoked, and assuming that export manifest train arrival date has been updated successfully, when the system completes the arrival processing, the desired outcome is that create audit log entry recording the export manifest train arrival with train id, port, and arrival timestamp.
💻 Technical Criteria
Given Export manifest train arrival date has been updated successfully
When The system completes the arrival processing
Then Create audit log entry recording the export manifest train arrival with train ID, port, and arrival timestamp
R-GCX016E-cbl-00270 Generate Export Manifest Arrival Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Export Manifest Arrival Notification' is invoked, and assuming that export manifest train arrival has been logged successfully, when the system generates arrival notifications, the desired outcome is that create and send export manifest arrival notification containing train details, arrival information, and routing to appropriate recipients.
💻 Technical Criteria
Given Export manifest train arrival has been logged successfully
When The system generates arrival notifications
Then Create and send export manifest arrival notification containing train details, arrival information, and routing to appropriate recipients
R-GCX016E-cbl-00271 Route to Standard Import Processing
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Route to Standard Import Processing', assuming that train is identified as import type or export train port is not designated for export processing, when the system determines processing route, the desired outcome is that route train to standard import processing workflow and complete processing according to import procedures.
💻 Technical Criteria
EXCLUDING Train is identified as import type OR export train port is not designated for export processing
When The system determines processing route
Then Route train to standard import processing workflow and complete processing according to import procedures
R-GCX016E-cbl-00272 Train ID Suffix Check
Decision Rules
📊 Business Logic Narrative
When the process 'Train ID Suffix Check' is invoked, and assuming that a train arrival event (pod/aad disposition code) is being processed, when the system checks the train id suffix, the desired outcome is that if train id ends with suffix 't', route to export manifest processing, otherwise route to import manifest processing.
💻 Technical Criteria
Given A train arrival event (POD/AAD disposition code) is being processed
When The system checks the train ID suffix
Then If train ID ends with suffix 'T', route to export manifest processing, otherwise route to import manifest processing
R-GCX016E-cbl-00273 Set Train Arrival Status
Action Rules
📊 Business Logic Narrative
When the process 'Set Train Arrival Status' is invoked, and assuming that a train is being processed for import manifest arrival, when the train arrival status needs to be established, the desired outcome is that set the train arrival status flag to indicate the train has arrived for import processing.
💻 Technical Criteria
Given A train is being processed for import manifest arrival
When The train arrival status needs to be established
Then Set the train arrival status flag to indicate the train has arrived for import processing
R-GCX016E-cbl-00282 Train ID has 'T' suffix?
Decision Rules
📊 Business Logic Narrative
When the process 'Train ID has 'T' suffix?' is invoked, and assuming that a train arrival event is received with a train id, when the system checks if the train id has a 't' suffix, the desired outcome is that the train is classified as export manifest if suffix is 't', otherwise as import manifest.
💻 Technical Criteria
Given A train arrival event is received with a train ID
When The system checks if the train ID has a 'T' suffix
Then The train is classified as export manifest if suffix is 'T', otherwise as import manifest
R-GCX016E-cbl-00283 Port Designated for Export Manifests?
Validation Rules
📊 Business Logic Narrative
When the process 'Port Designated for Export Manifests?' is invoked, and assuming that an export manifest train arrives at a specific port and the port code is extracted from p4 location segment, when the system looks up the port in the export manifest port configuration table, the desired outcome is that the port is validated as authorized for export manifests if found in the table, otherwise validation fails.
💻 Technical Criteria
Given An export manifest train arrives at a specific port AND the port code is extracted from P4 location segment
When The system looks up the port in the export manifest port configuration table
Then The port is validated as authorized for export manifests if found in the table, otherwise validation fails
R-GCX016E-cbl-00284 Set Export Manifest Port Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Export Manifest Port Flag' is invoked, and assuming that an export manifest train arrives at a port and the port is validated as authorized for export manifests, when the port validation succeeds, the desired outcome is that the system sets the export manifest port flag and continues with export manifest processing.
💻 Technical Criteria
Given An export manifest train arrives at a port AND the port is validated as authorized for export manifests
When The port validation succeeds
Then The system sets the export manifest port flag and continues with export manifest processing
R-GCX016E-cbl-00285 Generate Port Validation Error
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Port Validation Error', assuming that an export manifest train arrives at a port and the port is not found in the export manifest port configuration table, when the port validation fails, the desired outcome is that the system generates a port validation error and logs the invalid port for export manifest incident.
💻 Technical Criteria
EXCLUDING An export manifest train arrives at a port AND the port is not found in the export manifest port configuration table
When The port validation fails
Then The system generates a port validation error and logs the invalid port for export manifest incident
R-GCX016E-cbl-00286 Route to Standard Import Processing
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Route to Standard Import Processing', assuming that a train arrival event is received and either the train id does not have 't' suffix or the export manifest port validation fails, when the train is classified as import manifest or export port validation fails, the desired outcome is that the system routes the train to standard import processing workflow.
💻 Technical Criteria
EXCLUDING A train arrival event is received AND either the train ID does not have 'T' suffix OR the export manifest port validation fails
When The train is classified as import manifest or export port validation fails
Then The system routes the train to standard import processing workflow
R-GCX016E-cbl-00287 Train Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Train Type?' is invoked, and assuming that a train arrival event has been detected, when the system evaluates the train's manifest type, the desired outcome is that the train is classified as either export manifest train (suffix 't') or import manifest train for appropriate aei processing.
💻 Technical Criteria
Given A train arrival event has been detected
When The system evaluates the train's manifest type
Then The train is classified as either export manifest train (suffix 'T') or import manifest train for appropriate AEI processing
R-GCX016E-cbl-00288 Port Valid for Export?
Validation Rules
📊 Business Logic Narrative
When the process 'Port Valid for Export?' is invoked, and assuming that an export manifest train has arrived at a port, when the system validates the port's export processing capabilities, the desired outcome is that the port is either confirmed as valid for export processing or flagged as invalid, determining the processing path.
💻 Technical Criteria
Given An export manifest train has arrived at a port
When The system validates the port's export processing capabilities
Then The port is either confirmed as valid for export processing or flagged as invalid, determining the processing path
R-GCX016E-cbl-00289 Process Export Manifest Arrival
Process Rules
📊 Business Logic Narrative
When the process 'Process Export Manifest Arrival' is invoked, and assuming that an export manifest train has arrived and the port is valid for export processing, when the system processes the export manifest arrival, the desired outcome is that export-specific aei processing is initiated with appropriate export manifest handling procedures.
💻 Technical Criteria
Given An export manifest train has arrived and the port is valid for export processing
When The system processes the export manifest arrival
Then Export-specific AEI processing is initiated with appropriate export manifest handling procedures
R-GCX016E-cbl-00290 Process Import Manifest Arrival
Process Rules
📊 Business Logic Narrative
When the process 'Process Import Manifest Arrival' is invoked, and assuming that either an import manifest train has arrived or an export train has arrived at a port invalid for export processing, when the system processes the manifest arrival, the desired outcome is that import-specific aei processing is initiated with appropriate import manifest handling procedures.
💻 Technical Criteria
Given Either an import manifest train has arrived or an export train has arrived at a port invalid for export processing
When The system processes the manifest arrival
Then Import-specific AEI processing is initiated with appropriate import manifest handling procedures
R-GCX016E-cbl-03173 Identify Counterpart Code Types
Definitional Rules
📊 Business Logic Narrative
When the process 'Identify Counterpart Code Types' is invoked, and assuming that conflicting disposition codes have been found in the status array, when the system analyzes the conflicting codes, the desired outcome is that each conflicting code is classified by type (hold, release, proceed, cancel, arrival, export) for targeted removal.
💻 Technical Criteria
Given Conflicting disposition codes have been found in the status array
When The system analyzes the conflicting codes
Then Each conflicting code is classified by type (hold, release, proceed, cancel, arrival, export) for targeted removal
R-GCX016E-cbl-03179 Remove Export Codes if Cancel Export Added
Action Rules
📊 Business Logic Narrative
When the process 'Remove Export Codes if Cancel Export Added' is invoked, and assuming that a cancel export disposition code is being added and export codes exist in the status array, when the system processes the cancel export code addition, the desired outcome is that all conflicting export disposition codes are removed from the status array.
💻 Technical Criteria
Given A cancel export disposition code is being added and export codes exist in the status array
When The system processes the cancel export code addition
Then All conflicting export disposition codes are removed from the status array
R-GCX016E-cbl-03363 Apply Special Border Crossing Logic
Process Rules
📊 Business Logic Narrative
When the process 'Apply Special Border Crossing Logic' is invoked, and assuming that the entry type code is identified as a border crossing code, when the system applies border crossing specific processing rules, the desired outcome is that special border crossing logic is applied including canadian border location mapping.
💻 Technical Criteria
Given The entry type code is identified as a border crossing code
When The system applies border crossing specific processing rules
Then Special border crossing logic is applied including Canadian border location mapping
R-GCX016E-cbl-03478 Validate Canadian Border Location
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Canadian Border Location' is invoked, and assuming that a mapped canadian border location code and the canadian border location table, when the system validates the canadian border location, the desired outcome is that the system confirms whether the canadian location exists in the reference table.
💻 Technical Criteria
Given A mapped Canadian border location code and the Canadian Border Location Table
When The system validates the Canadian border location
Then The system confirms whether the Canadian location exists in the reference table
R-GCX016E-cbl-03206 Train ID Suffix Check
Decision Rules
📊 Business Logic Narrative
When the process 'Train ID Suffix Check' is invoked, and assuming that a train arrival processing event (pod/aad disposition) is being processed, when the system checks the train id suffix, the desired outcome is that if train id ends with 't', classify as export manifest train, otherwise classify as import manifest train.
💻 Technical Criteria
Given A train arrival processing event (POD/AAD disposition) is being processed
When The system checks the train ID suffix
Then If train ID ends with 'T', classify as export manifest train, otherwise classify as import manifest train
R-GCX016E-cbl-03207 Export Manifest Port Validation
Validation Rules
📊 Business Logic Narrative
When the process 'Export Manifest Port Validation' is invoked, and assuming that an export manifest train (suffix 't') is arriving at a port, when the system validates the arrival port against export port configuration, the desired outcome is that if port is designated for export, allow export manifest processing, otherwise generate validation message.
💻 Technical Criteria
Given An export manifest train (suffix 'T') is arriving at a port
When The system validates the arrival port against export port configuration
Then If port is designated for export, allow export manifest processing, otherwise generate validation message
R-GCX016E-cbl-03208 Arrival Port Designated for Export?
Decision Rules
📊 Business Logic Narrative
When the process 'Arrival Port Designated for Export?' is invoked, and assuming that an export manifest train is processed and arrival port information is available from p4 location segments, when the system checks if the arrival port is designated for export processing, the desired outcome is that if port is designated for export, proceed with export manifest business rules, otherwise generate location validation messages.
💻 Technical Criteria
Given An export manifest train is processed and arrival port information is available from P4 location segments
When The system checks if the arrival port is designated for export processing
Then If port is designated for export, proceed with export manifest business rules, otherwise generate location validation messages
R-GCX016E-cbl-03209 Apply Export Manifest Business Rules
Process Rules
📊 Business Logic Narrative
When the process 'Apply Export Manifest Business Rules' is invoked, and assuming that a train is identified as export manifest and arrival port is validated for export, when the system processes the export manifest, the desired outcome is that apply export-specific processing rules including location validation and status updates.
💻 Technical Criteria
Given A train is identified as export manifest and arrival port is validated for export
When The system processes the export manifest
Then Apply export-specific processing rules including location validation and status updates
R-GCX016E-cbl-03210 Standard Import Processing Rules
Process Rules
📊 Business Logic Narrative
When the process 'Standard Import Processing Rules' is invoked, and assuming that a train is identified as import manifest (no 't' suffix), when the system processes the import manifest, the desired outcome is that apply standard import processing rules and proceed to location validation.
💻 Technical Criteria
Given A train is identified as import manifest (no 'T' suffix)
When The system processes the import manifest
Then Apply standard import processing rules and proceed to location validation
R-GCX016E-cbl-03211 Valid Destination Location?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid Destination Location?' is invoked, and assuming that location identifier information is available from p4 location segments, when the system validates the destination location against destination station table, the desired outcome is that if destination location is valid, proceed with location-specific rule application, otherwise generate location validation messages.
💻 Technical Criteria
Given Location identifier information is available from P4 location segments
When The system validates the destination location against destination station table
Then If destination location is valid, proceed with location-specific rule application, otherwise generate location validation messages
R-GCX016E-cbl-03212 Border Crossing Location?
Decision Rules
📊 Business Logic Narrative
When the process 'Border Crossing Location?' is invoked, and assuming that a valid destination location is confirmed, when the system checks if the location is a border crossing point, the desired outcome is that if location is border crossing, apply border crossing rules, otherwise apply standard location rules.
💻 Technical Criteria
Given A valid destination location is confirmed
When The system checks if the location is a border crossing point
Then If location is border crossing, apply border crossing rules, otherwise apply standard location rules
R-GCX016E-cbl-03213 Apply Border Crossing Rules
Process Rules
📊 Business Logic Narrative
When the process 'Apply Border Crossing Rules' is invoked, and assuming that a location is identified as a border crossing point, when the system processes the border crossing location, the desired outcome is that apply border-specific processing rules including vessel information swapping and special status handling.
💻 Technical Criteria
Given A location is identified as a border crossing point
When The system processes the border crossing location
Then Apply border-specific processing rules including vessel information swapping and special status handling
R-GCX016E-cbl-03214 Apply Standard Location Rules
Process Rules
📊 Business Logic Narrative
When the process 'Apply Standard Location Rules' is invoked, and assuming that a location is identified as non-border crossing, when the system processes the standard location, the desired outcome is that apply standard location processing rules without special border crossing handling.
💻 Technical Criteria
Given A location is identified as non-border crossing
When The system processes the standard location
Then Apply standard location processing rules without special border crossing handling
R-GCX016E-cbl-03215 Set Export Manifest Status
Action Rules
📊 Business Logic Narrative
When the process 'Set Export Manifest Status' is invoked, and assuming that export manifest business rules have been applied successfully, when the system updates the manifest status, the desired outcome is that set export manifest status and proceed to train arrival status update.
💻 Technical Criteria
Given Export manifest business rules have been applied successfully
When The system updates the manifest status
Then Set export manifest status and proceed to train arrival status update
R-GCX016E-cbl-03216 Set Import Manifest Status
Action Rules
📊 Business Logic Narrative
When the process 'Set Import Manifest Status' is invoked, and assuming that import manifest processing rules have been applied successfully, when the system updates the manifest status, the desired outcome is that set import manifest status and proceed to train arrival status update.
💻 Technical Criteria
Given Import manifest processing rules have been applied successfully
When The system updates the manifest status
Then Set import manifest status and proceed to train arrival status update
R-GCX016E-cbl-03217 Update Train Arrival Status
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Arrival Status' is invoked, and assuming that location-specific rules have been applied and manifest status has been set, when the system finalizes train arrival processing, the desired outcome is that update train arrival status to reflect completed processing and generate location validation messages.
💻 Technical Criteria
Given Location-specific rules have been applied and manifest status has been set
When The system finalizes train arrival processing
Then Update train arrival status to reflect completed processing and generate location validation messages
R-GCX016E-cbl-03218 Generate Location Validation Messages
Action Rules
📊 Business Logic Narrative
When the process 'Generate Location Validation Messages' is invoked, and assuming that train arrival processing is complete or validation errors occurred, when the system generates validation messages, the desired outcome is that create appropriate messages for successful processing or validation failures including invalid ports or destinations.
💻 Technical Criteria
Given Train arrival processing is complete or validation errors occurred
When The system generates validation messages
Then Create appropriate messages for successful processing or validation failures including invalid ports or destinations
R-GCX016E-cbl-03370 Train ID has 'T' suffix?
Decision Rules
📊 Business Logic Narrative
When the process 'Train ID has 'T' suffix?' is invoked, and assuming that a train arrival event is received with a train id, when the system checks if the train id has a 't' suffix, the desired outcome is that if train id has 't' suffix, identify as export manifest train, otherwise route to standard import processing.
💻 Technical Criteria
Given A train arrival event is received with a train ID
When The system checks if the train ID has a 'T' suffix
Then If train ID has 'T' suffix, identify as export manifest train, otherwise route to standard import processing
R-GCX016E-cbl-03371 Identify as Export Manifest Train
Definitional Rules
📊 Business Logic Narrative
When the process 'Identify as Export Manifest Train' is invoked, and assuming that a train id has been validated to contain a 't' suffix, when the system processes the train classification, the desired outcome is that the train is identified and flagged as an export manifest train for export-specific business rule application.
💻 Technical Criteria
Given A train ID has been validated to contain a 'T' suffix
When The system processes the train classification
Then The train is identified and flagged as an export manifest train for export-specific business rule application
R-GCX016E-cbl-03372 Extract Arrival Port from P4 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Arrival Port from P4 Segment' is invoked, and assuming that an export manifest train has been identified, when the system processes the p4 location segment, the desired outcome is that the arrival port information is extracted from the p4 segment for further validation.
💻 Technical Criteria
Given An export manifest train has been identified
When The system processes the P4 location segment
Then The arrival port information is extracted from the P4 segment for further validation
R-GCX016E-cbl-03373 Lookup Port Configuration in System Tables
Action Rules
📊 Business Logic Narrative
When the process 'Lookup Port Configuration in System Tables' is invoked, and assuming that an arrival port has been extracted from the p4 segment, when the system looks up the port configuration in system tables, the desired outcome is that port configuration data is retrieved to determine export manifest processing eligibility.
💻 Technical Criteria
Given An arrival port has been extracted from the P4 segment
When The system looks up the port configuration in system tables
Then Port configuration data is retrieved to determine export manifest processing eligibility
R-GCX016E-cbl-03374 Port Designated for Export Manifests?
Validation Rules
📊 Business Logic Narrative
When the process 'Port Designated for Export Manifests?' is invoked, and assuming that port configuration data has been retrieved from system tables, when the system checks if the port is designated for export manifests, the desired outcome is that if port is designated for export manifests, proceed with export processing, otherwise generate port validation error.
💻 Technical Criteria
Given Port configuration data has been retrieved from system tables
When The system checks if the port is designated for export manifests
Then If port is designated for export manifests, proceed with export processing, otherwise generate port validation error
R-GCX016E-cbl-03375 Apply Export Manifest Business Rules
Process Rules
📊 Business Logic Narrative
When the process 'Apply Export Manifest Business Rules' is invoked, and assuming that the arrival port has been validated as designated for export manifests, when the system applies export manifest business rules, the desired outcome is that export-specific business rules are applied to the manifest processing workflow.
💻 Technical Criteria
Given The arrival port has been validated as designated for export manifests
When The system applies export manifest business rules
Then Export-specific business rules are applied to the manifest processing workflow
R-GCX016E-cbl-03376 Process as Export Manifest Arrival
Process Rules
📊 Business Logic Narrative
When the process 'Process as Export Manifest Arrival' is invoked, and assuming that export manifest business rules have been applied successfully, when the system processes the export manifest arrival, the desired outcome is that the train arrival is processed using export manifest specific procedures and status updates.
💻 Technical Criteria
Given Export manifest business rules have been applied successfully
When The system processes the export manifest arrival
Then The train arrival is processed using export manifest specific procedures and status updates
R-GCX016E-cbl-03377 Generate Port Validation Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Port Validation Error', assuming that the arrival port is not designated for export manifests, when the system generates a port validation error, the desired outcome is that a port validation error is created indicating the port cannot process export manifests.
💻 Technical Criteria
EXCLUDING The arrival port is not designated for export manifests
When The system generates a port validation error
Then A port validation error is created indicating the port cannot process export manifests
R-GCX016E-cbl-03378 Route to Standard Import Processing
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Route to Standard Import Processing', assuming that a train id does not have a 't' suffix, when the system routes the processing, the desired outcome is that the train is routed to standard import processing workflow instead of export processing.
💻 Technical Criteria
EXCLUDING A train ID does not have a 'T' suffix
When The system routes the processing
Then The train is routed to standard import processing workflow instead of export processing
R-GCX016E-cbl-03379 Log Port Validation Result
Process Rules
📊 Business Logic Narrative
When the process 'Log Port Validation Result' is invoked, and assuming that port validation processing has been completed (either successful export processing, error generation, or import routing), when the system logs the validation result, the desired outcome is that the port validation result and processing outcome are logged for audit trail and system monitoring.
💻 Technical Criteria
Given Port validation processing has been completed (either successful export processing, error generation, or import routing)
When The system logs the validation result
Then The port validation result and processing outcome are logged for audit trail and system monitoring
R-GCX016E-cbl-00375 Retrieve Corresponding Canadian Border Location Name
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Corresponding Canadian Border Location Name' is invoked, and assuming that a us port code exists in the canadian border location mapping table, when the system finds a valid mapping entry, the desired outcome is that the corresponding canadian border location name is retrieved from the mapping table.
💻 Technical Criteria
Given A US port code exists in the Canadian border location mapping table
When The system finds a valid mapping entry
Then The corresponding Canadian border location name is retrieved from the mapping table
R-GCX016E-cbl-00401 Include Disposition Information
Process Rules
📊 Business Logic Narrative
When the process 'Include Disposition Information' is invoked, and assuming that origin and destination station information has been included in the email, when the system adds disposition information to the email, the desired outcome is that the email includes disposition codes, hold reasons, and any special handling instructions.
💻 Technical Criteria
Given Origin and destination station information has been included in the email
When The system adds disposition information to the email
Then The email includes disposition codes, hold reasons, and any special handling instructions
R-GCX016E-cbl-00429 Link Follower to Lead Manifest
Process Rules
📊 Business Logic Narrative
When the process 'Link Follower to Lead Manifest' is invoked, and assuming that a follower manifest is being processed and a lead manifest exists, when the follower manifest processing is completed, the desired outcome is that the follower manifest is properly linked to its lead manifest for tracking and reporting purposes.
💻 Technical Criteria
Given A follower manifest is being processed AND a lead manifest exists
When The follower manifest processing is completed
Then The follower manifest is properly linked to its lead manifest for tracking and reporting purposes
R-GCX016E-cbl-00442 Process Transit Routing
Process Rules
📊 Business Logic Narrative
When the process 'Process Transit Routing' is invoked, and assuming that valid canadian records have been identified and linked, when the system processes transit routing information, the desired outcome is that transit routing data is processed and updated for cross-border movement tracking.
💻 Technical Criteria
Given Valid Canadian records have been identified and linked
When The system processes transit routing information
Then Transit routing data is processed and updated for cross-border movement tracking
R-GCX016E-cbl-00502 Log Export Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Export Action' is invoked, and assuming that a disposition code is classified as an export action type, when the system processes the export disposition code, the desired outcome is that the system must log the export action with disposition code details and action description.
💻 Technical Criteria
Given A disposition code is classified as an export action type
When The system processes the export disposition code
Then The system must log the export action with disposition code details and action description
R-GCX016E-cbl-00549 Include Train ID and Location Information
Process Rules
📊 Business Logic Narrative
When the process 'Include Train ID and Location Information' is invoked, and assuming that merlin warning notification is being created, when the system includes train and location information in the notification, the desired outcome is that train id and location information are included in the warning notification for complete operational context.
💻 Technical Criteria
Given Merlin warning notification is being created
When The system includes train and location information in the notification
Then Train ID and location information are included in the warning notification for complete operational context
R-GCX016E-cbl-00550 Set Re-arrival Process Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Re-arrival Process Flag' is invoked, and assuming that warning notification includes train id and location information, when the system sets re-arrival process flag for the train, the desired outcome is that re-arrival process flag is set to ensure proper handling when train actually arrives.
💻 Technical Criteria
Given Warning notification includes train ID and location information
When The system sets re-arrival process flag for the train
Then Re-arrival process flag is set to ensure proper handling when train actually arrives
R-GCX016E-cbl-02962 Populate Array Entry with Location Code
Process Rules
📊 Business Logic Narrative
When the process 'Populate Array Entry with Location Code' is invoked, and assuming that a database status segment contains location code information, when the segment is being converted to array format, the desired outcome is that the system populates the location code field in the corresponding array entry.
💻 Technical Criteria
Given A database status segment contains location code information
When The segment is being converted to array format
Then The system populates the location code field in the corresponding array entry
R-GCX016E-cbl-02996 Generate Merlin Error Message
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Merlin Error Message', assuming that a disposition code is not found in the dc table during lookup, when the system determines the disposition code is invalid, the desired outcome is that the system generates an error message to the merlin messaging system reporting the unknown disposition code.
💻 Technical Criteria
EXCLUDING A disposition code is not found in the DC table during lookup
When The system determines the disposition code is invalid
Then The system generates an error message to the Merlin messaging system reporting the unknown disposition code
R-GCX016E-cbl-03513 Route Error Message to Recipients
Action Rules
📊 Business Logic Narrative
When the process 'Route Error Message to Recipients' is invoked, and assuming that an error message has been formatted and classified, when the system routes the error message, the desired outcome is that the error message is sent to the designated recipients according to error routing rules.
💻 Technical Criteria
Given An error message has been formatted and classified
When The system routes the error message
Then The error message is sent to the designated recipients according to error routing rules
R-GCX016E-cbl-03514 Log Error for Audit Trail
Policy Rules
📊 Business Logic Narrative
When the process 'Log Error for Audit Trail' is invoked, and assuming that an error message has been generated and routed for an unknown disposition code, when the system logs the error, the desired outcome is that the error details are recorded in the audit trail with timestamp and relevant transaction information.
💻 Technical Criteria
Given An error message has been generated and routed for an unknown disposition code
When The system logs the error
Then The error details are recorded in the audit trail with timestamp and relevant transaction information
R-GCX016E-cbl-00686 Valid Border/Destination Location?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid Border/Destination Location?' is invoked, and assuming that an arrival disposition code has been received, when the system validates the arrival location against valid border and destination locations, the desired outcome is that the system continues arrival processing if location is valid, otherwise generates location error message and skips processing.
💻 Technical Criteria
Given An arrival disposition code has been received
When The system validates the arrival location against valid border and destination locations
Then The system continues arrival processing if location is valid, otherwise generates location error message and skips processing
R-GCX016E-cbl-00697 Generate Location Error Message
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Location Error Message', assuming that an arrival location validation has failed, when the system detects an invalid border or destination location, the desired outcome is that a location error message is generated to notify of the invalid location.
💻 Technical Criteria
EXCLUDING An arrival location validation has failed
When The system detects an invalid border or destination location
Then A location error message is generated to notify of the invalid location
R-GCX016E-cbl-00699 Validate Export Location
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Export Location' is invoked, and assuming that an export disposition code has been received with location information, when the system validates the export location against valid export ports, the desired outcome is that the system confirms the location is valid for export processing.
💻 Technical Criteria
Given An export disposition code has been received with location information
When The system validates the export location against valid export ports
Then The system confirms the location is valid for export processing
R-GCX016E-cbl-00700 Valid Export Port?
Decision Rules
📊 Business Logic Narrative
When the process 'Valid Export Port?' is invoked, and assuming that an export location has been specified in the disposition code, when the system checks the location against the valid export port table, the desired outcome is that the system either confirms the port is valid and continues processing or generates an error for invalid ports.
💻 Technical Criteria
Given An export location has been specified in the disposition code
When The system checks the location against the valid export port table
Then The system either confirms the port is valid and continues processing or generates an error for invalid ports
R-GCX016E-cbl-00708 Format Export Message
Process Rules
📊 Business Logic Narrative
When the process 'Format Export Message' is invoked, and assuming that an export notification needs to be generated, when the system creates the export message, the desired outcome is that the system formats the message with proper export notification headers and structure.
💻 Technical Criteria
Given An export notification needs to be generated
When The system creates the export message
Then The system formats the message with proper export notification headers and structure
R-GCX016E-cbl-00714 Export Processing Complete
Process Rules
📊 Business Logic Narrative
When the process 'Export Processing Complete' is invoked, and assuming that all export processing steps have been completed successfully or skipped appropriately, when the system reaches the end of export processing logic, the desired outcome is that the system marks the export processing as complete and returns control to the main processing flow.
💻 Technical Criteria
Given All export processing steps have been completed successfully or skipped appropriately
When The system reaches the end of export processing logic
Then The system marks the export processing as complete and returns control to the main processing flow
R-GCX016E-cbl-00715 Generate Error Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Error Message' is invoked, and assuming that an invalid export port has been detected or other validation has failed, when the system cannot proceed with export processing, the desired outcome is that the system generates an appropriate error message describing the export processing failure.
💻 Technical Criteria
Given An invalid export port has been detected or other validation has failed
When The system cannot proceed with export processing
Then The system generates an appropriate error message describing the export processing failure
R-GCX016E-cbl-00740 Send Notification to Business Users
Action Rules
📊 Business Logic Narrative
When the process 'Send Notification to Business Users' is invoked, and assuming that an export cancellation has been logged and notification prepared, when the system sends notifications to business users, the desired outcome is that export cancellation notifications are sent to brokers, freight forwarders, and other relevant parties via merlin messaging system or email.
💻 Technical Criteria
Given An export cancellation has been logged and notification prepared
When The system sends notifications to business users
Then Export cancellation notifications are sent to brokers, freight forwarders, and other relevant parties via Merlin messaging system or email
R-GCX016E-cbl-00770 Retrieve Location Information
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Location Information' is invoked, and assuming that disposition code details have been collected, when the system accesses station data tables for location information, the desired outcome is that origin station, destination station, and border information are retrieved for the notification.
💻 Technical Criteria
Given Disposition code details have been collected
When The system accesses station data tables for location information
Then Origin station, destination station, and border information are retrieved for the notification
R-GCX016E-cbl-00778 Add Location and Station Data
Process Rules
📊 Business Logic Narrative
When the process 'Add Location and Station Data' is invoked, and assuming that hold reason codes have been included in the notification, when the system processes location data from station tables, the desired outcome is that origin station, destination station, and border information are formatted and added to the message.
💻 Technical Criteria
Given Hold reason codes have been included in the notification
When The system processes location data from station tables
Then Origin station, destination station, and border information are formatted and added to the message
R-GCX016E-cbl-00779 Format Origin Station
Computation Rules
📊 Business Logic Narrative
When the process 'Format Origin Station' is invoked, and assuming that location and station data is being added to the notification, when the system processes origin station information, the desired outcome is that origin station name and code are formatted and included in the notification.
💻 Technical Criteria
Given Location and station data is being added to the notification
When The system processes origin station information
Then Origin station name and code are formatted and included in the notification
R-GCX016E-cbl-00780 Format Destination Station
Computation Rules
📊 Business Logic Narrative
When the process 'Format Destination Station' is invoked, and assuming that origin station has been formatted for the notification, when the system processes destination station information, the desired outcome is that destination station name and code are formatted and included in the notification.
💻 Technical Criteria
Given Origin station has been formatted for the notification
When The system processes destination station information
Then Destination station name and code are formatted and included in the notification
R-GCX016E-cbl-00781 Format Date and Time Information
Computation Rules
📊 Business Logic Narrative
When the process 'Format Date and Time Information' is invoked, and assuming that location and station data has been added to the notification, when the system processes date and time information, the desired outcome is that hold date, time, and related temporal information are formatted according to standard format.
💻 Technical Criteria
Given Location and station data has been added to the notification
When The system processes date and time information
Then Hold date, time, and related temporal information are formatted according to standard format
R-GCX016E-cbl-00786 Route to Merlin Message System
Action Rules
📊 Business Logic Narrative
When the process 'Route to Merlin Message System' is invoked, and assuming that hold notification message has been created and validated, when the system routes the message to the merlin message system, the desired outcome is that the message is successfully queued in the merlin system for distribution.
💻 Technical Criteria
Given Hold notification message has been created and validated
When The system routes the message to the Merlin message system
Then The message is successfully queued in the Merlin system for distribution
R-GCX016E-cbl-00787 Distribute Hold Notification
Process Rules
📊 Business Logic Narrative
When the process 'Distribute Hold Notification' is invoked, and assuming that hold notification has been routed to the merlin message system, when the system processes the message for distribution, the desired outcome is that the hold notification is distributed to all appropriate recipients based on routing rules.
💻 Technical Criteria
Given Hold notification has been routed to the Merlin message system
When The system processes the message for distribution
Then The hold notification is distributed to all appropriate recipients based on routing rules
R-GCX016E-cbl-00793 Process Hold Disposition Code
Process Rules
📊 Business Logic Narrative
When the process 'Process Hold Disposition Code' is invoked, and assuming that a status entry contains a hold-type disposition code, when the hold disposition code is processed, the desired outcome is that hold-specific data including location, reason, and quantity are extracted and processed.
💻 Technical Criteria
Given A status entry contains a hold-type disposition code
When The hold disposition code is processed
Then Hold-specific data including location, reason, and quantity are extracted and processed
R-GCX016E-cbl-00795 Process Proceed Disposition Code
Process Rules
📊 Business Logic Narrative
When the process 'Process Proceed Disposition Code' is invoked, and assuming that a status entry contains a proceed-type disposition code, when the proceed disposition code is processed, the desired outcome is that proceed-specific data including destination, timing, and conditions are extracted and processed.
💻 Technical Criteria
Given A status entry contains a proceed-type disposition code
When The proceed disposition code is processed
Then Proceed-specific data including destination, timing, and conditions are extracted and processed
R-GCX016E-cbl-00797 Update Hold Status Flags
Process Rules
📊 Business Logic Narrative
When the process 'Update Hold Status Flags' is invoked, and assuming that a hold disposition code has been processed, when hold status flags are updated, the desired outcome is that appropriate hold flags are set including border hold, destination hold, fda hold, or general hold based on the disposition code.
💻 Technical Criteria
Given A hold disposition code has been processed
When Hold status flags are updated
Then Appropriate hold flags are set including border hold, destination hold, FDA hold, or general hold based on the disposition code
R-GCX016E-cbl-03265 Hold Takes Precedence?
Policy Rules
📊 Business Logic Narrative
When the process 'Hold Takes Precedence?' is invoked, and assuming that hold conditions are present along with other status conditions, when the system evaluates precedence according to regulatory hierarchy, the desired outcome is that the system determines if hold conditions take absolute precedence over release, proceed, arrival, or export conditions.
💻 Technical Criteria
Given Hold conditions are present along with other status conditions
When The system evaluates precedence according to regulatory hierarchy
Then The system determines if hold conditions take absolute precedence over release, proceed, arrival, or export conditions
R-GCX016E-cbl-03273 Export Status Valid?
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Export Status Valid?', assuming that export conditions are present and higher precedence conditions do not apply, when the system validates export status legitimacy, the desired outcome is that the system determines if export conditions meet all requirements and can be applied as final status.
💻 Technical Criteria
EXCLUDING Export conditions are present and higher precedence conditions do not apply
When The system validates export status legitimacy
Then The system determines if export conditions meet all requirements and can be applied as final status
R-GCX016E-cbl-03400 Apply Hold Code Hierarchy
Policy Rules
📊 Business Logic Narrative
When the process 'Apply Hold Code Hierarchy' is invoked, and assuming that a disposition code is classified as a hold code type, when regulatory hierarchy processing is applied, the desired outcome is that the system applies hold-specific precedence rules including border holds, destination holds, and fda holds with appropriate priority ordering.
💻 Technical Criteria
Given A disposition code is classified as a Hold Code type
When Regulatory hierarchy processing is applied
Then The system applies hold-specific precedence rules including border holds, destination holds, and FDA holds with appropriate priority ordering
R-GCX016E-cbl-03406 Apply Regulatory Precedence Rules
Policy Rules
📊 Business Logic Narrative
When the process 'Apply Regulatory Precedence Rules' is invoked, and assuming that counterpart codes are identified and regulatory precedence must be determined, when the system applies regulatory precedence logic, the desired outcome is that the system determines which codes have higher priority based on customs regulations, fda requirements, and business policy hierarchy.
💻 Technical Criteria
Given Counterpart codes are identified and regulatory precedence must be determined
When The system applies regulatory precedence logic
Then The system determines which codes have higher priority based on customs regulations, FDA requirements, and business policy hierarchy
R-GCX016E-cbl-03411 Regulatory Compliance Check
Policy Rules
📊 Business Logic Narrative
When the process 'Regulatory Compliance Check' is invoked, and assuming that final disposition code combination is validated, when regulatory compliance verification is performed, the desired outcome is that the system determines if the combination is compliant with customs regulations, fda requirements, and other applicable regulatory standards.
💻 Technical Criteria
Given Final disposition code combination is validated
When Regulatory compliance verification is performed
Then The system determines if the combination is compliant with customs regulations, FDA requirements, and other applicable regulatory standards
R-GCX016E-cbl-03523 Validate Regulatory Compliance
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Regulatory Compliance' is invoked, and assuming that precedence rules have been applied to disposition codes, when the system validates regulatory compliance, the desired outcome is that the system confirms that the resulting code combination meets all customs regulatory requirements.
💻 Technical Criteria
Given Precedence rules have been applied to disposition codes
When The system validates regulatory compliance
Then The system confirms that the resulting code combination meets all customs regulatory requirements
R-GCX016E-cbl-00886 Route to Merlin Message Distribution
Action Rules
📊 Business Logic Narrative
When the process 'Route to Merlin Message Distribution' is invoked, and assuming that cancel release notification is formatted and classified as unrlse type, when message routing is initiated, the desired outcome is that the system routes notification to merlin message distribution system.
💻 Technical Criteria
Given Cancel release notification is formatted and classified as UNRLSE type
When Message routing is initiated
Then The system routes notification to Merlin message distribution system
R-GCX016E-cbl-00887 Send to Business Recipients
Action Rules
📊 Business Logic Narrative
When the process 'Send to Business Recipients' is invoked, and assuming that cancel release notification is routed through merlin distribution, when recipient delivery is processed, the desired outcome is that the system sends notification to om01247 and sd segment cancel merlin ids.
💻 Technical Criteria
Given Cancel release notification is routed through Merlin distribution
When Recipient delivery is processed
Then The system sends notification to OM01247 and SD segment cancel Merlin IDs
R-GCX016E-cbl-00905 Trigger Status Updates
Action Rules
📊 Business Logic Narrative
When the process 'Trigger Status Updates' is invoked, and assuming that destination index management has been completed, when dependent status updates are required, the desired outcome is that all related status update processes are triggered.
💻 Technical Criteria
Given Destination index management has been completed
When Dependent status updates are required
Then All related status update processes are triggered
R-GCX016E-cbl-00984 Send Export Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send Export Notification' is invoked, and assuming that a routed export notification message with identified recipients, when the system sends the export notification, the desired outcome is that the system delivers the export notification message to all identified recipients.
💻 Technical Criteria
Given A routed export notification message with identified recipients
When The system sends the export notification
Then The system delivers the export notification message to all identified recipients
R-GCX016E-cbl-00985 Delivery Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Delivery Successful?' is invoked, and assuming that an export notification that has been sent to recipients, when the system checks delivery status, the desired outcome is that the system determines if the export notification was successfully delivered to all recipients.
💻 Technical Criteria
Given An export notification that has been sent to recipients
When The system checks delivery status
Then The system determines if the export notification was successfully delivered to all recipients
R-GCX016E-cbl-00986 Log Export Notification Sent
Process Rules
📊 Business Logic Narrative
When the process 'Log Export Notification Sent' is invoked, and assuming that an export notification that was successfully delivered to all recipients, when the system logs the successful delivery, the desired outcome is that the system records export notification delivery success with timestamp and recipient information.
💻 Technical Criteria
Given An export notification that was successfully delivered to all recipients
When The system logs the successful delivery
Then The system records export notification delivery success with timestamp and recipient information
R-GCX016E-cbl-00987 Handle Delivery Failure
Action Rules
📊 Business Logic Narrative
When the process 'Handle Delivery Failure' is invoked, and assuming that an export notification that failed delivery to one or more recipients, when the system handles the delivery failure, the desired outcome is that the system initiates failure handling procedures and prepares for alternative delivery methods.
💻 Technical Criteria
Given An export notification that failed delivery to one or more recipients
When The system handles the delivery failure
Then The system initiates failure handling procedures and prepares for alternative delivery methods
R-GCX016E-cbl-00988 Reroute to Default Recipients
Action Rules
📊 Business Logic Narrative
When the process 'Reroute to Default Recipients' is invoked, and assuming that an export notification with delivery failure and default recipient configuration, when the system reroutes to default recipients, the desired outcome is that the system sends the export notification to default recipients (om01247 and backup recipients) as fallback delivery.
💻 Technical Criteria
Given An export notification with delivery failure and default recipient configuration
When The system reroutes to default recipients
Then The system sends the export notification to default recipients (OM01247 and backup recipients) as fallback delivery
R-GCX016E-cbl-01002 Include Location Information
Process Rules
📊 Business Logic Narrative
When the process 'Include Location Information' is invoked, and assuming that an arrival notification is being formatted, when the system includes location information, the desired outcome is that the system adds arrival location, destination details, and routing information to the notification message.
💻 Technical Criteria
Given An arrival notification is being formatted
When The system includes location information
Then The system adds arrival location, destination details, and routing information to the notification message
R-GCX016E-cbl-01005 Route to Merlin Distribution
Action Rules
📊 Business Logic Narrative
When the process 'Route to Merlin Distribution' is invoked, and assuming that an arrival notification message is complete and formatted, when the system routes the message for distribution, the desired outcome is that the system sends the notification to the merlin messaging system for distribution to appropriate recipients.
💻 Technical Criteria
Given An arrival notification message is complete and formatted
When The system routes the message for distribution
Then The system sends the notification to the Merlin messaging system for distribution to appropriate recipients
R-GCX016E-cbl-01007 Send to ARRCANL Basket
Action Rules
📊 Business Logic Narrative
When the process 'Send to ARRCANL Basket' is invoked, and assuming that an arrival notification is classified as arrcanl message type, when the system routes the message, the desired outcome is that the system sends the message to the arrcanl basket for specialized arrival cancellation processing.
💻 Technical Criteria
Given An arrival notification is classified as ARRCANL message type
When The system routes the message
Then The system sends the message to the ARRCANL basket for specialized arrival cancellation processing
R-GCX016E-cbl-01008 Send to Default Recipient
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Send to Default Recipient', assuming that an arrival notification is not classified as arrcanl message type, when the system routes the message, the desired outcome is that the system sends the message to default recipients configured for standard arrival notifications.
💻 Technical Criteria
EXCLUDING An arrival notification is not classified as ARRCANL message type
When The system routes the message
Then The system sends the message to default recipients configured for standard arrival notifications
R-GCX016E-cbl-01026 Extract Transport Type from M10
Process Rules
📊 Business Logic Narrative
When the process 'Extract Transport Type from M10' is invoked, and assuming that an m10 input segment is received containing transportation mode information, when the system processes the m10 segment for transport type extraction, the desired outcome is that the transport type is extracted from the designated field position in the m10 segment.
💻 Technical Criteria
Given An M10 input segment is received containing transportation mode information
When The system processes the M10 segment for transport type extraction
Then The transport type is extracted from the designated field position in the M10 segment
R-GCX016E-cbl-01032 Set Default Transport Type
Decision Rules
📊 Business Logic Narrative
When the process 'Set Default Transport Type' is invoked, and assuming that the extracted transport type has failed validation, when the system needs to assign a transport type for processing, the desired outcome is that a default transport type is assigned to ensure processing can continue.
💻 Technical Criteria
Given The extracted transport type has failed validation
When The system needs to assign a transport type for processing
Then A default transport type is assigned to ensure processing can continue
R-GCX016E-cbl-01062 Station Type Required?
Decision Rules
📊 Business Logic Narrative
When the process 'Station Type Required?' is invoked, and assuming that a station data lookup request is initiated, when the system evaluates the station type requirement, the desired outcome is that the system routes to either destination station retrieval or key station retrieval based on the station type needed.
💻 Technical Criteria
Given A station data lookup request is initiated
When The system evaluates the station type requirement
Then The system routes to either destination station retrieval or key station retrieval based on the station type needed
R-GCX016E-cbl-01063 Retrieve Destination Station Data
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Destination Station Data' is invoked, and assuming that a destination station lookup is required, when the system processes the destination station request, the desired outcome is that the system initiates retrieval of destination station data from the ds table.
💻 Technical Criteria
Given A destination station lookup is required
When The system processes the destination station request
Then The system initiates retrieval of destination station data from the DS table
R-GCX016E-cbl-01066 Access DS Table via GCCTBIO
Action Rules
📊 Business Logic Narrative
When the process 'Access DS Table via GCCTBIO' is invoked, and assuming that destination station data is required, when the system executes table access through gcctbio, the desired outcome is that the system retrieves data from the ds table containing destination station information.
💻 Technical Criteria
Given Destination station data is required
When The system executes table access through GCCTBIO
Then The system retrieves data from the DS table containing destination station information
R-GCX016E-cbl-01068 Station Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Station Found?' is invoked, and assuming that a station lookup has been performed on either ds or ks table, when the system evaluates the lookup results, the desired outcome is that the system determines if the station was found and routes processing accordingly.
💻 Technical Criteria
Given A station lookup has been performed on either DS or KS table
When The system evaluates the lookup results
Then The system determines if the station was found and routes processing accordingly
R-GCX016E-cbl-01070 Validate Location Identifiers
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Location Identifiers' is invoked, and assuming that station information has been extracted from the table, when the system validates the location identifiers, the desired outcome is that the system ensures location identifiers meet required format and business rules.
💻 Technical Criteria
Given Station information has been extracted from the table
When The system validates the location identifiers
Then The system ensures location identifiers meet required format and business rules
R-GCX016E-cbl-01076 Location Identifier Present?
Validation Rules
📊 Business Logic Narrative
When the process 'Location Identifier Present?' is invoked, and assuming that a location identifier has been extracted from the x4 segment, when the system checks for the presence of the location identifier, the desired outcome is that if location identifier is present, proceed with station lookup, otherwise generate station not found error.
💻 Technical Criteria
Given A location identifier has been extracted from the X4 segment
When The system checks for the presence of the location identifier
Then If location identifier is present, proceed with station lookup, otherwise generate station not found error
R-GCX016E-cbl-01077 Set DS Table Type for Lookup
Process Rules
📊 Business Logic Narrative
When the process 'Set DS Table Type for Lookup' is invoked, and assuming that a valid location identifier exists for station lookup, when the system prepares to access the destination station table, the desired outcome is that the ds table type is set for the generic table interface lookup.
💻 Technical Criteria
Given A valid location identifier exists for station lookup
When The system prepares to access the destination station table
Then The DS table type is set for the generic table interface lookup
R-GCX016E-cbl-01080 Retrieve Destination Station Information
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Destination Station Information' is invoked, and assuming that a station record has been found in the destination station table, when the system accesses the station record, the desired outcome is that the destination station information is retrieved from the table segments.
💻 Technical Criteria
Given A station record has been found in the destination station table
When The system accesses the station record
Then The destination station information is retrieved from the table segments
R-GCX016E-cbl-01081 Extract Station Name and Routing Data
Process Rules
📊 Business Logic Narrative
When the process 'Extract Station Name and Routing Data' is invoked, and assuming that destination station information has been retrieved, when the system processes the station record data, the desired outcome is that the station name and routing data are extracted from the station information.
💻 Technical Criteria
Given Destination station information has been retrieved
When The system processes the station record data
Then The station name and routing data are extracted from the station information
R-GCX016E-cbl-01088 Extract Location Identifier from X4 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Location Identifier from X4 Segment' is invoked, and assuming that an x4 segment containing disposition code information is being processed, when the system needs to validate the location identifier for station lookup, the desired outcome is that the location identifier is extracted from the x4 segment and prepared for key station table lookup.
💻 Technical Criteria
Given An X4 segment containing disposition code information is being processed
When The system needs to validate the location identifier for station lookup
Then The location identifier is extracted from the X4 segment and prepared for key station table lookup
R-GCX016E-cbl-01089 Call Generic Table I/O Interface
Action Rules
📊 Business Logic Narrative
When the process 'Call Generic Table I/O Interface' is invoked, and assuming that a location identifier has been extracted from the x4 segment, when the system needs to access key station information, the desired outcome is that the generic table i/o interface is called to access the ks table via gcctbio.
💻 Technical Criteria
Given A location identifier has been extracted from the X4 segment
When The system needs to access key station information
Then The generic table I/O interface is called to access the KS table via GCCTBIO
R-GCX016E-cbl-01090 Access KS Table via GCCTBIO
Action Rules
📊 Business Logic Narrative
When the process 'Access KS Table via GCCTBIO' is invoked, and assuming that the generic table i/o interface has been called with a location identifier, when the system accesses the ks table through gcctbio, the desired outcome is that key station information is retrieved from the ks table for the specified location identifier.
💻 Technical Criteria
Given The generic table I/O interface has been called with a location identifier
When The system accesses the KS table through GCCTBIO
Then Key station information is retrieved from the KS table for the specified location identifier
R-GCX016E-cbl-01091 Key Station Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Key Station Found?' is invoked, and assuming that a key station lookup has been performed using a location identifier, when the system checks the lookup results, the desired outcome is that the system determines if the key station exists and branches processing accordingly.
💻 Technical Criteria
Given A key station lookup has been performed using a location identifier
When The system checks the lookup results
Then The system determines if the key station exists and branches processing accordingly
R-GCX016E-cbl-01092 Retrieve Key Station Information
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Key Station Information' is invoked, and assuming that a key station exists in the ks table for the specified location identifier, when the system processes the found station record, the desired outcome is that key station information is retrieved and made available for further processing.
💻 Technical Criteria
Given A key station exists in the KS table for the specified location identifier
When The system processes the found station record
Then Key station information is retrieved and made available for further processing
R-GCX016E-cbl-01093 Validate Location Identifier
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Location Identifier' is invoked, and assuming that key station information has been retrieved from the ks table, when the system validates the location identifier for business rules compliance, the desired outcome is that the location identifier is validated against business requirements and processing rules.
💻 Technical Criteria
Given Key station information has been retrieved from the KS table
When The system validates the location identifier for business rules compliance
Then The location identifier is validated against business requirements and processing rules
R-GCX016E-cbl-01094 Set Station Data for Processing
Process Rules
📊 Business Logic Narrative
When the process 'Set Station Data for Processing' is invoked, and assuming that the location identifier has been validated successfully, when the system prepares station data for processing, the desired outcome is that station data is set and formatted for use in subsequent business operations.
💻 Technical Criteria
Given The location identifier has been validated successfully
When The system prepares station data for processing
Then Station data is set and formatted for use in subsequent business operations
R-GCX016E-cbl-01095 Generate Station Not Found Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Station Not Found Error', assuming that a key station lookup has been performed for a location identifier, when the key station is not found in the ks table, the desired outcome is that a station not found error is generated and processing continues with error handling.
💻 Technical Criteria
EXCLUDING A key station lookup has been performed for a location identifier
When The key station is not found in the KS table
Then A station not found error is generated and processing continues with error handling
R-GCX016E-cbl-01097 Table Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Table Type?' is invoked, and assuming that a table lookup request is initiated with specific table type parameters, when the system evaluates the table type identifier, the desired outcome is that the system routes the request to the appropriate table processing logic (ds for station data, ks for key station data, dc for disposition codes, or broker table for broker information).
💻 Technical Criteria
Given A table lookup request is initiated with specific table type parameters
When The system evaluates the table type identifier
Then The system routes the request to the appropriate table processing logic (DS for station data, KS for key station data, DC for disposition codes, or broker table for broker information)
R-GCX016E-cbl-01098 Station Data Lookup - DS Table
Process Rules
📊 Business Logic Narrative
When the process 'Station Data Lookup - DS Table' is invoked, and assuming that a request for station data lookup is received with a valid station code, when the system accesses the ds table in gcstbrt, the desired outcome is that the system retrieves the corresponding station information including station name and location details.
💻 Technical Criteria
Given A request for station data lookup is received with a valid station code
When The system accesses the DS table in GCSTBRT
Then The system retrieves the corresponding station information including station name and location details
R-GCX016E-cbl-01102 Call GCCTBIO Interface
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCTBIO Interface' is invoked, and assuming that a table lookup request has been routed to the appropriate table type, when the system needs to perform the actual table access operation, the desired outcome is that the system calls the gcctbio interface with the table type and key parameters.
💻 Technical Criteria
Given A table lookup request has been routed to the appropriate table type
When The system needs to perform the actual table access operation
Then The system calls the GCCTBIO interface with the table type and key parameters
R-GCX016E-cbl-03034 Quantity Impact Analysis
Decision Rules
📊 Business Logic Narrative
When the process 'Quantity Impact Analysis' is invoked, and assuming that release quantity impact has been calculated, when the system evaluates quantity impact, the desired outcome is that processing is routed to show quantity details if impact is detected, otherwise continues to comment processing.
💻 Technical Criteria
Given Release quantity impact has been calculated
When The system evaluates quantity impact
Then Processing is routed to show quantity details if impact is detected, otherwise continues to comment processing
R-GCX016E-cbl-01142 Format Disposition Code Description
Process Rules
📊 Business Logic Narrative
When the process 'Format Disposition Code Description' is invoked, and assuming that disposition code information and description from dc table, when impact message formatting is performed, the desired outcome is that the disposition code description is formatted for inclusion in the impact report.
💻 Technical Criteria
Given Disposition code information and description from DC table
When Impact message formatting is performed
Then The disposition code description is formatted for inclusion in the impact report
R-GCX016E-cbl-01146 Format Complete Release Impact Report
Process Rules
📊 Business Logic Narrative
When the process 'Format Complete Release Impact Report' is invoked, and assuming that all impact message components including quantities, descriptions, and comments, when final report formatting is performed, the desired outcome is that the system creates a complete formatted release impact report ready for distribution.
💻 Technical Criteria
Given All impact message components including quantities, descriptions, and comments
When Final report formatting is performed
Then The system creates a complete formatted release impact report ready for distribution
R-GCX016E-cbl-01174 Freight Forwarder Identified?
Decision Rules
📊 Business Logic Narrative
When the process 'Freight Forwarder Identified?' is invoked, and assuming that freight forwarder data validation has been completed, when the system evaluates if a freight forwarder has been successfully identified, the desired outcome is that the system determines the freight forwarder identification status and routes processing accordingly.
💻 Technical Criteria
Given Freight forwarder data validation has been completed
When The system evaluates if a freight forwarder has been successfully identified
Then The system determines the freight forwarder identification status and routes processing accordingly
R-GCX016E-cbl-01218 Include Origin/Destination Stations
Process Rules
📊 Business Logic Narrative
When the process 'Include Origin/Destination Stations' is invoked, and assuming that content description has been included in the email content, when the system processes origin and destination station data, the desired outcome is that the system includes origin and destination station names and codes in the email notification.
💻 Technical Criteria
Given Content description has been included in the email content
When The system processes origin and destination station data
Then The system includes origin and destination station names and codes in the email notification
R-GCX016E-cbl-01219 Include CIH Disposition Information
Process Rules
📊 Business Logic Narrative
When the process 'Include CIH Disposition Information' is invoked, and assuming that origin and destination station information has been included in the email content, when the system processes cih disposition information, the desired outcome is that the system includes cih disposition code details, hold reasons, and related customs information in the email notification.
💻 Technical Criteria
Given Origin and destination station information has been included in the email content
When The system processes CIH disposition information
Then The system includes CIH disposition code details, hold reasons, and related customs information in the email notification
R-GCX016E-cbl-01225 Retry Limit Reached?
Validation Rules
📊 Business Logic Narrative
When the process 'Retry Limit Reached?' is invoked, and assuming that email delivery retry has been attempted, when the system checks the retry attempt count against the maximum limit, the desired outcome is that if retry limit has not been reached, attempt delivery again, otherwise log delivery failure and route to error handler.
💻 Technical Criteria
Given Email delivery retry has been attempted
When The system checks the retry attempt count against the maximum limit
Then If retry limit has not been reached, attempt delivery again, otherwise log delivery failure and route to error handler
R-GCX016E-cbl-01227 Route to Error Handler
Action Rules
📊 Business Logic Narrative
When the process 'Route to Error Handler' is invoked, and assuming that email delivery has failed after maximum retry attempts, when the system routes to error handling, the desired outcome is that the system invokes error handler to process alternative notification methods such as routing to backup recipients (aei9999, om01247).
💻 Technical Criteria
Given Email delivery has failed after maximum retry attempts
When The system routes to error handling
Then The system invokes error handler to process alternative notification methods such as routing to backup recipients (AEI9999, OM01247)
R-GCX016E-cbl-03293 Valid Broker Relationship?
Decision Rules
📊 Business Logic Narrative
When the process 'Valid Broker Relationship?' is invoked, and assuming that broker relationship validation has been completed, when the system evaluates the validation results, the desired outcome is that the system determines if the broker relationship is valid and routes processing accordingly.
💻 Technical Criteria
Given Broker relationship validation has been completed
When The system evaluates the validation results
Then The system determines if the broker relationship is valid and routes processing accordingly
R-GCX016E-cbl-03071 Format Station Names and Codes
Process Rules
📊 Business Logic Narrative
When the process 'Format Station Names and Codes' is invoked, and assuming that origin and destination station information has been retrieved, when the system formats station information for display, the desired outcome is that station names and codes are formatted according to business display standards.
💻 Technical Criteria
Given Origin and destination station information has been retrieved
When The system formats station information for display
Then Station names and codes are formatted according to business display standards
R-GCX016E-cbl-01229 Validate Email Recipients
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Email Recipients' is invoked, and assuming that an email distribution request is received with recipient information, when the system validates the email recipients, the desired outcome is that the system determines if recipients are valid based on configuration and proceeds with email preparation or routes to default recipient.
💻 Technical Criteria
Given An email distribution request is received with recipient information
When The system validates the email recipients
Then The system determines if recipients are valid based on configuration and proceeds with email preparation or routes to default recipient
R-GCX016E-cbl-01236 Route to Default Recipient
Action Rules
📊 Business Logic Narrative
When the process 'Route to Default Recipient' is invoked, and assuming that email delivery has failed completely or recipients are invalid, when the system routes to default recipient, the desired outcome is that the system sends the email to configured default recipient as fallback delivery method.
💻 Technical Criteria
Given Email delivery has failed completely or recipients are invalid
When The system routes to default recipient
Then The system sends the email to configured default recipient as fallback delivery method
R-GCX016E-cbl-01237 Generate Error Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Error Notification' is invoked, and assuming that email has been routed to default recipient due to delivery failure or invalid recipients, when the system generates error notification, the desired outcome is that the system creates error notification message indicating the delivery issue and fallback action taken.
💻 Technical Criteria
Given Email has been routed to default recipient due to delivery failure or invalid recipients
When The system generates error notification
Then The system creates error notification message indicating the delivery issue and fallback action taken
R-GCX016E-cbl-01250 Route Debug Message to Recipients
Action Rules
📊 Business Logic Narrative
When the process 'Route Debug Message to Recipients' is invoked, and assuming that debug message has been formatted with all required information, when debug message routing is initiated, the desired outcome is that the system routes the debug message to appropriate recipients for review.
💻 Technical Criteria
Given Debug message has been formatted with all required information
When Debug message routing is initiated
Then The system routes the debug message to appropriate recipients for review
R-GCX016E-cbl-01252 Route ERROR Message
Decision Rules
📊 Business Logic Narrative
When the process 'Route ERROR Message' is invoked, and assuming that a merlin message has been generated, when the message type is error, the desired outcome is that the message should be routed to the in destination.
💻 Technical Criteria
Given A Merlin message has been generated
When The message type is ERROR
Then The message should be routed to the IN destination
R-GCX016E-cbl-01253 Route INFO Message
Decision Rules
📊 Business Logic Narrative
When the process 'Route INFO Message' is invoked, and assuming that a merlin message has been generated with sd segment recipient information, when the message type is info, the desired outcome is that the message should be routed to the in destination and all sd segment merlin ids.
💻 Technical Criteria
Given A Merlin message has been generated with SD segment recipient information
When The message type is INFO
Then The message should be routed to the IN destination and all SD segment Merlin IDs
R-GCX016E-cbl-01254 Route RELEASE Message
Decision Rules
📊 Business Logic Narrative
When the process 'Route RELEASE Message' is invoked, and assuming that a merlin message has been generated with sd segment recipient information, when the message type is release, the desired outcome is that the message should be routed only to sd segment merlin ids.
💻 Technical Criteria
Given A Merlin message has been generated with SD segment recipient information
When The message type is RELEASE
Then The message should be routed only to SD segment Merlin IDs
R-GCX016E-cbl-01256 Route UNRLSE Message
Decision Rules
📊 Business Logic Narrative
When the process 'Route UNRLSE Message' is invoked, and assuming that a merlin message has been generated with sd segment cancel recipient information, when the message type is unrlse, the desired outcome is that the message should be routed to om01247 and all sd segment cancel merlin ids.
💻 Technical Criteria
Given A Merlin message has been generated with SD segment cancel recipient information
When The message type is UNRLSE
Then The message should be routed to OM01247 and all SD segment cancel Merlin IDs
R-GCX016E-cbl-01257 Route ARRCANL Message
Decision Rules
📊 Business Logic Narrative
When the process 'Route ARRCANL Message' is invoked, and assuming that a merlin message has been generated for arrival cancellation, when the message type is arrcanl, the desired outcome is that the message should be routed to configured arrival cancellation recipients.
💻 Technical Criteria
Given A Merlin message has been generated for arrival cancellation
When The message type is ARRCANL
Then The message should be routed to configured arrival cancellation recipients
R-GCX016E-cbl-01264 Reroute to Default Recipient
Action Rules
📊 Business Logic Narrative
When the process 'Reroute to Default Recipient' is invoked, and assuming that a message delivery has failed and an error notification has been generated, when rerouting is attempted, the desired outcome is that the message should be rerouted to the default recipient.
💻 Technical Criteria
Given A message delivery has failed and an error notification has been generated
When Rerouting is attempted
Then The message should be rerouted to the default recipient
R-GCX016E-cbl-01266 Message Type Classification
Decision Rules
📊 Business Logic Narrative
When the process 'Message Type Classification' is invoked, and assuming that a merlin message is ready for distribution, when the system evaluates the message type indicator, the desired outcome is that the message is classified as error, info, release, export, unrlse, or arrcanl type for routing purposes.
💻 Technical Criteria
Given A Merlin message is ready for distribution
When The system evaluates the message type indicator
Then The message is classified as ERROR, INFO, RELEASE, EXPORT, UNRLSE, or ARRCANL type for routing purposes
R-GCX016E-cbl-01267 Route ERROR Messages
Process Rules
📊 Business Logic Narrative
When the process 'Route ERROR Messages' is invoked, and assuming that a message has been classified as error type, when the routing process begins, the desired outcome is that the message is directed to the 'in' destination queue.
💻 Technical Criteria
Given A message has been classified as ERROR type
When The routing process begins
Then The message is directed to the 'IN' destination queue
R-GCX016E-cbl-01268 Route INFO Messages
Process Rules
📊 Business Logic Narrative
When the process 'Route INFO Messages' is invoked, and assuming that a message has been classified as info type, when the routing process begins, the desired outcome is that the message is sent to 'in' destination and all configured sd segment merlin ids.
💻 Technical Criteria
Given A message has been classified as INFO type
When The routing process begins
Then The message is sent to 'IN' destination and all configured SD segment Merlin IDs
R-GCX016E-cbl-01269 Route RELEASE Messages
Process Rules
📊 Business Logic Narrative
When the process 'Route RELEASE Messages' is invoked, and assuming that a message has been classified as release type, when the routing process begins, the desired outcome is that the message is sent only to configured sd segment merlin ids.
💻 Technical Criteria
Given A message has been classified as RELEASE type
When The routing process begins
Then The message is sent only to configured SD segment Merlin IDs
R-GCX016E-cbl-01271 Route UNRLSE Messages
Process Rules
📊 Business Logic Narrative
When the process 'Route UNRLSE Messages' is invoked, and assuming that a message has been classified as unrlse type, when the routing process begins, the desired outcome is that the message is sent to om01247 and all configured sd cancel merlin ids.
💻 Technical Criteria
Given A message has been classified as UNRLSE type
When The routing process begins
Then The message is sent to OM01247 and all configured SD cancel Merlin IDs
R-GCX016E-cbl-01272 Route ARRCANL Messages
Process Rules
📊 Business Logic Narrative
When the process 'Route ARRCANL Messages' is invoked, and assuming that a message has been classified as arrcanl type, when the routing process begins, the desired outcome is that the message is routed according to arrival cancellation notification rules.
💻 Technical Criteria
Given A message has been classified as ARRCANL type
When The routing process begins
Then The message is routed according to arrival cancellation notification rules
R-GCX016E-cbl-01273 Determine Message Recipient
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Message Recipient' is invoked, and assuming that a message has been classified and routing rules applied, when the system looks up recipient configuration, the desired outcome is that the appropriate recipient merlin id or destination is identified.
💻 Technical Criteria
Given A message has been classified and routing rules applied
When The system looks up recipient configuration
Then The appropriate recipient Merlin ID or destination is identified
R-GCX016E-cbl-01280 Initiate Rerouting Process
Process Rules
📊 Business Logic Narrative
When the process 'Initiate Rerouting Process' is invoked, and assuming that a message delivery has failed, when the rerouting process is triggered, the desired outcome is that alternative delivery routes are identified and activated.
💻 Technical Criteria
Given A message delivery has failed
When The rerouting process is triggered
Then Alternative delivery routes are identified and activated
R-GCX016E-cbl-01289 Open GC350.EXP.INPUT Queue
Action Rules
📊 Business Logic Narrative
When the process 'Open GC350.EXP.INPUT Queue' is invoked, and assuming that mq manager connection is successfully established, when system attempts to open gc350.exp.input queue, the desired outcome is that the export input queue is opened for message processing.
💻 Technical Criteria
Given MQ Manager connection is successfully established
When System attempts to open GC350.EXP.INPUT queue
Then The export input queue is opened for message processing
R-GCX016E-cbl-01297 MQ Connection Ready for Processing
Process Rules
📊 Business Logic Narrative
When the process 'MQ Connection Ready for Processing' is invoked, and assuming that connection success has been logged, when all mq setup operations are complete, the desired outcome is that mq connection is confirmed ready for processing export messages from gc350.exp.input queue.
💻 Technical Criteria
Given Connection success has been logged
When All MQ setup operations are complete
Then MQ connection is confirmed ready for processing export messages from GC350.EXP.INPUT queue
R-GCX016E-cbl-01310 Create M10 Segment Structure
Definitional Rules
📊 Business Logic Narrative
When the process 'Create M10 Segment Structure' is invoked, and assuming that train message arrays are being initialized, when the system creates m10 segment structure, the desired outcome is that the system defines fields for vessel name, train identification, and transport details.
💻 Technical Criteria
Given Train message arrays are being initialized
When The system creates M10 segment structure
Then The system defines fields for vessel name, train identification, and transport details
R-GCX016E-cbl-01312 Set SCAC and Transport Type
Process Rules
📊 Business Logic Narrative
When the process 'Set SCAC and Transport Type' is invoked, and assuming that vessel/train information has been set in the m10 segment, when the system sets scac and transport type, the desired outcome is that the system populates scac code and transport mode information in the m10 segment.
💻 Technical Criteria
Given Vessel/train information has been set in the M10 segment
When The system sets SCAC and transport type
Then The system populates SCAC code and transport mode information in the M10 segment
R-GCX016E-cbl-01313 Set Country Code Details
Process Rules
📊 Business Logic Narrative
When the process 'Set Country Code Details' is invoked, and assuming that scac and transport type have been set in the m10 segment, when the system sets country code details, the desired outcome is that the system assigns origin country code and destination country code to the m10 segment.
💻 Technical Criteria
Given SCAC and transport type have been set in the M10 segment
When The system sets country code details
Then The system assigns origin country code and destination country code to the M10 segment
R-GCX016E-cbl-01314 Create V9 Segment Structure
Definitional Rules
📊 Business Logic Narrative
When the process 'Create V9 Segment Structure' is invoked, and assuming that m10 segment has been completed with country code details, when the system creates v9 segment structure, the desired outcome is that the system defines fields for event codes, status information, and location data.
💻 Technical Criteria
Given M10 segment has been completed with country code details
When The system creates V9 segment structure
Then The system defines fields for event codes, status information, and location data
R-GCX016E-cbl-01317 Set Location Data
Process Rules
📊 Business Logic Narrative
When the process 'Set Location Data' is invoked, and assuming that disposition code has been set in the v9 segment, when the system sets location data, the desired outcome is that the system assigns location code, location name, and geographic coordinates to the v9 segment.
💻 Technical Criteria
Given Disposition code has been set in the V9 segment
When The system sets location data
Then The system assigns location code, location name, and geographic coordinates to the V9 segment
R-GCX016E-cbl-01337 Format Disposition Code Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Disposition Code Information' is invoked, and assuming that a disposition code exists for processing, when disposition code information formatting is performed, the desired outcome is that disposition code details are formatted for the report.
💻 Technical Criteria
Given A disposition code exists for processing
When Disposition code information formatting is performed
Then Disposition code details are formatted for the report
R-GCX016E-cbl-01340 Format Date/Time Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Date/Time Information' is invoked, and assuming that system processing times are available, when date/time information formatting is performed, the desired outcome is that date and time information is formatted for the report.
💻 Technical Criteria
Given System processing times are available
When Date/time information formatting is performed
Then Date and time information is formatted for the report
R-GCX016E-cbl-01341 Format USCS Processing Time
Computation Rules
📊 Business Logic Narrative
When the process 'Format USCS Processing Time' is invoked, and assuming that uscs processing time information is available, when uscs processing time formatting is performed, the desired outcome is that uscs processing time is formatted for the report.
💻 Technical Criteria
Given USCS processing time information is available
When USCS processing time formatting is performed
Then USCS processing time is formatted for the report
R-GCX016E-cbl-01342 Format System Processing Time
Computation Rules
📊 Business Logic Narrative
When the process 'Format System Processing Time' is invoked, and assuming that system processing time information is available, when system processing time formatting is performed, the desired outcome is that system processing time is formatted for the report.
💻 Technical Criteria
Given System processing time information is available
When System processing time formatting is performed
Then System processing time is formatted for the report
R-GCX016E-cbl-01345 Include Quantity Impact in Report
Process Rules
📊 Business Logic Narrative
When the process 'Include Quantity Impact in Report' is invoked, and assuming that a disposition code affects release quantities, when report formatting includes quantity impact processing, the desired outcome is that quantity impact information is included in the report.
💻 Technical Criteria
Given A disposition code affects release quantities
When Report formatting includes quantity impact processing
Then Quantity impact information is included in the report
R-GCX016E-cbl-01346 Exclude Quantity Impact from Report
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Exclude Quantity Impact from Report', assuming that a disposition code does not affect release quantities, when report formatting excludes quantity impact processing, the desired outcome is that quantity impact information is excluded from the report.
💻 Technical Criteria
EXCLUDING A disposition code does not affect release quantities
When Report formatting excludes quantity impact processing
Then Quantity impact information is excluded from the report
R-GCX016E-cbl-01347 Combine All Formatted Elements
Process Rules
📊 Business Logic Narrative
When the process 'Combine All Formatted Elements' is invoked, and assuming that all report elements have been individually formatted, when element combination is performed, the desired outcome is that all formatted elements are combined into a unified report structure.
💻 Technical Criteria
Given All report elements have been individually formatted
When Element combination is performed
Then All formatted elements are combined into a unified report structure
R-GCX016E-cbl-01348 Generate Final Merlin Report Format
Process Rules
📊 Business Logic Narrative
When the process 'Generate Final Merlin Report Format' is invoked, and assuming that all report elements have been combined, when final report generation is performed, the desired outcome is that a complete formatted merlin report is generated.
💻 Technical Criteria
Given All report elements have been combined
When Final report generation is performed
Then A complete formatted Merlin report is generated
R-GCX016E-cbl-01354 Action Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Action Type?' is invoked, and assuming that a disposition code has a defined action type, when the system evaluates the action type for quantity impact, the desired outcome is that the system routes to add, subtract, or no quantity impact processing based on the action type.
💻 Technical Criteria
Given A disposition code has a defined action type
When The system evaluates the action type for quantity impact
Then The system routes to Add, Subtract, or No Quantity Impact processing based on the action type
R-GCX016E-cbl-01384 Retrieve Location Identifiers
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Location Identifiers' is invoked, and assuming that entry numbers have been successfully retrieved for the shipment, when the system processes location information, the desired outcome is that the system should retrieve all relevant location identifiers for the shipment.
💻 Technical Criteria
Given Entry numbers have been successfully retrieved for the shipment
When The system processes location information
Then The system should retrieve all relevant location identifiers for the shipment
R-GCX016E-cbl-01385 Process Destination Station Information from X4 Segments
Process Rules
📊 Business Logic Narrative
When the process 'Process Destination Station Information from X4 Segments' is invoked, and assuming that location identifiers have been retrieved and x4 segments are available, when the system processes destination station information, the desired outcome is that the system should extract destination station data from x4 segments and validate the information.
💻 Technical Criteria
Given Location identifiers have been retrieved and X4 segments are available
When The system processes destination station information
Then The system should extract destination station data from X4 segments and validate the information
R-GCX016E-cbl-01386 Process Key Station Information
Process Rules
📊 Business Logic Narrative
When the process 'Process Key Station Information' is invoked, and assuming that destination station information has been processed from x4 segments, when the system processes key station information, the desired outcome is that the system should identify and validate key station data for shipment routing.
💻 Technical Criteria
Given Destination station information has been processed from X4 segments
When The system processes key station information
Then The system should identify and validate key station data for shipment routing
R-GCX016E-cbl-01390 Populate Location Identifiers in U1
Process Rules
📊 Business Logic Narrative
When the process 'Populate Location Identifiers in U1' is invoked, and assuming that entry numbers have been populated in the u1 segment and location identifiers are available, when the system populates location information, the desired outcome is that the system should insert all location identifiers into the appropriate fields of the u1 segment.
💻 Technical Criteria
Given Entry numbers have been populated in the U1 segment and location identifiers are available
When The system populates location information
Then The system should insert all location identifiers into the appropriate fields of the U1 segment
R-GCX016E-cbl-01394 Extract Destination Station Code
Process Rules
📊 Business Logic Narrative
When the process 'Extract Destination Station Code' is invoked, and assuming that an x4 segment has been received for processing, when the system processes the x4 segment, the desired outcome is that the destination station code is extracted from the segment data.
💻 Technical Criteria
Given An X4 segment has been received for processing
When The system processes the X4 segment
Then The destination station code is extracted from the segment data
R-GCX016E-cbl-01395 Station Code Present?
Validation Rules
📊 Business Logic Narrative
When the process 'Station Code Present?' is invoked, and assuming that a destination station code has been extracted from x4 segment, when the system validates the extracted station code, the desired outcome is that the system determines if the station code is present or missing.
💻 Technical Criteria
Given A destination station code has been extracted from X4 segment
When The system validates the extracted station code
Then The system determines if the station code is present or missing
R-GCX016E-cbl-01396 Valid Format?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid Format?' is invoked, and assuming that a destination station code is present, when the system validates the station code format, the desired outcome is that the system determines if the format is valid according to business standards.
💻 Technical Criteria
Given A destination station code is present
When The system validates the station code format
Then The system determines if the format is valid according to business standards
R-GCX016E-cbl-01397 Lookup Station in Destination Table
Action Rules
📊 Business Logic Narrative
When the process 'Lookup Station in Destination Table' is invoked, and assuming that a valid format destination station code exists, when the system performs a lookup in the destination station table, the desired outcome is that the system searches for matching station information.
💻 Technical Criteria
Given A valid format destination station code exists
When The system performs a lookup in the destination station table
Then The system searches for matching station information
R-GCX016E-cbl-01398 Station Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Station Found?' is invoked, and assuming that a lookup has been performed in the destination station table, when the system evaluates the lookup results, the desired outcome is that the system determines if the station was found or not found.
💻 Technical Criteria
Given A lookup has been performed in the destination station table
When The system evaluates the lookup results
Then The system determines if the station was found or not found
R-GCX016E-cbl-01399 Retrieve Station Information
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Station Information' is invoked, and assuming that a destination station is found in the reference table, when the system retrieves station data, the desired outcome is that complete station information including name and attributes is retrieved.
💻 Technical Criteria
Given A destination station is found in the reference table
When The system retrieves station data
Then Complete station information including name and attributes is retrieved
R-GCX016E-cbl-01400 Set Destination Station Data
Process Rules
📊 Business Logic Narrative
When the process 'Set Destination Station Data' is invoked, and assuming that complete station information has been retrieved, when the system sets destination station data, the desired outcome is that all relevant destination station fields are populated with the retrieved information.
💻 Technical Criteria
Given Complete station information has been retrieved
When The system sets destination station data
Then All relevant destination station fields are populated with the retrieved information
R-GCX016E-cbl-01403 Set Default Station Information
Process Rules
📊 Business Logic Narrative
When the process 'Set Default Station Information' is invoked, and assuming that no destination station code is present in the x4 segment, when the system processes the missing station code, the desired outcome is that default station information is applied to maintain data integrity.
💻 Technical Criteria
Given No destination station code is present in the X4 segment
When The system processes the missing station code
Then Default station information is applied to maintain data integrity
R-GCX016E-cbl-01404 Log Station Code Missing
Process Rules
📊 Business Logic Narrative
When the process 'Log Station Code Missing' is invoked, and assuming that an x4 segment is processed without a destination station code, when the system detects the missing station code, the desired outcome is that a log entry is created indicating the station code is missing.
💻 Technical Criteria
Given An X4 segment is processed without a destination station code
When The system detects the missing station code
Then A log entry is created indicating the station code is missing
R-GCX016E-cbl-01405 Log Invalid Station Format
Process Rules
📊 Business Logic Narrative
When the process 'Log Invalid Station Format' is invoked, and assuming that a destination station code is present but has invalid format, when the system validates the station code format, the desired outcome is that a log entry is created indicating invalid station format.
💻 Technical Criteria
Given A destination station code is present but has invalid format
When The system validates the station code format
Then A log entry is created indicating invalid station format
R-GCX016E-cbl-01406 Log Station Not Found Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Station Not Found Error', assuming that a valid format destination station code is not found in the reference table, when the system completes the lookup process, the desired outcome is that an error log entry is created indicating the station was not found.
💻 Technical Criteria
EXCLUDING A valid format destination station code is not found in the reference table
When The system completes the lookup process
Then An error log entry is created indicating the station was not found
R-GCX016E-cbl-01407 Continue X4 Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue X4 Processing' is invoked, and assuming that destination station processing is complete (successful or with defaults), when the system finishes station processing, the desired outcome is that processing continues with the next components of the x4 segment.
💻 Technical Criteria
Given Destination station processing is complete (successful or with defaults)
When The system finishes station processing
Then Processing continues with the next components of the X4 segment
R-GCX016E-cbl-01409 Validate Location Identifier Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Location Identifier Format' is invoked, and assuming that a location identifier has been extracted from x4 segment data, when the system validates the location identifier format, the desired outcome is that the location identifier format is confirmed as valid or invalid.
💻 Technical Criteria
Given A location identifier has been extracted from X4 segment data
When The system validates the location identifier format
Then The location identifier format is confirmed as valid or invalid
R-GCX016E-cbl-01410 Location Identifier Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Location Identifier Valid?' is invoked, and assuming that a location identifier has undergone format validation, when the system evaluates the validation results, the desired outcome is that the system proceeds with key station lookup if valid or generates error message if invalid.
💻 Technical Criteria
Given A location identifier has undergone format validation
When The system evaluates the validation results
Then The system proceeds with key station lookup if valid or generates error message if invalid
R-GCX016E-cbl-01411 Retrieve Key Station Information from KS Table
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Key Station Information from KS Table' is invoked, and assuming that a valid location identifier has been confirmed, when the system queries the ks table for key station information, the desired outcome is that the system retrieves matching key station data from the ks table.
💻 Technical Criteria
Given A valid location identifier has been confirmed
When The system queries the KS table for key station information
Then The system retrieves matching key station data from the KS table
R-GCX016E-cbl-01412 Call GCCTBIO for Table Lookup
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCTBIO for Table Lookup' is invoked, and assuming that the system needs to lookup key station information in the ks table, when the system calls gcctbio with the location identifier, the desired outcome is that gcctbio performs the table lookup and returns results.
💻 Technical Criteria
Given The system needs to lookup key station information in the KS table
When The system calls GCCTBIO with the location identifier
Then GCCTBIO performs the table lookup and returns results
R-GCX016E-cbl-01418 Update Location Validation Status
Process Rules
📊 Business Logic Narrative
When the process 'Update Location Validation Status' is invoked, and assuming that key station fields have been successfully set, when the system updates location validation status, the desired outcome is that location validation status indicates successful key station processing.
💻 Technical Criteria
Given Key station fields have been successfully set
When The system updates location validation status
Then Location validation status indicates successful key station processing
R-GCX016E-cbl-01419 Generate Error Message for Invalid Location
Process Rules
📊 Business Logic Narrative
When the process 'Generate Error Message for Invalid Location' is invoked, and assuming that a location identifier has failed format validation, when the system generates an error message, the desired outcome is that an error message is created indicating invalid location identifier.
💻 Technical Criteria
Given A location identifier has failed format validation
When The system generates an error message
Then An error message is created indicating invalid location identifier
R-GCX016E-cbl-01468 Route Error Message to Default Recipient
Action Rules
📊 Business Logic Narrative
When the process 'Route Error Message to Default Recipient' is invoked, and assuming that an error message has been generated for routing, when primary merlin id routing fails or is unavailable, the desired outcome is that route error message to default recipients (om01247, aei9999) with fallback notification.
💻 Technical Criteria
Given An error message has been generated for routing
When Primary Merlin ID routing fails or is unavailable
Then Route error message to default recipients (OM01247, AEI9999) with fallback notification
R-GCX016E-cbl-01552 Train ID ends with 'T'?
Decision Rules
📊 Business Logic Narrative
When the process 'Train ID ends with 'T'?' is invoked, and assuming that a train arrival event (pod/aad disposition) is being processed, when the system evaluates the train id suffix, the desired outcome is that if train id ends with 't', classify as export manifest train, otherwise process as standard import train.
💻 Technical Criteria
Given A train arrival event (POD/AAD disposition) is being processed
When The system evaluates the train ID suffix
Then If train ID ends with 'T', classify as export manifest train, otherwise process as standard import train
R-GCX016E-cbl-01553 Is Port Designated for Export Manifests?
Validation Rules
📊 Business Logic Narrative
When the process 'Is Port Designated for Export Manifests?' is invoked, and assuming that an export manifest train has been identified and arrival port has been extracted from p4 location segment, when the system checks the port against the export port validation table, the desired outcome is that if port is designated for export manifests, proceed with export processing, otherwise generate port validation error.
💻 Technical Criteria
Given An export manifest train has been identified and arrival port has been extracted from P4 location segment
When The system checks the port against the export port validation table
Then If port is designated for export manifests, proceed with export processing, otherwise generate port validation error
R-GCX016E-cbl-01554 Set Export Manifest Pre-Arrival Status
Action Rules
📊 Business Logic Narrative
When the process 'Set Export Manifest Pre-Arrival Status' is invoked, and assuming that an export manifest train has been identified and port validation has been successful, when the system processes the export manifest pre-arrival, the desired outcome is that set the train status to export manifest pre-arrival status.
💻 Technical Criteria
Given An export manifest train has been identified and port validation has been successful
When The system processes the export manifest pre-arrival
Then Set the train status to export manifest pre-arrival status
R-GCX016E-cbl-01555 Update Train Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Status Flags' is invoked, and assuming that export manifest pre-arrival status has been set for a train, when the system updates train status information, the desired outcome is that update train status flags in train records to reflect export manifest pre-arrival state.
💻 Technical Criteria
Given Export manifest pre-arrival status has been set for a train
When The system updates train status information
Then Update train status flags in train records to reflect export manifest pre-arrival state
R-GCX016E-cbl-01556 Log Export Manifest Pre-Arrival Action
Action Rules
📊 Business Logic Narrative
When the process 'Log Export Manifest Pre-Arrival Action' is invoked, and assuming that train status flags have been updated for export manifest pre-arrival, when the system completes export manifest processing, the desired outcome is that log the export manifest pre-arrival action with relevant train and port information.
💻 Technical Criteria
Given Train status flags have been updated for export manifest pre-arrival
When The system completes export manifest processing
Then Log the export manifest pre-arrival action with relevant train and port information
R-GCX016E-cbl-01557 Generate Pre-Arrival Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Pre-Arrival Notification' is invoked, and assuming that export manifest pre-arrival action has been logged, when the system completes export processing workflow, the desired outcome is that generate pre-arrival notification message for the export manifest train.
💻 Technical Criteria
Given Export manifest pre-arrival action has been logged
When The system completes export processing workflow
Then Generate pre-arrival notification message for the export manifest train
R-GCX016E-cbl-01558 Generate Port Validation Error
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Port Validation Error', assuming that an export manifest train has been identified but port validation has failed, when the arrival port is not found in the export port validation table, the desired outcome is that generate port validation error message indicating the port is not authorized for export manifests.
💻 Technical Criteria
EXCLUDING An export manifest train has been identified but port validation has failed
When The arrival port is not found in the export port validation table
Then Generate port validation error message indicating the port is not authorized for export manifests
R-GCX016E-cbl-01559 Route Error to Default Recipient
Action Rules
📊 Business Logic Narrative
When the process 'Route Error to Default Recipient' is invoked, and assuming that a port validation error has been generated for an export manifest train, when the system processes the error routing, the desired outcome is that route the port validation error message to the default error recipient for resolution.
💻 Technical Criteria
Given A port validation error has been generated for an export manifest train
When The system processes the error routing
Then Route the port validation error message to the default error recipient for resolution
R-GCX016E-cbl-01560 Continue with Standard Import Processing
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Continue with Standard Import Processing', assuming that a train arrival event is being processed and train id does not end with 't', when the system determines the train is not an export manifest train, the desired outcome is that continue processing the train using standard import manifest procedures.
💻 Technical Criteria
EXCLUDING A train arrival event is being processed and train ID does not end with 'T'
When The system determines the train is not an export manifest train
Then Continue processing the train using standard import manifest procedures
R-GCX016E-cbl-01561 Train ID has 'T' suffix?
Decision Rules
📊 Business Logic Narrative
When the process 'Train ID has 'T' suffix?' is invoked, and assuming that a train arrival event (pod/aad) is being processed, when the system checks the train id for 't' suffix, the desired outcome is that if train id does not have 't' suffix, classify as import manifest for standard processing.
💻 Technical Criteria
Given A train arrival event (POD/AAD) is being processed
When The system checks the train ID for 'T' suffix
Then If train ID does not have 'T' suffix, classify as import manifest for standard processing
R-GCX016E-cbl-01562 Valid Arrival Date?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid Arrival Date?' is invoked, and assuming that an import manifest train arrival is being processed and arrival date/time is extracted from v9 segment, when the system validates the arrival date format and content, the desired outcome is that if arrival date is valid, use it for train arrival processing, otherwise use system current date/time.
💻 Technical Criteria
Given An import manifest train arrival is being processed and arrival date/time is extracted from V9 segment
When The system validates the arrival date format and content
Then If arrival date is valid, use it for train arrival processing, otherwise use system current date/time
R-GCX016E-cbl-01563 Use System Current Date/Time
Action Rules
📊 Business Logic Narrative
When the process 'Use System Current Date/Time' is invoked, and assuming that an import manifest train arrival is being processed and the v9 segment arrival date is invalid or missing, when the system needs to set train arrival date/time, the desired outcome is that use system current date/time as the train arrival date/time.
💻 Technical Criteria
Given An import manifest train arrival is being processed and the V9 segment arrival date is invalid or missing
When The system needs to set train arrival date/time
Then Use system current date/time as the train arrival date/time
R-GCX016E-cbl-01564 Set Train Arrival Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Train Arrival Status Flag' is invoked, and assuming that an import manifest train has valid arrival date/time established, when the system processes the train arrival, the desired outcome is that set the train arrival status flag to indicate successful arrival processing.
💻 Technical Criteria
Given An import manifest train has valid arrival date/time established
When The system processes the train arrival
Then Set the train arrival status flag to indicate successful arrival processing
R-GCX016E-cbl-01565 Update Train Status in Database
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Status in Database' is invoked, and assuming that a train arrival status flag has been set for an import manifest train, when the system updates train information, the desired outcome is that update the train status in gcwtl train list segments database with arrival information.
💻 Technical Criteria
Given A train arrival status flag has been set for an import manifest train
When The system updates train information
Then Update the train status in GCWTL train list segments database with arrival information
R-GCX016E-cbl-01568 Generate Train Arrival Merlin Messages
Action Rules
📊 Business Logic Narrative
When the process 'Generate Train Arrival Merlin Messages' is invoked, and assuming that aei messages have been sent for an import manifest train arrival, when the system generates internal notifications, the desired outcome is that generate and send merlin messages to notify internal stakeholders of the train arrival.
💻 Technical Criteria
Given AEI messages have been sent for an import manifest train arrival
When The system generates internal notifications
Then Generate and send Merlin messages to notify internal stakeholders of the train arrival
R-GCX016E-cbl-01569 Log Train Arrival Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Train Arrival Action' is invoked, and assuming that merlin messages have been generated for an import manifest train arrival, when the system completes arrival processing, the desired outcome is that log the train arrival action with relevant details for audit and tracking purposes.
💻 Technical Criteria
Given Merlin messages have been generated for an import manifest train arrival
When The system completes arrival processing
Then Log the train arrival action with relevant details for audit and tracking purposes
R-GCX016E-cbl-01621 Disposition Code?
Decision Rules
📊 Business Logic Narrative
When the process 'Disposition Code?' is invoked, and assuming that a v9 segment is received with event code data, when the system evaluates the disposition code in the v9 segment, the desired outcome is that the system identifies pod (proof of delivery) or aad (actual arrival date) events and routes to appropriate arrival processing.
💻 Technical Criteria
Given A V9 segment is received with event code data
When The system evaluates the disposition code in the V9 segment
Then The system identifies POD (Proof of Delivery) or AAD (Actual Arrival Date) events and routes to appropriate arrival processing
R-GCX016E-cbl-01627 Train Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Train Type?' is invoked, and assuming that a train arrival is being processed with a formatted arrival date, when the system evaluates the train type based on manifest characteristics, the desired outcome is that the system classifies the train as either export manifest train (with 't' suffix) or import manifest train for specialized processing.
💻 Technical Criteria
Given A train arrival is being processed with a formatted arrival date
When The system evaluates the train type based on manifest characteristics
Then The system classifies the train as either export manifest train (with 'T' suffix) or import manifest train for specialized processing
R-GCX016E-cbl-01628 Validate Export Port Authorization
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Export Port Authorization' is invoked, and assuming that a train is classified as an export manifest train with 't' suffix, when the system processes the export train arrival, the desired outcome is that the system validates that the export port is authorized for the train's export operations before proceeding with arrival processing.
💻 Technical Criteria
Given A train is classified as an export manifest train with 'T' suffix
When The system processes the export train arrival
Then The system validates that the export port is authorized for the train's export operations before proceeding with arrival processing
R-GCX016E-cbl-01632 Generate AEI Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate AEI Notification' is invoked, and assuming that the train arrival has been logged and all arrival processing is complete, when the system generates external notifications for the arrival event, the desired outcome is that the system creates an aei notification containing train identification, arrival date, and location information for external systems.
💻 Technical Criteria
Given The train arrival has been logged and all arrival processing is complete
When The system generates external notifications for the arrival event
Then The system creates an AEI notification containing train identification, arrival date, and location information for external systems
R-GCX016E-cbl-01634 Train Type Check
Decision Rules
📊 Business Logic Narrative
When the process 'Train Type Check' is invoked, and assuming that a train arrival event (pod/aad disposition) has been received, when the system checks the train manifest type suffix, the desired outcome is that if the manifest has 't' suffix, classify as export manifest train, otherwise classify as import manifest train.
💻 Technical Criteria
Given A train arrival event (POD/AAD disposition) has been received
When The system checks the train manifest type suffix
Then If the manifest has 'T' suffix, classify as export manifest train, otherwise classify as import manifest train
R-GCX016E-cbl-01635 Port Valid for Export?
Validation Rules
📊 Business Logic Narrative
When the process 'Port Valid for Export?' is invoked, and assuming that an export manifest train with 't' suffix is being processed for arrival, when the system validates the arrival port against authorized export ports, the desired outcome is that if the port is valid for export operations, continue with arrival processing, otherwise terminate processing.
💻 Technical Criteria
Given An export manifest train with 'T' suffix is being processed for arrival
When The system validates the arrival port against authorized export ports
Then If the port is valid for export operations, continue with arrival processing, otherwise terminate processing
R-GCX016E-cbl-01720 Validate Converted Entry Type Code
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Converted Entry Type Code' is invoked, and assuming that an entry type code has been converted and potentially processed for border crossing, when the system validates the converted entry type code, the desired outcome is that verify that the converted entry type code is valid and meets system requirements.
💻 Technical Criteria
Given An entry type code has been converted and potentially processed for border crossing
When The system validates the converted entry type code
Then Verify that the converted entry type code is valid and meets system requirements
R-GCX016E-cbl-01725 Access Canadian Border Mapping Table
Action Rules
📊 Business Logic Narrative
When the process 'Access Canadian Border Mapping Table' is invoked, and assuming that a us port code needs to be mapped to a canadian border location, when the system requires canadian location mapping, the desired outcome is that the canadian border mapping table is accessed for lookup operations.
💻 Technical Criteria
Given A US port code needs to be mapped to a Canadian border location
When The system requires Canadian location mapping
Then The Canadian border mapping table is accessed for lookup operations
R-GCX016E-cbl-01726 Lookup US Port Code in Mapping Table
Process Rules
📊 Business Logic Narrative
When the process 'Lookup US Port Code in Mapping Table' is invoked, and assuming that a us port code is available and the canadian border mapping table is accessible, when the system performs a lookup operation for the us port code, the desired outcome is that the system searches the mapping table to find a corresponding canadian border location.
💻 Technical Criteria
Given A US port code is available and the Canadian border mapping table is accessible
When The system performs a lookup operation for the US port code
Then The system searches the mapping table to find a corresponding Canadian border location
R-GCX016E-cbl-01727 Mapping Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Mapping Found?' is invoked, and assuming that a us port code lookup has been performed in the canadian border mapping table, when the system evaluates the lookup results, the desired outcome is that the system determines if a valid mapping exists for the us port code.
💻 Technical Criteria
Given A US port code lookup has been performed in the Canadian border mapping table
When The system evaluates the lookup results
Then The system determines if a valid mapping exists for the US port code
R-GCX016E-cbl-01728 Retrieve Canadian Border Location Name
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Canadian Border Location Name' is invoked, and assuming that a valid mapping exists for the us port code in the canadian border mapping table, when the mapping is found during lookup, the desired outcome is that the system retrieves the corresponding canadian border location name.
💻 Technical Criteria
Given A valid mapping exists for the US port code in the Canadian border mapping table
When The mapping is found during lookup
Then The system retrieves the corresponding Canadian border location name
R-GCX016E-cbl-01732 Generate Error for Unmapped Port
Validation Rules
📊 Business Logic Narrative
When the process 'Generate Error for Unmapped Port' is invoked, and assuming that a us port code lookup in the canadian border mapping table returns no results, when no valid mapping is found for the us port code, the desired outcome is that the system generates an error indicating the port code cannot be mapped.
💻 Technical Criteria
Given A US port code lookup in the Canadian border mapping table returns no results
When No valid mapping is found for the US port code
Then The system generates an error indicating the port code cannot be mapped
R-GCX016E-cbl-01733 Use Default Canadian Location
Decision Rules
📊 Business Logic Narrative
When the process 'Use Default Canadian Location' is invoked, and assuming that an error has been generated for an unmapped us port code, when no specific mapping is available, the desired outcome is that the system uses a default canadian location to continue processing.
💻 Technical Criteria
Given An error has been generated for an unmapped US port code
When No specific mapping is available
Then The system uses a default Canadian location to continue processing
R-GCX016E-cbl-01871 US Port Code Found in Mapping?
Validation Rules
📊 Business Logic Narrative
When the process 'US Port Code Found in Mapping?' is invoked, and assuming that a us port code and access to the canadian border mapping table, when the system searches for the us port code in the mapping table, the desired outcome is that the system determines if a valid mapping exists for the port code.
💻 Technical Criteria
Given A US port code and access to the Canadian border mapping table
When The system searches for the US port code in the mapping table
Then The system determines if a valid mapping exists for the port code
R-GCX016E-cbl-01872 Retrieve Canadian Border Port Name
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Canadian Border Port Name' is invoked, and assuming that a us port code that exists in the canadian border mapping table, when the system finds a valid mapping entry, the desired outcome is that the corresponding canadian border port name is retrieved from the mapping table.
💻 Technical Criteria
Given A US port code that exists in the Canadian border mapping table
When The system finds a valid mapping entry
Then The corresponding Canadian border port name is retrieved from the mapping table
R-GCX016E-cbl-01877 Generate Warning Message
Process Rules
📊 Business Logic Narrative
When the process 'Generate Warning Message' is invoked, and assuming that a us port code with no mapping found and default border location being used, when the system assigns the default border location, the desired outcome is that a warning message is generated to alert users about the missing port code mapping.
💻 Technical Criteria
Given A US port code with no mapping found and default border location being used
When The system assigns the default border location
Then A warning message is generated to alert users about the missing port code mapping
R-GCX016E-cbl-01881 Disposition Code Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Disposition Code Type?' is invoked, and assuming that an n9 reference segment with disposition code is being processed, when the system evaluates the disposition code type, the desired outcome is that the system should route to a1 processing if a1 code or a3 processing if a3 code.
💻 Technical Criteria
Given An N9 reference segment with disposition code is being processed
When The system evaluates the disposition code type
Then The system should route to A1 processing if A1 code or A3 processing if A3 code
R-GCX016E-cbl-01887 FDA Disposition Code?
Decision Rules
📊 Business Logic Narrative
When the process 'FDA Disposition Code?' is invoked, and assuming that a disposition code is being processed for n9 reference segment management, when the system evaluates the disposition code type, the desired outcome is that the system routes to a1 code processing if disposition code is a1, routes to a3 code processing if disposition code is a3, or exits processing for any other disposition code.
💻 Technical Criteria
Given A disposition code is being processed for N9 reference segment management
When The system evaluates the disposition code type
Then The system routes to A1 code processing if disposition code is A1, routes to A3 code processing if disposition code is A3, or exits processing for any other disposition code
R-GCX016E-cbl-02101 Generate Error Message
Process Rules
📊 Business Logic Narrative
When the process 'Generate Error Message' is invoked, and assuming that a manual release request fails validation or processing, when the system encounters an error condition, the desired outcome is that the system generates a specific error message describing the failure reason and routes it to the appropriate error handling system.
💻 Technical Criteria
Given A manual release request fails validation or processing
When The system encounters an error condition
Then The system generates a specific error message describing the failure reason and routes it to the appropriate error handling system
R-GCX016E-cbl-02184 Add Disposition Code Description
Process Rules
📊 Business Logic Narrative
When the process 'Add Disposition Code Description' is invoked, and assuming that location context has been added to the hold notification, when the system adds disposition code descriptions, the desired outcome is that the system includes disposition code descriptions from disposition code tables providing business-friendly explanations of the codes, regulatory requirements, and action items associated with the hold.
💻 Technical Criteria
Given Location context has been added to the hold notification
When The system adds disposition code descriptions
Then The system includes disposition code descriptions from disposition code tables providing business-friendly explanations of the codes, regulatory requirements, and action items associated with the hold
R-GCX016E-cbl-02186 Route to Business Users
Action Rules
📊 Business Logic Narrative
When the process 'Route to Business Users' is invoked, and assuming that a detailed hold message has been created, when the system routes the notification to business users, the desired outcome is that the system determines appropriate recipients based on hold type, location, and business rules, then routes the notification through appropriate channels (merlin system, email, or other communication methods) to relevant business personnel.
💻 Technical Criteria
Given A detailed hold message has been created
When The system routes the notification to business users
Then The system determines appropriate recipients based on hold type, location, and business rules, then routes the notification through appropriate channels (Merlin system, email, or other communication methods) to relevant business personnel
R-GCX016E-cbl-02187 Log Hold Notification
Process Rules
📊 Business Logic Narrative
When the process 'Log Hold Notification' is invoked, and assuming that a hold notification has been routed to business users, when the system logs the notification activity, the desired outcome is that the system creates audit records documenting the hold notification including timestamp, recipients, hold details, and notification status for compliance and business tracking purposes.
💻 Technical Criteria
Given A hold notification has been routed to business users
When The system logs the notification activity
Then The system creates audit records documenting the hold notification including timestamp, recipients, hold details, and notification status for compliance and business tracking purposes
R-GCX016E-cbl-02196 Arrival/Export Codes Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Arrival/Export Codes Present?' is invoked, and assuming that proceed evaluation has been completed, when the system evaluates for arrival or export conditions, the desired outcome is that arrival or export disposition codes are identified if present in the status array.
💻 Technical Criteria
Given Proceed evaluation has been completed
When The system evaluates for arrival or export conditions
Then Arrival or export disposition codes are identified if present in the status array
R-GCX016E-cbl-02197 Validate Location and Port
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Location and Port' is invoked, and assuming that arrival or export disposition codes are present, when the system validates location requirements, the desired outcome is that location and port information are verified as valid for arrival or export processing.
💻 Technical Criteria
Given Arrival or export disposition codes are present
When The system validates location requirements
Then Location and port information are verified as valid for arrival or export processing
R-GCX016E-cbl-02198 Manual Release Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Manual Release Present?' is invoked, and assuming that location and port validation has been completed, when the system evaluates for manual release override, the desired outcome is that manual release disposition codes are identified if present in the status array.
💻 Technical Criteria
Given Location and port validation has been completed
When The system evaluates for manual release override
Then Manual release disposition codes are identified if present in the status array
R-GCX016E-cbl-02228 Validate Arrival Location
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Arrival Location' is invoked, and assuming that an arrival disposition code (aad or pod) has been identified, when the system validates the location code against valid arrival locations, the desired outcome is that the system confirms the location is authorized for arrival processing or rejects invalid locations.
💻 Technical Criteria
Given An arrival disposition code (AAD or POD) has been identified
When The system validates the location code against valid arrival locations
Then The system confirms the location is authorized for arrival processing or rejects invalid locations
R-GCX016E-cbl-02234 Validate Export Location
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Export Location' is invoked, and assuming that an export disposition code has been identified, when the system validates the location code against authorized export locations, the desired outcome is that the system confirms the location is authorized for export processing or rejects invalid locations.
💻 Technical Criteria
Given An export disposition code has been identified
When The system validates the location code against authorized export locations
Then The system confirms the location is authorized for export processing or rejects invalid locations
R-GCX016E-cbl-02244 Restore Previous Export Date
Action Rules
📊 Business Logic Narrative
When the process 'Restore Previous Export Date' is invoked, and assuming that export status is being cancelled and a previous export date exists, when the system processes the export cancellation, the desired outcome is that the previous export date is restored to maintain historical accuracy.
💻 Technical Criteria
Given Export status is being cancelled and a previous export date exists
When The system processes the export cancellation
Then The previous export date is restored to maintain historical accuracy
R-GCX016E-cbl-02245 Clear Export Index
Action Rules
📊 Business Logic Narrative
When the process 'Clear Export Index' is invoked, and assuming that export status is being cancelled, when the system processes the export cancellation, the desired outcome is that the export index is cleared to remove the export location reference.
💻 Technical Criteria
Given Export status is being cancelled
When The system processes the export cancellation
Then The export index is cleared to remove the export location reference
R-GCX016E-cbl-02296 Route to Merlin Message System
Action Rules
📊 Business Logic Narrative
When the process 'Route to Merlin Message System' is invoked, and assuming that a complete cancellation message is formatted with all required details, when the system routes the message to merlin, the desired outcome is that the message is successfully submitted to the merlin messaging system for processing.
💻 Technical Criteria
Given A complete cancellation message is formatted with all required details
When The system routes the message to Merlin
Then The message is successfully submitted to the Merlin messaging system for processing
R-GCX016E-cbl-02297 Send to Business Users
Action Rules
📊 Business Logic Narrative
When the process 'Send to Business Users' is invoked, and assuming that the cancellation message is routed to merlin messaging system, when the system processes the message delivery, the desired outcome is that the notification is delivered to the appropriate business users and stakeholders.
💻 Technical Criteria
Given The cancellation message is routed to Merlin messaging system
When The system processes the message delivery
Then The notification is delivered to the appropriate business users and stakeholders
R-GCX016E-cbl-02303 Hold Disposition Code?
Decision Rules
📊 Business Logic Narrative
When the process 'Hold Disposition Code?' is invoked, and assuming that a disposition code is being evaluated, when the disposition code indicates a hold condition (border hold, destination hold, fda hold), the desired outcome is that set the hold status flag to true.
💻 Technical Criteria
Given A disposition code is being evaluated
When The disposition code indicates a hold condition (border hold, destination hold, FDA hold)
Then Set the hold status flag to true
R-GCX016E-cbl-02311 Export Disposition Code?
Decision Rules
📊 Business Logic Narrative
When the process 'Export Disposition Code?' is invoked, and assuming that a disposition code is being evaluated, when the disposition code indicates an export condition, the desired outcome is that set the export status flag to true.
💻 Technical Criteria
Given A disposition code is being evaluated
When The disposition code indicates an export condition
Then Set the export status flag to true
R-GCX016E-cbl-02312 Set Export Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Export Status Flag' is invoked, and assuming that an export disposition code has been identified, when processing the disposition code, the desired outcome is that the export status flag is set to active.
💻 Technical Criteria
Given An export disposition code has been identified
When Processing the disposition code
Then The export status flag is set to active
R-GCX016E-cbl-02323 Export Status Active?
Decision Rules
📊 Business Logic Narrative
When the process 'Export Status Active?' is invoked, and assuming that no hold, proceed, or arrival status conditions are active, when export status flag is active, the desired outcome is that set final status to exported.
💻 Technical Criteria
Given No hold, proceed, or arrival status conditions are active
When Export status flag is active
Then Set final status to EXPORTED
R-GCX016E-cbl-03562 Border Hold Takes Priority?
Policy Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Border Hold Takes Priority?', assuming that border hold is present and fda hold does not take priority, when the system evaluates hold priority, the desired outcome is that the system returns true if border hold takes priority over remaining hold types, false otherwise.
💻 Technical Criteria
EXCLUDING Border hold is present and FDA hold does not take priority
When The system evaluates hold priority
Then The system returns true if border hold takes priority over remaining hold types, false otherwise
R-GCX016E-cbl-03319 Extract Transport Type
Process Rules
📊 Business Logic Narrative
When the process 'Extract Transport Type' is invoked, and assuming that an m10 segment with valid scac code is being processed, when the system extracts transport type information, the desired outcome is that the transport type code is extracted from the designated position in the m10 segment.
💻 Technical Criteria
Given An M10 segment with valid SCAC code is being processed
When The system extracts transport type information
Then The transport type code is extracted from the designated position in the M10 segment
R-GCX016E-cbl-03320 Transport Type Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Transport Type Valid?' is invoked, and assuming that a transport type code has been extracted from the m10 segment, when the system validates the transport type, the desired outcome is that the transport type must be a valid code representing rail, truck, vessel, or air transportation.
💻 Technical Criteria
Given A transport type code has been extracted from the M10 segment
When The system validates the transport type
Then The transport type must be a valid code representing rail, truck, vessel, or air transportation
R-GCX016E-cbl-03321 Extract Country Code
Process Rules
📊 Business Logic Narrative
When the process 'Extract Country Code' is invoked, and assuming that an m10 segment with valid transport type is being processed, when the system extracts country code information, the desired outcome is that the country code is extracted from the designated position in the m10 segment.
💻 Technical Criteria
Given An M10 segment with valid transport type is being processed
When The system extracts country code information
Then The country code is extracted from the designated position in the M10 segment
R-GCX016E-cbl-03322 Country Code Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Country Code Valid?' is invoked, and assuming that a country code has been extracted from the m10 segment, when the system validates the country code, the desired outcome is that the country code must be a valid iso country code or recognized customs country identifier.
💻 Technical Criteria
Given A country code has been extracted from the M10 segment
When The system validates the country code
Then The country code must be a valid ISO country code or recognized customs country identifier
R-GCX016E-cbl-03325 Vessel Info Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Vessel Info Valid?' is invoked, and assuming that vessel details have been extracted from the m10 segment, when the system validates the vessel information, the desired outcome is that the vessel name must be non-blank and vessel details must conform to transportation standards.
💻 Technical Criteria
Given Vessel details have been extracted from the M10 segment
When The system validates the vessel information
Then The vessel name must be non-blank and vessel details must conform to transportation standards
R-GCX016E-cbl-03326 Extract Cross-Border Routing Info
Process Rules
📊 Business Logic Narrative
When the process 'Extract Cross-Border Routing Info' is invoked, and assuming that valid vessel information has been extracted from the m10 segment, when the system extracts cross-border routing information, the desired outcome is that port of entry, port of exit, and routing codes are extracted from their designated positions in the m10 segment.
💻 Technical Criteria
Given Valid vessel information has been extracted from the M10 segment
When The system extracts cross-border routing information
Then Port of entry, port of exit, and routing codes are extracted from their designated positions in the M10 segment
R-GCX016E-cbl-03327 Routing Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Routing Valid?' is invoked, and assuming that cross-border routing information has been extracted from the m10 segment, when the system validates the routing information, the desired outcome is that port codes must be valid customs ports and routing must be logically consistent for the transportation mode.
💻 Technical Criteria
Given Cross-border routing information has been extracted from the M10 segment
When The system validates the routing information
Then Port codes must be valid customs ports and routing must be logically consistent for the transportation mode
R-GCX016E-cbl-03328 Build Foreign Manifest Structure
Process Rules
📊 Business Logic Narrative
When the process 'Build Foreign Manifest Structure' is invoked, and assuming that all m10 segment data has been validated successfully, when the system builds the foreign manifest structure, the desired outcome is that a complete foreign manifest record is created with scac, transport type, country, vessel, and routing information.
💻 Technical Criteria
Given All M10 segment data has been validated successfully
When The system builds the foreign manifest structure
Then A complete foreign manifest record is created with SCAC, transport type, country, vessel, and routing information
R-GCX016E-cbl-03330 Manifest Complete?
Validation Rules
📊 Business Logic Narrative
When the process 'Manifest Complete?' is invoked, and assuming that manifest data fields have been set with extracted information, when the system validates the complete manifest, the desired outcome is that all mandatory fields must be populated and the manifest must meet completeness requirements for customs processing.
💻 Technical Criteria
Given Manifest data fields have been set with extracted information
When The system validates the complete manifest
Then All mandatory fields must be populated and the manifest must meet completeness requirements for customs processing
R-GCX016E-cbl-03453 Extract Transport Type
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Transport Type' is invoked, and assuming that m10 segment scac code has been mapped, when the system processes the transport type field from m10 segment, the desired outcome is that the transport type is extracted and prepared for manifest structure mapping.
💻 Technical Criteria
Given M10 segment SCAC code has been mapped
When The system processes the transport type field from M10 segment
Then The transport type is extracted and prepared for manifest structure mapping
R-GCX016E-cbl-03454 Map Country Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Map Country Code' is invoked, and assuming that transport type has been extracted from m10 segment, when the system processes the country code field from m10 segment, the desired outcome is that the country code is mapped to the foreign manifest structure with proper validation.
💻 Technical Criteria
Given Transport type has been extracted from M10 segment
When The system processes the country code field from M10 segment
Then The country code is mapped to the foreign manifest structure with proper validation
R-GCX016E-cbl-03456 Map Port Information
Definitional Rules
📊 Business Logic Narrative
When the process 'Map Port Information' is invoked, and assuming that vessel details have been extracted from m10 segment, when the system processes port information fields from m10 segment, the desired outcome is that port of loading and discharge codes are mapped to the foreign manifest structure.
💻 Technical Criteria
Given Vessel details have been extracted from M10 segment
When The system processes port information fields from M10 segment
Then Port of loading and discharge codes are mapped to the foreign manifest structure
R-GCX016E-cbl-02436 Extract Transport Type from M10
Process Rules
📊 Business Logic Narrative
When the process 'Extract Transport Type from M10' is invoked, and assuming that an m10 segment containing transport information is received, when the system processes the m10 segment for foreign manifest building, the desired outcome is that the transport type is extracted from the m10 segment and stored for manifest construction.
💻 Technical Criteria
Given An M10 segment containing transport information is received
When The system processes the M10 segment for foreign manifest building
Then The transport type is extracted from the M10 segment and stored for manifest construction
R-GCX016E-cbl-02443 Build Foreign Manifest Structure
Process Rules
📊 Business Logic Narrative
When the process 'Build Foreign Manifest Structure' is invoked, and assuming that all required information has been extracted from the m10 segment including scac, transport type, country code, and vessel details, when the system builds the foreign manifest structure, the desired outcome is that a complete foreign manifest structure is constructed with all extracted information properly organized.
💻 Technical Criteria
Given All required information has been extracted from the M10 segment including SCAC, transport type, country code, and vessel details
When The system builds the foreign manifest structure
Then A complete foreign manifest structure is constructed with all extracted information properly organized
R-GCX016E-cbl-02444 Set Transport Mode Information
Process Rules
📊 Business Logic Narrative
When the process 'Set Transport Mode Information' is invoked, and assuming that transport type has been extracted from the m10 segment and foreign manifest structure is being built, when the system sets transport mode information in the manifest, the desired outcome is that transport mode information is properly configured in the foreign manifest structure.
💻 Technical Criteria
Given Transport type has been extracted from the M10 segment and foreign manifest structure is being built
When The system sets transport mode information in the manifest
Then Transport mode information is properly configured in the foreign manifest structure
R-GCX016E-cbl-02449 Station Type Required?
Decision Rules
📊 Business Logic Narrative
When the process 'Station Type Required?' is invoked, and assuming that a station data lookup request is initiated, when the system evaluates the station type requirement, the desired outcome is that the system routes to either destination station retrieval or key station retrieval based on the station type needed.
💻 Technical Criteria
Given A station data lookup request is initiated
When The system evaluates the station type requirement
Then The system routes to either destination station retrieval or key station retrieval based on the station type needed
R-GCX016E-cbl-02450 Retrieve Destination Station Information
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Destination Station Information' is invoked, and assuming that a destination station lookup is required, when the system processes the destination station request, the desired outcome is that the system accesses the ds table via gcctbio to retrieve destination station information.
💻 Technical Criteria
Given A destination station lookup is required
When The system processes the destination station request
Then The system accesses the DS table via GCCTBIO to retrieve destination station information
R-GCX016E-cbl-02452 Access DS Table via GCCTBIO
Action Rules
📊 Business Logic Narrative
When the process 'Access DS Table via GCCTBIO' is invoked, and assuming that destination station information is needed, when the system calls gcctbio to access the ds table, the desired outcome is that the system retrieves station data from the ds table using the gcctbio interface.
💻 Technical Criteria
Given Destination station information is needed
When The system calls GCCTBIO to access the DS table
Then The system retrieves station data from the DS table using the GCCTBIO interface
R-GCX016E-cbl-02454 Station Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Station Found?' is invoked, and assuming that a station lookup has been performed in either ds or ks table, when the system evaluates the lookup results, the desired outcome is that the system determines if the station was found and routes to either location validation or station not found error processing.
💻 Technical Criteria
Given A station lookup has been performed in either DS or KS table
When The system evaluates the lookup results
Then The system determines if the station was found and routes to either location validation or station not found error processing
R-GCX016E-cbl-02459 Generate Invalid Location Error
Validation Rules
📊 Business Logic Narrative
When the process 'Generate Invalid Location Error' is invoked, and assuming that a station has been found but its location identifier has been validated, when the location identifier fails validation criteria, the desired outcome is that the system generates an invalid location error and completes the station lookup process.
💻 Technical Criteria
Given A station has been found but its location identifier has been validated
When The location identifier fails validation criteria
Then The system generates an invalid location error and completes the station lookup process
R-GCX016E-cbl-02496 Route to Appropriate Recipients
Action Rules
📊 Business Logic Narrative
When the process 'Route to Appropriate Recipients' is invoked, and assuming that a comprehensive merlin notification has been created, when the notification is routed to recipients, the desired outcome is that the message is sent to appropriate business users, brokers, and systems based on established routing rules.
💻 Technical Criteria
Given A comprehensive Merlin notification has been created
When The notification is routed to recipients
Then The message is sent to appropriate business users, brokers, and systems based on established routing rules
R-GCX016E-cbl-02509 Skip Quantity Impact Reporting
Decision Rules
📊 Business Logic Narrative
When the process 'Skip Quantity Impact Reporting' is invoked, and assuming that no release quantity change was detected or disposition code has no quantity impact, when quantity impact reporting evaluation is performed, the desired outcome is that the system skips creating impact descriptions and does not add quantity information to notifications.
💻 Technical Criteria
Given No release quantity change was detected or disposition code has no quantity impact
When Quantity impact reporting evaluation is performed
Then The system skips creating impact descriptions and does not add quantity information to notifications
R-GCX016E-cbl-02524 Location Identifier Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Location Identifier Valid?' is invoked, and assuming that a location identifier has been validated for format compliance, when the system checks if the location identifier is valid, the desired outcome is that if valid, proceed to call generic table interface; if invalid, log error and return error to calling process.
💻 Technical Criteria
Given A location identifier has been validated for format compliance
When The system checks if the location identifier is valid
Then If valid, proceed to call generic table interface; if invalid, log error and return error to calling process
R-GCX016E-cbl-02525 Call Generic Table I/O Interface
Action Rules
📊 Business Logic Narrative
When the process 'Call Generic Table I/O Interface' is invoked, and assuming that a valid location identifier is available for processing, when the system needs to retrieve station information, the desired outcome is that the generic table i/o interface is called to access the station data repository.
💻 Technical Criteria
Given A valid location identifier is available for processing
When The system needs to retrieve station information
Then The generic table I/O interface is called to access the station data repository
R-GCX016E-cbl-02526 Retrieve Station Information from DS Table
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Station Information from DS Table' is invoked, and assuming that the generic table i/o interface has been called with a valid location identifier, when the system searches the ds table for matching station data, the desired outcome is that station information is retrieved from the ds table based on the location identifier.
💻 Technical Criteria
Given The generic table I/O interface has been called with a valid location identifier
When The system searches the DS table for matching station data
Then Station information is retrieved from the DS table based on the location identifier
R-GCX016E-cbl-02530 Generate Station Not Found Error
Process Rules
📊 Business Logic Narrative
When the process 'Generate Station Not Found Error' is invoked, and assuming that a search for station information in the ds table has been performed, when no station data is found for the location identifier, the desired outcome is that a station not found error is generated and returned to the calling process.
💻 Technical Criteria
Given A search for station information in the DS table has been performed
When No station data is found for the location identifier
Then A station not found error is generated and returned to the calling process
R-GCX016E-cbl-02531 Log Invalid Location Identifier
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Invalid Location Identifier', assuming that a location identifier has failed format validation, when the system processes the invalid location identifier, the desired outcome is that an invalid location identifier error is logged and error is returned to calling process.
💻 Technical Criteria
EXCLUDING A location identifier has failed format validation
When The system processes the invalid location identifier
Then An invalid location identifier error is logged and error is returned to calling process
R-GCX016E-cbl-02532 Extract Location Identifier from X4 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Location Identifier from X4 Segment' is invoked, and assuming that an x4 segment containing location data is available for processing, when the system processes the x4 segment for station lookup, the desired outcome is that the location identifier is extracted from the x4 segment and made available for table lookup.
💻 Technical Criteria
Given An X4 segment containing location data is available for processing
When The system processes the X4 segment for station lookup
Then The location identifier is extracted from the X4 segment and made available for table lookup
R-GCX016E-cbl-02533 Location Identifier Present?
Validation Rules
📊 Business Logic Narrative
When the process 'Location Identifier Present?' is invoked, and assuming that the system has extracted location data from the x4 segment, when the system checks for the presence of a location identifier, the desired outcome is that if location identifier is present, proceed with station lookup; if not present, continue with default routing.
💻 Technical Criteria
Given The system has extracted location data from the X4 segment
When The system checks for the presence of a location identifier
Then If location identifier is present, proceed with station lookup; if not present, continue with default routing
R-GCX016E-cbl-02534 Set DS Table Type for Lookup
Process Rules
📊 Business Logic Narrative
When the process 'Set DS Table Type for Lookup' is invoked, and assuming that a valid location identifier is available for station lookup, when the system prepares to access the ds table, the desired outcome is that the ds table type is set for the lookup operation.
💻 Technical Criteria
Given A valid location identifier is available for station lookup
When The system prepares to access the DS table
Then The DS table type is set for the lookup operation
R-GCX016E-cbl-02535 Call GCCTBIO Table I/O Interface
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCTBIO Table I/O Interface' is invoked, and assuming that the ds table type is configured and location identifier is available, when the system needs to retrieve station information, the desired outcome is that the gcctbio table i/o interface is invoked to access the ds table.
💻 Technical Criteria
Given The DS table type is configured and location identifier is available
When The system needs to retrieve station information
Then The GCCTBIO table I/O interface is invoked to access the DS table
R-GCX016E-cbl-02536 Station Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Station Record Found?' is invoked, and assuming that the gcctbio interface has been called with a location identifier, when the system checks the lookup result, the desired outcome is that if station record is found, proceed with data retrieval; if not found, log error and continue with default routing.
💻 Technical Criteria
Given The GCCTBIO interface has been called with a location identifier
When The system checks the lookup result
Then If station record is found, proceed with data retrieval; if not found, log error and continue with default routing
R-GCX016E-cbl-02540 Log Station Not Found Error
Process Rules
📊 Business Logic Narrative
When the process 'Log Station Not Found Error' is invoked, and assuming that a station lookup has been performed with a valid location identifier, when no matching station record is found in the ds table, the desired outcome is that a station not found error is logged for tracking and audit purposes.
💻 Technical Criteria
Given A station lookup has been performed with a valid location identifier
When No matching station record is found in the DS table
Then A station not found error is logged for tracking and audit purposes
R-GCX016E-cbl-02541 Continue with Default Routing
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Continue with Default Routing', assuming that either no location identifier is present or station record is not found, when the system cannot obtain specific station information, the desired outcome is that processing continues with default routing configuration.
💻 Technical Criteria
EXCLUDING Either no location identifier is present or station record is not found
When The system cannot obtain specific station information
Then Processing continues with default routing configuration
R-GCX016E-cbl-02542 Extract Location Code from X4 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Location Code from X4 Segment' is invoked, and assuming that an x4 segment contains location information, when the system processes the x4 segment for location validation, the desired outcome is that the location code is extracted and prepared for key station lookup.
💻 Technical Criteria
Given An X4 segment contains location information
When The system processes the X4 segment for location validation
Then The location code is extracted and prepared for key station lookup
R-GCX016E-cbl-02543 Set Table Type to KS - Key Station
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Table Type to KS - Key Station' is invoked, and assuming that a location code needs to be validated against key station data, when the system prepares for table lookup operation, the desired outcome is that the table type is set to ks for key station table access.
💻 Technical Criteria
Given A location code needs to be validated against key station data
When The system prepares for table lookup operation
Then The table type is set to KS for Key Station table access
R-GCX016E-cbl-02544 Call GCCTBIO Table Lookup Interface
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCTBIO Table Lookup Interface' is invoked, and assuming that location code and table type ks are configured, when the system needs to validate location against key station data, the desired outcome is that gcctbio table lookup interface is called to retrieve station information.
💻 Technical Criteria
Given Location code and table type KS are configured
When The system needs to validate location against key station data
Then GCCTBIO table lookup interface is called to retrieve station information
R-GCX016E-cbl-02545 Key Station Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Key Station Found?' is invoked, and assuming that a table lookup has been performed for a location code in ks table, when the system evaluates the lookup results, the desired outcome is that the system determines whether a valid key station record was found or not.
💻 Technical Criteria
Given A table lookup has been performed for a location code in KS table
When The system evaluates the lookup results
Then The system determines whether a valid key station record was found or not
R-GCX016E-cbl-02546 Retrieve Key Station Information
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Key Station Information' is invoked, and assuming that a valid key station record exists for the location code, when the table lookup successfully finds the station, the desired outcome is that key station information is retrieved from the ks table data.
💻 Technical Criteria
Given A valid key station record exists for the location code
When The table lookup successfully finds the station
Then Key station information is retrieved from the KS table data
R-GCX016E-cbl-02547 Validate Location Identifier
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Location Identifier' is invoked, and assuming that key station information has been retrieved from the table, when the system validates the location identifier, the desired outcome is that the location identifier is confirmed as valid based on station data.
💻 Technical Criteria
Given Key station information has been retrieved from the table
When The system validates the location identifier
Then The location identifier is confirmed as valid based on station data
R-GCX016E-cbl-02548 Set Station Data Fields
Process Rules
📊 Business Logic Narrative
When the process 'Set Station Data Fields' is invoked, and assuming that location identifier has been successfully validated, when the system processes the validated station information, the desired outcome is that station data fields are populated with the retrieved key station details.
💻 Technical Criteria
Given Location identifier has been successfully validated
When The system processes the validated station information
Then Station data fields are populated with the retrieved key station details
R-GCX016E-cbl-02549 Return Validated Location Information
Process Rules
📊 Business Logic Narrative
When the process 'Return Validated Location Information' is invoked, and assuming that station data fields have been populated with valid information, when the location validation process completes successfully, the desired outcome is that validated location information is returned to the requesting process.
💻 Technical Criteria
Given Station data fields have been populated with valid information
When The location validation process completes successfully
Then Validated location information is returned to the requesting process
R-GCX016E-cbl-02550 Generate Location Validation Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Location Validation Error', assuming that a location code does not exist in the ks key station table, when the table lookup fails to find a matching station record, the desired outcome is that a location validation error is generated for the invalid location.
💻 Technical Criteria
EXCLUDING A location code does not exist in the KS key station table
When The table lookup fails to find a matching station record
Then A location validation error is generated for the invalid location
R-GCX016E-cbl-02551 Set Error Flag for Invalid Location
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Error Flag for Invalid Location', assuming that a location validation error has been generated, when the system handles the invalid location condition, the desired outcome is that an error flag is set to indicate invalid location status.
💻 Technical Criteria
EXCLUDING A location validation error has been generated
When The system handles the invalid location condition
Then An error flag is set to indicate invalid location status
R-GCX016E-cbl-02552 Continue Processing with Error Status
Process Rules
📊 Business Logic Narrative
When the process 'Continue Processing with Error Status' is invoked, and assuming that an error flag has been set for invalid location, when the system continues with subsequent processing steps, the desired outcome is that processing continues with error status maintained for downstream handling.
💻 Technical Criteria
Given An error flag has been set for invalid location
When The system continues with subsequent processing steps
Then Processing continues with error status maintained for downstream handling
R-GCX016E-cbl-02553 Generic Table I/O Request
Action Rules
📊 Business Logic Narrative
When the process 'Generic Table I/O Request' is invoked, and assuming that a request is made for table data retrieval, when the generic table i/o interface is invoked, the desired outcome is that the system should route the request to the appropriate table lookup service.
💻 Technical Criteria
Given A request is made for table data retrieval
When The generic table I/O interface is invoked
Then The system should route the request to the appropriate table lookup service
R-GCX016E-cbl-02559 Retrieve Destination Station Data
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Destination Station Data' is invoked, and assuming that a destination station data request is processed through gcctbio, when the destination station lookup is executed, the desired outcome is that the system should retrieve destination station details from the gcstbrt table segments.
💻 Technical Criteria
Given A destination station data request is processed through GCCTBIO
When The destination station lookup is executed
Then The system should retrieve destination station details from the GCSTBRT table segments
R-GCX016E-cbl-02603 Disposition Code Action?
Decision Rules
📊 Business Logic Narrative
When the process 'Disposition Code Action?' is invoked, and assuming that a disposition code with defined quantity impact rules, when the system processes the disposition code for quantity calculations, the desired outcome is that the system routes to add quantity processing if the code increases release amounts, subtract quantity processing if it decreases amounts, or no change processing if quantities remain the same.
💻 Technical Criteria
Given A disposition code with defined quantity impact rules
When The system processes the disposition code for quantity calculations
Then The system routes to add quantity processing if the code increases release amounts, subtract quantity processing if it decreases amounts, or no change processing if quantities remain the same
R-GCX016E-cbl-02672 Contact Information Complete?
Decision Rules
📊 Business Logic Narrative
When the process 'Contact Information Complete?' is invoked, and assuming that contact information has been validated, when the system evaluates information completeness, the desired outcome is that the system determines if contact information is complete and routes to storage or warning logging accordingly.
💻 Technical Criteria
Given Contact information has been validated
When The system evaluates information completeness
Then The system determines if contact information is complete and routes to storage or warning logging accordingly
R-GCX016E-cbl-02687 Include Origin/Destination Stations
Process Rules
📊 Business Logic Narrative
When the process 'Include Origin/Destination Stations' is invoked, and assuming that content description has been included in the email content, when the system processes origin and destination station information for email inclusion, the desired outcome is that the system adds origin and destination station details to the email notification content.
💻 Technical Criteria
Given Content description has been included in the email content
When The system processes origin and destination station information for email inclusion
Then The system adds origin and destination station details to the email notification content
R-GCX016E-cbl-02688 Include CIH Disposition Information
Process Rules
📊 Business Logic Narrative
When the process 'Include CIH Disposition Information' is invoked, and assuming that origin and destination station information has been included in the email content, when the system processes cih disposition information for email inclusion, the desired outcome is that the system adds cih disposition code details and related information to the email notification.
💻 Technical Criteria
Given Origin and destination station information has been included in the email content
When The system processes CIH disposition information for email inclusion
Then The system adds CIH disposition code details and related information to the email notification
R-GCX016E-cbl-02695 Reroute to Default Recipient
Action Rules
📊 Business Logic Narrative
When the process 'Reroute to Default Recipient' is invoked, and assuming that email delivery has failed and alternative handling has been initiated, when the system implements fallback notification procedures, the desired outcome is that the system reroutes the notification to default recipients (aei9999, om01247) to ensure notification delivery.
💻 Technical Criteria
Given Email delivery has failed and alternative handling has been initiated
When The system implements fallback notification procedures
Then The system reroutes the notification to default recipients (AEI9999, OM01247) to ensure notification delivery
R-GCX016E-cbl-02707 Route to Alternative Recipient
Action Rules
📊 Business Logic Narrative
When the process 'Route to Alternative Recipient' is invoked, and assuming that primary email delivery has failed after maximum retry attempts, when the system routes to alternative recipient, the desired outcome is that the email is prepared for delivery to backup recipients (aei9999, om01247) as fallback options.
💻 Technical Criteria
Given Primary email delivery has failed after maximum retry attempts
When The system routes to alternative recipient
Then The email is prepared for delivery to backup recipients (AEI9999, OM01247) as fallback options
R-GCX016E-cbl-02721 Route Debug Message to Recipients
Action Rules
📊 Business Logic Narrative
When the process 'Route Debug Message to Recipients' is invoked, and assuming that debug message has been formatted and is ready for distribution, when the system processes debug message routing, the desired outcome is that debug messages are routed to designated merlin recipients for troubleshooting support.
💻 Technical Criteria
Given Debug message has been formatted and is ready for distribution
When The system processes debug message routing
Then Debug messages are routed to designated Merlin recipients for troubleshooting support
R-GCX016E-cbl-02723 ERROR Message Type
Decision Rules
📊 Business Logic Narrative
When the process 'ERROR Message Type' is invoked, and assuming that a merlin message is ready for distribution, when the message type is determined to be error, the desired outcome is that the message should be routed to the in destination.
💻 Technical Criteria
Given A Merlin message is ready for distribution
When The message type is determined to be ERROR
Then The message should be routed to the IN destination
R-GCX016E-cbl-02724 INFO Message Type
Decision Rules
📊 Business Logic Narrative
When the process 'INFO Message Type' is invoked, and assuming that a merlin message is ready for distribution and message type is info, when the system processes the message routing, the desired outcome is that the message should be sent to in destination and all valid sd segment merlin ids.
💻 Technical Criteria
Given A Merlin message is ready for distribution and message type is INFO
When The system processes the message routing
Then The message should be sent to IN destination and all valid SD segment Merlin IDs
R-GCX016E-cbl-02725 RELEASE Message Type
Decision Rules
📊 Business Logic Narrative
When the process 'RELEASE Message Type' is invoked, and assuming that a merlin message is ready for distribution and message type is release, when the system processes the message routing, the desired outcome is that the message should be sent only to valid sd segment merlin ids and not to in destination.
💻 Technical Criteria
Given A Merlin message is ready for distribution and message type is RELEASE
When The system processes the message routing
Then The message should be sent only to valid SD segment Merlin IDs and not to IN destination
R-GCX016E-cbl-02730 Route to Configured Recipient
Action Rules
📊 Business Logic Narrative
When the process 'Route to Configured Recipient' is invoked, and assuming that valid recipients have been found in the ad segment configuration, when the system processes message routing, the desired outcome is that the message should be delivered to all configured valid recipients.
💻 Technical Criteria
Given Valid recipients have been found in the AD segment configuration
When The system processes message routing
Then The message should be delivered to all configured valid recipients
R-GCX016E-cbl-02731 Route to Default Recipient OM01247
Action Rules
📊 Business Logic Narrative
When the process 'Route to Default Recipient OM01247' is invoked, and assuming that no valid recipients were found in the ad segment configuration, when the system needs to deliver the message, the desired outcome is that the message should be routed to the default recipient om01247.
💻 Technical Criteria
Given No valid recipients were found in the AD segment configuration
When The system needs to deliver the message
Then The message should be routed to the default recipient OM01247
R-GCX016E-cbl-02733 Reroute Message with Error Notification
Action Rules
📊 Business Logic Narrative
When the process 'Reroute Message with Error Notification' is invoked, and assuming that an invalid recipient error has been generated, when the system needs to handle the failed routing, the desired outcome is that the message should be rerouted with an error notification indicating the routing failure.
💻 Technical Criteria
Given An invalid recipient error has been generated
When The system needs to handle the failed routing
Then The message should be rerouted with an error notification indicating the routing failure
R-GCX016E-cbl-02736 Retry Required?
Decision Rules
📊 Business Logic Narrative
When the process 'Retry Required?' is invoked, and assuming that a message delivery failure has been detected, when the system evaluates the failure conditions, the desired outcome is that if retry is required, reroute to default recipient; if no retry is needed, complete the distribution process.
💻 Technical Criteria
Given A message delivery failure has been detected
When The system evaluates the failure conditions
Then If retry is required, reroute to default recipient; if no retry is needed, complete the distribution process
R-GCX016E-cbl-02737 Reroute to Default Recipient
Action Rules
📊 Business Logic Narrative
When the process 'Reroute to Default Recipient' is invoked, and assuming that a delivery failure has occurred and retry is required, when the system initiates the retry process, the desired outcome is that the message should be rerouted to the default recipient as a fallback delivery method.
💻 Technical Criteria
Given A delivery failure has occurred and retry is required
When The system initiates the retry process
Then The message should be rerouted to the default recipient as a fallback delivery method
R-GCX016E-cbl-02738 Route ERROR Message
Decision Rules
📊 Business Logic Narrative
When the process 'Route ERROR Message' is invoked, and assuming that a merlin message needs to be delivered, when the message type is error, the desired outcome is that the message should be routed to the 'in' destination.
💻 Technical Criteria
Given A Merlin message needs to be delivered
When The message type is ERROR
Then The message should be routed to the 'IN' destination
R-GCX016E-cbl-02739 Route INFO Message
Decision Rules
📊 Business Logic Narrative
When the process 'Route INFO Message' is invoked, and assuming that a merlin message needs to be delivered, when the message type is info, the desired outcome is that the message should be routed to 'in' destination plus sd segment merlin ids.
💻 Technical Criteria
Given A Merlin message needs to be delivered
When The message type is INFO
Then The message should be routed to 'IN' destination plus SD segment Merlin IDs
R-GCX016E-cbl-02740 Route RELEASE Message
Decision Rules
📊 Business Logic Narrative
When the process 'Route RELEASE Message' is invoked, and assuming that a merlin message needs to be delivered, when the message type is release, the desired outcome is that the message should be routed to sd segment merlin ids only.
💻 Technical Criteria
Given A Merlin message needs to be delivered
When The message type is RELEASE
Then The message should be routed to SD segment Merlin IDs only
R-GCX016E-cbl-02742 Route UNRLSE Message
Decision Rules
📊 Business Logic Narrative
When the process 'Route UNRLSE Message' is invoked, and assuming that a merlin message needs to be delivered, when the message type is unrlse, the desired outcome is that the message should be routed to om01247 plus sd cancel merlin ids.
💻 Technical Criteria
Given A Merlin message needs to be delivered
When The message type is UNRLSE
Then The message should be routed to OM01247 plus SD cancel Merlin IDs
R-GCX016E-cbl-02743 Route ARRCANL Message
Decision Rules
📊 Business Logic Narrative
When the process 'Route ARRCANL Message' is invoked, and assuming that a merlin message needs to be delivered, when the message type is arrcanl, the desired outcome is that the message should be routed to arrival cancellation recipients.
💻 Technical Criteria
Given A Merlin message needs to be delivered
When The message type is ARRCANL
Then The message should be routed to arrival cancellation recipients
R-GCX016E-cbl-02747 Reroute to Default Recipient
Process Rules
📊 Business Logic Narrative
When the process 'Reroute to Default Recipient' is invoked, and assuming that a message delivery has failed and error notification has been generated, when rerouting is attempted, the desired outcome is that the message should be sent to the default recipient.
💻 Technical Criteria
Given A message delivery has failed and error notification has been generated
When Rerouting is attempted
Then The message should be sent to the default recipient
R-GCX016E-cbl-02749 Log Delivery Status
Process Rules
📊 Business Logic Narrative
When the process 'Log Delivery Status' is invoked, and assuming that a message delivery process has completed, when the delivery outcome is determined (success, rerouted success, or failure), the desired outcome is that the system should log the delivery status.
💻 Technical Criteria
Given A message delivery process has completed
When The delivery outcome is determined (success, rerouted success, or failure)
Then The system should log the delivery status
R-GCX016E-cbl-02764 Retrieve Disposition Code
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Disposition Code' is invoked, and assuming that a disposition code identifier exists, when the system needs disposition code details for merlin reporting, the desired outcome is that the disposition code is retrieved from the disposition code table.
💻 Technical Criteria
Given A disposition code identifier exists
When The system needs disposition code details for Merlin reporting
Then The disposition code is retrieved from the disposition code table
R-GCX016E-cbl-02765 Get Disposition Description
Action Rules
📊 Business Logic Narrative
When the process 'Get Disposition Description' is invoked, and assuming that a disposition code has been retrieved from the table, when the system needs the description for merlin reporting, the desired outcome is that the disposition code description is obtained from the disposition code table.
💻 Technical Criteria
Given A disposition code has been retrieved from the table
When The system needs the description for Merlin reporting
Then The disposition code description is obtained from the disposition code table
R-GCX016E-cbl-02767 Format USCS Processing Time
Process Rules
📊 Business Logic Narrative
When the process 'Format USCS Processing Time' is invoked, and assuming that uscs processing time data is available, when the system processes uscs timing information for merlin reporting, the desired outcome is that the uscs processing time is formatted according to report standards.
💻 Technical Criteria
Given USCS processing time data is available
When The system processes USCS timing information for Merlin reporting
Then The USCS processing time is formatted according to report standards
R-GCX016E-cbl-02768 Format System Processing Time
Process Rules
📊 Business Logic Narrative
When the process 'Format System Processing Time' is invoked, and assuming that system processing time data is available, when the system processes internal timing information for merlin reporting, the desired outcome is that the system processing time is formatted according to report requirements.
💻 Technical Criteria
Given System processing time data is available
When The system processes internal timing information for Merlin reporting
Then The system processing time is formatted according to report requirements
R-GCX016E-cbl-02769 Apply Release Quantity Impact Logic
Decision Rules
📊 Business Logic Narrative
When the process 'Apply Release Quantity Impact Logic' is invoked, and assuming that a disposition code is being processed for merlin reporting, when the system evaluates the disposition code's impact on release quantities, the desired outcome is that the system determines whether the disposition code affects release quantities based on business rules.
💻 Technical Criteria
Given A disposition code is being processed for Merlin reporting
When The system evaluates the disposition code's impact on release quantities
Then The system determines whether the disposition code affects release quantities based on business rules
R-GCX016E-cbl-02771 Include Quantity Impact in Report
Process Rules
📊 Business Logic Narrative
When the process 'Include Quantity Impact in Report' is invoked, and assuming that a disposition code affects release quantities, when the system formats the merlin report, the desired outcome is that the quantity impact information is included in the report.
💻 Technical Criteria
Given A disposition code affects release quantities
When The system formats the Merlin report
Then The quantity impact information is included in the report
R-GCX016E-cbl-02772 Exclude Quantity Impact from Report
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Exclude Quantity Impact from Report', assuming that a disposition code does not affect release quantities, when the system formats the merlin report, the desired outcome is that the quantity impact information is excluded from the report.
💻 Technical Criteria
EXCLUDING A disposition code does not affect release quantities
When The system formats the Merlin report
Then The quantity impact information is excluded from the report
R-GCX016E-cbl-02773 Assemble Complete Merlin Report Fields
Process Rules
📊 Business Logic Narrative
When the process 'Assemble Complete Merlin Report Fields' is invoked, and assuming that all individual report field components have been formatted, when the system assembles the complete merlin report, the desired outcome is that all formatted fields are combined into a complete report structure.
💻 Technical Criteria
Given All individual report field components have been formatted
When The system assembles the complete Merlin report
Then All formatted fields are combined into a complete report structure
R-GCX016E-cbl-02774 Return Formatted Report Fields
Process Rules
📊 Business Logic Narrative
When the process 'Return Formatted Report Fields' is invoked, and assuming that the complete merlin report fields have been assembled, when the field management process completes, the desired outcome is that the formatted report fields are returned to the calling process.
💻 Technical Criteria
Given The complete Merlin report fields have been assembled
When The field management process completes
Then The formatted report fields are returned to the calling process
R-GCX016E-cbl-02779 Route Message to Default Recipient
Process Rules
📊 Business Logic Narrative
When the process 'Route Message to Default Recipient' is invoked, and assuming that a merlin message has been assigned the default recipient om01247 due to invalid original recipient, when the system initiates message routing, the desired outcome is that the message is routed to the default recipient om01247.
💻 Technical Criteria
Given A Merlin message has been assigned the default recipient OM01247 due to invalid original recipient
When The system initiates message routing
Then The message is routed to the default recipient OM01247
R-GCX016E-cbl-02780 Delivery Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Delivery Successful?' is invoked, and assuming that a merlin message has been routed to a recipient (either original or default), when the delivery attempt is completed, the desired outcome is that the system determines if the delivery was successful or failed.
💻 Technical Criteria
Given A Merlin message has been routed to a recipient (either original or default)
When The delivery attempt is completed
Then The system determines if the delivery was successful or failed
R-GCX016E-cbl-02783 Reroute to Alternative Default
Decision Rules
📊 Business Logic Narrative
When the process 'Reroute to Alternative Default' is invoked, and assuming that a merlin message delivery has failed to the primary recipient, when delivery failure handling is initiated, the desired outcome is that the system reroutes the message to an alternative default recipient.
💻 Technical Criteria
Given A Merlin message delivery has failed to the primary recipient
When Delivery failure handling is initiated
Then The system reroutes the message to an alternative default recipient
R-GCX016E-cbl-02784 Log Rerouting Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Rerouting Action' is invoked, and assuming that a merlin message has been rerouted to an alternative default recipient, when the rerouting action is completed, the desired outcome is that the system logs the rerouting action for audit and tracking purposes.
💻 Technical Criteria
Given A Merlin message has been rerouted to an alternative default recipient
When The rerouting action is completed
Then The system logs the rerouting action for audit and tracking purposes
R-GCX016E-cbl-02806 Set Transport Method Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Transport Method Code' is invoked, and assuming that vessel name is set in m10 segment, when the system sets transport method code, the desired outcome is that transport method code is assigned to indicate rail transportation mode.
💻 Technical Criteria
Given Vessel name is set in M10 segment
When The system sets transport method code
Then Transport method code is assigned to indicate rail transportation mode
R-GCX016E-cbl-02807 Set Country Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Country Code' is invoked, and assuming that transport method code is set in m10 segment, when the system sets country code, the desired outcome is that country code is assigned to identify train's operational country.
💻 Technical Criteria
Given Transport method code is set in M10 segment
When The system sets country code
Then Country code is assigned to identify train's operational country
R-GCX016E-cbl-02812 Set Location Information
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Location Information' is invoked, and assuming that event date and time are set in v9 segment, when the system sets location information, the desired outcome is that location fields are populated with appropriate location data for the event.
💻 Technical Criteria
Given Event date and time are set in V9 segment
When The system sets location information
Then Location fields are populated with appropriate location data for the event
R-GCX016E-cbl-02813 Set Event Description
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Event Description' is invoked, and assuming that location information is set in v9 segment, when the system sets event description, the desired outcome is that event description field is populated with explanatory text for the event.
💻 Technical Criteria
Given Location information is set in V9 segment
When The system sets event description
Then Event description field is populated with explanatory text for the event
R-GCX016E-cbl-02831 Format USCS Processing Time
Computation Rules
📊 Business Logic Narrative
When the process 'Format USCS Processing Time' is invoked, and assuming that uscs processing time information is available, when the uscs processing time formatting is executed, the desired outcome is that the uscs processing time is formatted for report display.
💻 Technical Criteria
Given USCS processing time information is available
When The USCS processing time formatting is executed
Then The USCS processing time is formatted for report display
R-GCX016E-cbl-02832 Format System Processing Time
Computation Rules
📊 Business Logic Narrative
When the process 'Format System Processing Time' is invoked, and assuming that system processing time information is available, when the system processing time formatting is executed, the desired outcome is that the system processing time is formatted for report display.
💻 Technical Criteria
Given System processing time information is available
When The system processing time formatting is executed
Then The system processing time is formatted for report display
R-GCX016E-cbl-02835 Include Quantity Impact in Report
Process Rules
📊 Business Logic Narrative
When the process 'Include Quantity Impact in Report' is invoked, and assuming that a disposition code affects release quantities, when the quantity impact inclusion process is executed, the desired outcome is that the quantity impact information is included in the merlin report fields.
💻 Technical Criteria
Given A disposition code affects release quantities
When The quantity impact inclusion process is executed
Then The quantity impact information is included in the Merlin report fields
R-GCX016E-cbl-02836 Exclude Quantity Impact from Report
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Exclude Quantity Impact from Report', assuming that a disposition code does not affect release quantities, when the quantity impact exclusion process is executed, the desired outcome is that the quantity impact information is excluded from the merlin report fields.
💻 Technical Criteria
EXCLUDING A disposition code does not affect release quantities
When The quantity impact exclusion process is executed
Then The quantity impact information is excluded from the Merlin report fields
R-GCX016E-cbl-02837 Assemble Complete Merlin Report Fields
Process Rules
📊 Business Logic Narrative
When the process 'Assemble Complete Merlin Report Fields' is invoked, and assuming that all individual report components have been formatted, when the complete report field assembly is executed, the desired outcome is that all components are assembled into complete merlin report fields ready for transmission.
💻 Technical Criteria
Given All individual report components have been formatted
When The complete report field assembly is executed
Then All components are assembled into complete Merlin report fields ready for transmission
R-GCX016E-cbl-02842 Get Location Identifiers from X4 Segments
Action Rules
📊 Business Logic Narrative
When the process 'Get Location Identifiers from X4 Segments' is invoked, and assuming that entry number information has been extracted and x4 segments are available, when the system processes x4 segments to get location identifiers, the desired outcome is that location identifiers should be extracted from x4 segments and prepared for shipment minimum segment creation.
💻 Technical Criteria
Given Entry number information has been extracted and X4 segments are available
When The system processes X4 segments to get location identifiers
Then Location identifiers should be extracted from X4 segments and prepared for shipment minimum segment creation
R-GCX016E-cbl-02843 Process Destination Station Information
Process Rules
📊 Business Logic Narrative
When the process 'Process Destination Station Information' is invoked, and assuming that location identifiers have been extracted from x4 segments, when the system processes destination station information, the desired outcome is that destination station information should be processed and prepared for u1 segment creation.
💻 Technical Criteria
Given Location identifiers have been extracted from X4 segments
When The system processes destination station information
Then Destination station information should be processed and prepared for U1 segment creation
R-GCX016E-cbl-02844 Process Key Station Information
Process Rules
📊 Business Logic Narrative
When the process 'Process Key Station Information' is invoked, and assuming that destination station information has been processed, when the system processes key station information, the desired outcome is that key station information should be processed and prepared for u1 segment creation.
💻 Technical Criteria
Given Destination station information has been processed
When The system processes key station information
Then Key station information should be processed and prepared for U1 segment creation
R-GCX016E-cbl-02848 Populate Location Identifiers in U1
Action Rules
📊 Business Logic Narrative
When the process 'Populate Location Identifiers in U1' is invoked, and assuming that entry number has been populated in u1 segment and location identifiers are available, when the system populates location identifiers in the u1 segment, the desired outcome is that location identifiers should be correctly populated in the appropriate fields of the u1 segment.
💻 Technical Criteria
Given Entry number has been populated in U1 segment and location identifiers are available
When The system populates location identifiers in the U1 segment
Then Location identifiers should be correctly populated in the appropriate fields of the U1 segment
🔁 EDI, Status & Database 1087 logic blocks
R-GCX016E-cbl-00001 1:MQ Message Retrieval
Process Rules
📊 Business Logic Narrative
When the process '1:MQ Message Retrieval' is invoked, and assuming that the system needs to process messages from gc350.exp.input queue, when message retrieval is initiated, the desired outcome is that messages are retrieved from queue and completion codes are evaluated to determine message availability status.
💻 Technical Criteria
Given The system needs to process messages from GC350.EXP.INPUT queue
When Message retrieval is initiated
Then Messages are retrieved from queue and completion codes are evaluated to determine message availability status
R-GCX016E-cbl-00002 Messages Available?
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Messages Available?', assuming that messages have been retrieved from the queue with completion codes, when completion code is not ok and reason code is 2033, the desired outcome is that set message not available flag.
💻 Technical Criteria
EXCLUDING Messages have been retrieved from the queue with completion codes
When Completion code is not OK and reason code is 2033
Then Set message not available flag
R-GCX016E-cbl-00003 Messages Available?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Messages Available?', assuming that message completion is ok, when backout count is not zero, the desired outcome is that skip message and set skip message flag.
💻 Technical Criteria
EXCLUDING Message completion is OK
When Backout count is not zero
Then Skip message and set skip message flag
R-GCX016E-cbl-00004 Messages Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Messages Available?' is invoked, and assuming that message completion is ok, when backout count is zero, the desired outcome is that set good message found flag for processing.
💻 Technical Criteria
Given Message completion is OK
When Backout count is zero
Then Set good message found flag for processing
R-GCX016E-cbl-00005 91:Message Array Initialization
Process Rules
📊 Business Logic Narrative
When the process '91:Message Array Initialization' is invoked, and assuming that valid messages are available for processing, when message id is gcw016, the desired outcome is that process messages directly varying ws-line from 1 until max entries or end found.
💻 Technical Criteria
Given Valid messages are available for processing
When Message ID is GCW016
Then Process messages directly varying WS-LINE from 1 until max entries or end found
R-GCX016E-cbl-00008 2:Train Identification and Validation
Validation Rules
📊 Business Logic Narrative
When the process '2:Train Identification and Validation' is invoked, and assuming that m10 segment contains vessel name information, when vessel name starts with 'train' or 'day', the desired outcome is that continue processing without additional validation.
💻 Technical Criteria
Given M10 segment contains vessel name information
When Vessel name starts with 'TRAIN' or 'DAY'
Then Continue processing without additional validation
R-GCX016E-cbl-00009 2:Train Identification and Validation
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process '2:Train Identification and Validation', assuming that vessel name does not start with 'train' or 'day', when train lookup is performed against train list, the desired outcome is that if train not found, generate error message to merlin system.
💻 Technical Criteria
EXCLUDING Vessel name does not start with 'TRAIN' or 'DAY'
When Train lookup is performed against train list
Then If train not found, generate error message to Merlin system
R-GCX016E-cbl-00010 3:Train Hold Processing - HMI
Action Rules
📊 Business Logic Narrative
When the process '3:Train Hold Processing - HMI' is invoked, and assuming that v9 segment contains event code hmi, when train hold event is processed, the desired outcome is that set train held status and log hold message to merlin system.
💻 Technical Criteria
Given V9 segment contains event code HMI
When Train hold event is processed
Then Set train held status and log hold message to Merlin system
R-GCX016E-cbl-00011 4:Train Hold Release Processing - HRE
Action Rules
📊 Business Logic Narrative
When the process '4:Train Hold Release Processing - HRE' is invoked, and assuming that v9 segment contains event code hre, when train hold release event is processed, the desired outcome is that remove train hold status and log release message to merlin system.
💻 Technical Criteria
Given V9 segment contains event code HRE
When Train hold release event is processed
Then Remove train hold status and log release message to Merlin system
R-GCX016E-cbl-00012 5:Train Arrival Processing - POD/AAD
Action Rules
📊 Business Logic Narrative
When the process '5:Train Arrival Processing - POD/AAD' is invoked, and assuming that v9 segment contains event code pod or aad, when train arrival event is processed, the desired outcome is that process train arrival and update arrival status in system.
💻 Technical Criteria
Given V9 segment contains event code POD or AAD
When Train arrival event is processed
Then Process train arrival and update arrival status in system
R-GCX016E-cbl-00013 6:Train Review Complete Processing - RC
Action Rules
📊 Business Logic Narrative
When the process '6:Train Review Complete Processing - RC' is invoked, and assuming that v9 segment contains event code rc, when review complete event is processed, the desired outcome is that set review completed status for the train.
💻 Technical Criteria
Given V9 segment contains event code RC
When Review complete event is processed
Then Set review completed status for the train
R-GCX016E-cbl-00014 7:Train Not Arrived Processing - OCA
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process '7:Train Not Arrived Processing - OCA', assuming that v9 segment contains event code oca, when train not arrived event is processed, the desired outcome is that handle arrival cancellation for the train.
💻 Technical Criteria
EXCLUDING V9 segment contains event code OCA
When Train not arrived event is processed
Then Handle arrival cancellation for the train
R-GCX016E-cbl-00015 8:Train Arrival Cancellation - COC
Action Rules
📊 Business Logic Narrative
When the process '8:Train Arrival Cancellation - COC' is invoked, and assuming that v9 segment contains event code coc, when train arrival cancellation is processed, the desired outcome is that process arrival cancellation with different logic based on current arrival status.
💻 Technical Criteria
Given V9 segment contains event code COC
When Train arrival cancellation is processed
Then Process arrival cancellation with different logic based on current arrival status
R-GCX016E-cbl-00016 9:Train Lock Processing - LCK
Action Rules
📊 Business Logic Narrative
When the process '9:Train Lock Processing - LCK' is invoked, and assuming that v9 segment contains event code lck, when train lock event is processed, the desired outcome is that set train locked status.
💻 Technical Criteria
Given V9 segment contains event code LCK
When Train lock event is processed
Then Set train locked status
R-GCX016E-cbl-00017 10:Train Unlock Processing - ULC
Action Rules
📊 Business Logic Narrative
When the process '10:Train Unlock Processing - ULC' is invoked, and assuming that v9 segment contains event code ulc, when train unlock event is processed and train is currently locked, the desired outcome is that remove train lock status.
💻 Technical Criteria
Given V9 segment contains event code ULC
When Train unlock event is processed and train is currently locked
Then Remove train lock status
R-GCX016E-cbl-00018 11:Train Seizure Processing - SEI
Action Rules
📊 Business Logic Narrative
When the process '11:Train Seizure Processing - SEI' is invoked, and assuming that v9 segment contains event code sei, when train seizure event is processed, the desired outcome is that set train seized status.
💻 Technical Criteria
Given V9 segment contains event code SEI
When Train seizure event is processed
Then Set train seized status
R-GCX016E-cbl-00019 12:Train Seizure Release Processing - SER
Action Rules
📊 Business Logic Narrative
When the process '12:Train Seizure Release Processing - SER' is invoked, and assuming that v9 segment contains event code ser, when train seizure release event is processed, the desired outcome is that remove train seize status.
💻 Technical Criteria
Given V9 segment contains event code SER
When Train seizure release event is processed
Then Remove train seize status
R-GCX016E-cbl-00020 13:Train All Clear Processing - CAE
Action Rules
📊 Business Logic Narrative
When the process '13:Train All Clear Processing - CAE' is invoked, and assuming that v9 segment contains event code cae, when train all clear event is processed, the desired outcome is that set all clear status for the train.
💻 Technical Criteria
Given V9 segment contains event code CAE
When Train all clear event is processed
Then Set all clear status for the train
R-GCX016E-cbl-00031 43:Disposition Code Table Lookup
Validation Rules
📊 Business Logic Narrative
When the process '43:Disposition Code Table Lookup' is invoked, and assuming that disposition code needs validation, when dc table lookup is performed, the desired outcome is that retrieve disposition code details from dc table.
💻 Technical Criteria
Given Disposition code needs validation
When DC table lookup is performed
Then Retrieve disposition code details from DC table
R-GCX016E-cbl-00032 44:Duplicate Disposition Code Detection
Validation Rules
📊 Business Logic Narrative
When the process '44:Duplicate Disposition Code Detection' is invoked, and assuming that status array contains existing disposition codes, when new disposition code is being added, the desired outcome is that search existing status array for matching disposition codes and check entry numbers and quantities for exact matches.
💻 Technical Criteria
Given Status array contains existing disposition codes
When New disposition code is being added
Then Search existing status array for matching disposition codes and check entry numbers and quantities for exact matches
R-GCX016E-cbl-00033 45:Counterpart Disposition Code Removal
Action Rules
📊 Business Logic Narrative
When the process '45:Counterpart Disposition Code Removal' is invoked, and assuming that new disposition code has counterpart logic defined, when counterpart disposition codes exist in status array, the desired outcome is that remove counterpart disposition codes from status array.
💻 Technical Criteria
Given New disposition code has counterpart logic defined
When Counterpart disposition codes exist in status array
Then Remove counterpart disposition codes from status array
R-GCX016E-cbl-00036 26:SNP Processing
Action Rules
📊 Business Logic Narrative
When the process '26:SNP Processing' is invoked, and assuming that disposition code is snp, when snp processing is initiated, the desired outcome is that process snp disposition with specific business logic.
💻 Technical Criteria
Given Disposition code is SNP
When SNP processing is initiated
Then Process SNP disposition with specific business logic
R-GCX016E-cbl-00039 58:Individual Status Analysis
Computation Rules
📊 Business Logic Narrative
When the process '58:Individual Status Analysis' is invoked, and assuming that status array contains multiple disposition codes, when individual status analysis is performed, the desired outcome is that analyze each status code for hold, release, ptt, and other status flags.
💻 Technical Criteria
Given Status array contains multiple disposition codes
When Individual status analysis is performed
Then Analyze each status code for hold, release, PTT, and other status flags
R-GCX016E-cbl-00046 176:Foreign Manifest Building from M10 Segments
Process Rules
📊 Business Logic Narrative
When the process '176:Foreign Manifest Building from M10 Segments' is invoked, and assuming that m10 segments contain foreign manifest information, when foreign manifest building is initiated, the desired outcome is that build foreign manifest structure from m10 segment data.
💻 Technical Criteria
Given M10 segments contain foreign manifest information
When Foreign manifest building is initiated
Then Build foreign manifest structure from M10 segment data
R-GCX016E-cbl-00047 76:Generic Table I/O Interface
Action Rules
📊 Business Logic Narrative
When the process '76:Generic Table I/O Interface' is invoked, and assuming that table operations are required for various business processes, when generic table interface is called, the desired outcome is that perform table read/write operations with appropriate error handling.
💻 Technical Criteria
Given Table operations are required for various business processes
When Generic table interface is called
Then Perform table read/write operations with appropriate error handling
R-GCX016E-cbl-00053 85:CIH Hold Email Notification
Action Rules
📊 Business Logic Narrative
When the process '85:CIH Hold Email Notification' is invoked, and assuming that email notification fails to primary recipients, when email failure is detected, the desired outcome is that resend email to backup recipients (aei9999, om01247).
💻 Technical Criteria
Given Email notification fails to primary recipients
When Email failure is detected
Then Resend email to backup recipients (AEI9999, OM01247)
R-GCX016E-cbl-00063 Queue Open Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Queue Open Successful?' is invoked, and assuming that an attempt to open gc350.exp.input queue has been made, when queue open operation completes, the desired outcome is that if queue opens successfully, proceed to message loading; otherwise set message not available.
💻 Technical Criteria
Given An attempt to open GC350.EXP.INPUT queue has been made
When Queue open operation completes
Then If queue opens successfully, proceed to message loading; otherwise set message not available
R-GCX016E-cbl-00070 Continue Loading?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Continue Loading?', assuming that a message processing result has been determined (good, skip, or not available), when loading continuation is evaluated, the desired outcome is that if more messages needed and conditions allow, continue loading; otherwise complete message loading process.
💻 Technical Criteria
EXCLUDING A message processing result has been determined (good, skip, or not available)
When Loading continuation is evaluated
Then If more messages needed and conditions allow, continue loading; otherwise complete message loading process
R-GCX016E-cbl-02867 Evaluate MQ Completion Code
Validation Rules
📊 Business Logic Narrative
When the process 'Evaluate MQ Completion Code' is invoked, and assuming that an mqget operation has been executed, when the mq completion code is evaluated, the desired outcome is that if completion code indicates success, proceed to message validation; if no message available, set message not available flag; if other error, handle error condition.
💻 Technical Criteria
Given An MQGET operation has been executed
When The MQ completion code is evaluated
Then If completion code indicates success, proceed to message validation; if no message available, set message not available flag; if other error, handle error condition
R-GCX016E-cbl-02869 Set Good Message Flag
Decision Rules
📊 Business Logic Narrative
When the process 'Set Good Message Flag' is invoked, and assuming that a message has been retrieved successfully and backout count is zero, when message classification is performed, the desired outcome is that set good message flag to indicate the message is ready for business processing.
💻 Technical Criteria
Given A message has been retrieved successfully and backout count is zero
When Message classification is performed
Then Set good message flag to indicate the message is ready for business processing
R-GCX016E-cbl-02870 Set Skip Message Flag - High Backout Count
Decision Rules
📊 Business Logic Narrative
When the process 'Set Skip Message Flag - High Backout Count' is invoked, and assuming that a message has been retrieved successfully but backout count is greater than zero, when message classification is performed, the desired outcome is that set skip message flag to prevent processing of potentially problematic message.
💻 Technical Criteria
Given A message has been retrieved successfully but backout count is greater than zero
When Message classification is performed
Then Set skip message flag to prevent processing of potentially problematic message
R-GCX016E-cbl-02872 Handle MQ Error Condition
Action Rules
📊 Business Logic Narrative
When the process 'Handle MQ Error Condition' is invoked, and assuming that an mqget operation is executed, when the completion code indicates an error other than 'no message available', the desired outcome is that handle the mq error condition appropriately based on the specific error type.
💻 Technical Criteria
Given An MQGET operation is executed
When The completion code indicates an error other than 'no message available'
Then Handle the MQ error condition appropriately based on the specific error type
R-GCX016E-cbl-02873 Message Classification
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Message Classification', assuming that a message has been classified as good, skip, or not available, when processing decision is made, the desired outcome is that if good message, proceed to business processing; if skip message, continue to next message; if no message available, end message loading process.
💻 Technical Criteria
EXCLUDING A message has been classified as good, skip, or not available
When Processing decision is made
Then If good message, proceed to business processing; if skip message, continue to next message; if no message available, end message loading process
R-GCX016E-cbl-00071 Extract Train ID from Vessel Name
Validation Rules
📊 Business Logic Narrative
When the process 'Extract Train ID from Vessel Name' is invoked, and assuming that a vessel name is provided in the m10 segment, when the vessel name starts with 'train' or 'day', the desired outcome is that the system continues with train processing without additional validation.
💻 Technical Criteria
Given A vessel name is provided in the M10 segment
When The vessel name starts with 'TRAIN' or 'DAY'
Then The system continues with train processing without additional validation
R-GCX016E-cbl-00072 Query GCWTL Train List Segments
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Query GCWTL Train List Segments', assuming that a vessel name that does not start with 'train' or 'day', when the system searches the train list using gccutrio, the desired outcome is that if the train is found in gcwtl segments, processing continues; if not found, an error is generated.
💻 Technical Criteria
EXCLUDING A vessel name that does not start with 'TRAIN' or 'DAY'
When The system searches the train list using GCCUTRIO
Then If the train is found in GCWTL segments, processing continues; if not found, an error is generated
R-GCX016E-cbl-00073 Generate Train Not Found Error
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Train Not Found Error', assuming that a train lookup has been performed, when the train is not found in the gcwtl train list segments, the desired outcome is that the system generates a train not found error message for merlin notification.
💻 Technical Criteria
EXCLUDING A train lookup has been performed
When The train is not found in the GCWTL train list segments
Then The system generates a train not found error message for Merlin notification
R-GCX016E-cbl-00075 Continue with Train Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue with Train Processing' is invoked, and assuming that train validation has been completed, when the train is either a valid train/day named vessel or found in the train list, the desired outcome is that the system sets the train found flag and continues with subsequent train processing operations.
💻 Technical Criteria
Given Train validation has been completed
When The train is either a valid TRAIN/DAY named vessel or found in the train list
Then The system sets the train found flag and continues with subsequent train processing operations
R-GCX016E-cbl-00076 Call GCCUTRIO to Lookup Train
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Call GCCUTRIO to Lookup Train', assuming that a vessel name that requires train validation, when the vessel name does not match train or day naming patterns, the desired outcome is that the system calls gccutrio service to lookup the train in external train records.
💻 Technical Criteria
EXCLUDING A vessel name that requires train validation
When The vessel name does not match TRAIN or DAY naming patterns
Then The system calls GCCUTRIO service to lookup the train in external train records
R-GCX016E-cbl-02874 Extract Train ID from Vessel Name
Process Rules
📊 Business Logic Narrative
When the process 'Extract Train ID from Vessel Name' is invoked, and assuming that an m10 segment contains a vessel name field, when the system processes the m10 segment, the desired outcome is that the train id is extracted from the vessel name for database lookup.
💻 Technical Criteria
Given An M10 segment contains a vessel name field
When The system processes the M10 segment
Then The train ID is extracted from the vessel name for database lookup
R-GCX016E-cbl-02875 Call GCCUTRIO Database Lookup
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCUTRIO Database Lookup' is invoked, and assuming that a train id has been extracted from the vessel name, when the system initiates train lookup, the desired outcome is that gccutrio database lookup is called to search for train information.
💻 Technical Criteria
Given A train ID has been extracted from the vessel name
When The system initiates train lookup
Then GCCUTRIO database lookup is called to search for train information
R-GCX016E-cbl-02876 Train Found in System?
Validation Rules
📊 Business Logic Narrative
When the process 'Train Found in System?' is invoked, and assuming that a database lookup has been performed for a train id, when the lookup results are evaluated, the desired outcome is that if train is found, retrieve train information; if not found, generate train not found error.
💻 Technical Criteria
Given A database lookup has been performed for a train ID
When The lookup results are evaluated
Then If train is found, retrieve train information; if not found, generate train not found error
R-GCX016E-cbl-02877 Retrieve Train Information
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Train Information' is invoked, and assuming that a train exists in the database, when train lookup is successful, the desired outcome is that complete train information is retrieved from the database.
💻 Technical Criteria
Given A train exists in the database
When Train lookup is successful
Then Complete train information is retrieved from the database
R-GCX016E-cbl-02878 Is CPRS Train?
Decision Rules
📊 Business Logic Narrative
When the process 'Is CPRS Train?' is invoked, and assuming that train information has been retrieved from the database, when the system evaluates train type, the desired outcome is that if train is cprs type, apply cprs special processing; otherwise proceed with standard processing.
💻 Technical Criteria
Given Train information has been retrieved from the database
When The system evaluates train type
Then If train is CPRS type, apply CPRS special processing; otherwise proceed with standard processing
R-GCX016E-cbl-02880 Set Train Found Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Train Found Flag' is invoked, and assuming that train information has been successfully retrieved and processed, when train processing is completed, the desired outcome is that train found flag is set to indicate successful train identification.
💻 Technical Criteria
Given Train information has been successfully retrieved and processed
When Train processing is completed
Then Train found flag is set to indicate successful train identification
R-GCX016E-cbl-02881 Generate Train Not Found Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Train Not Found Error', assuming that a train id does not exist in the database, when train lookup fails, the desired outcome is that a train not found error is generated for error handling.
💻 Technical Criteria
EXCLUDING A train ID does not exist in the database
When Train lookup fails
Then A train not found error is generated for error handling
R-GCX016E-cbl-02882 Create Merlin Error Message
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Create Merlin Error Message', assuming that a train not found error has been generated, when error message creation is triggered, the desired outcome is that a merlin error message is created to notify relevant parties of the train lookup failure.
💻 Technical Criteria
EXCLUDING A train not found error has been generated
When Error message creation is triggered
Then A Merlin error message is created to notify relevant parties of the train lookup failure
R-GCX016E-cbl-03130 Apply CPRS Naming Conventions
Process Rules
📊 Business Logic Narrative
When the process 'Apply CPRS Naming Conventions' is invoked, and assuming that a train has been identified as a cprs train, when the system processes the train identification, the desired outcome is that the system applies cprs naming conventions and formats the train id according to canadian pacific railway standards.
💻 Technical Criteria
Given A train has been identified as a CPRS train
When The system processes the train identification
Then The system applies CPRS naming conventions and formats the train ID according to Canadian Pacific Railway standards
R-GCX016E-cbl-03131 Validate CPRS Train Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate CPRS Train Format' is invoked, and assuming that a cprs train id has been formatted according to naming conventions, when the system validates the train format against cprs standards, the desired outcome is that the system confirms the train id meets canadian pacific railway formatting requirements or flags format violations.
💻 Technical Criteria
Given A CPRS train ID has been formatted according to naming conventions
When The system validates the train format against CPRS standards
Then The system confirms the train ID meets Canadian Pacific Railway formatting requirements or flags format violations
R-GCX016E-cbl-03132 CPRS Train Found in System?
Validation Rules
📊 Business Logic Narrative
When the process 'CPRS Train Found in System?' is invoked, and assuming that a validated cprs train id is ready for processing, when the system searches the gcwtl train data for the cprs train, the desired outcome is that the system either finds the train record and proceeds with normal processing or generates a train not found error.
💻 Technical Criteria
Given A validated CPRS train ID is ready for processing
When The system searches the GCWTL train data for the CPRS train
Then The system either finds the train record and proceeds with normal processing or generates a train not found error
R-GCX016E-cbl-00077 Validate Train ID from M10 Segment
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Train ID from M10 Segment' is invoked, and assuming that a v9 segment with hmi disposition code is received, when the system processes the m10 segment to extract train identification, the desired outcome is that the train id is validated and made available for subsequent hold processing.
💻 Technical Criteria
Given A V9 segment with HMI disposition code is received
When The system processes the M10 segment to extract train identification
Then The train ID is validated and made available for subsequent hold processing
R-GCX016E-cbl-00079 Retrieve Train Record from GCWTL
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Train Record from GCWTL' is invoked, and assuming that a train exists in the gcwtl train list segments, when the system needs to process a hold disposition for the train, the desired outcome is that the complete train record is retrieved from gcwtl for status updates.
💻 Technical Criteria
Given A train exists in the GCWTL train list segments
When The system needs to process a hold disposition for the train
Then The complete train record is retrieved from GCWTL for status updates
R-GCX016E-cbl-00080 Set Train Hold Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Train Hold Status Flag' is invoked, and assuming that a valid train record has been retrieved from gcwtl, when an hmi disposition code is being processed, the desired outcome is that the train hold status flag is set to indicate the train is held.
💻 Technical Criteria
Given A valid train record has been retrieved from GCWTL
When An HMI disposition code is being processed
Then The train hold status flag is set to indicate the train is held
R-GCX016E-cbl-00081 Update Train Status in Database
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Status in Database' is invoked, and assuming that the train hold status flag has been set, when the system completes hold processing, the desired outcome is that the updated train status is written back to the gcwtl database.
💻 Technical Criteria
Given The train hold status flag has been set
When The system completes hold processing
Then The updated train status is written back to the GCWTL database
R-GCX016E-cbl-00082 Log Hold Action with Timestamp
Process Rules
📊 Business Logic Narrative
When the process 'Log Hold Action with Timestamp' is invoked, and assuming that a train has been successfully placed on hold, when the hold status has been updated in the database, the desired outcome is that a log entry is created with the hold action and current timestamp for audit purposes.
💻 Technical Criteria
Given A train has been successfully placed on hold
When The hold status has been updated in the database
Then A log entry is created with the hold action and current timestamp for audit purposes
R-GCX016E-cbl-00083 Generate Merlin Hold Notification Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Merlin Hold Notification Message' is invoked, and assuming that a train hold action has been logged, when the system needs to notify stakeholders of the hold, the desired outcome is that a merlin hold notification message is generated with train details and hold information.
💻 Technical Criteria
Given A train hold action has been logged
When The system needs to notify stakeholders of the hold
Then A Merlin hold notification message is generated with train details and hold information
R-GCX016E-cbl-00084 Send Hold Notification to Recipients
Action Rules
📊 Business Logic Narrative
When the process 'Send Hold Notification to Recipients' is invoked, and assuming that a merlin hold notification message has been generated, when the system processes notification distribution, the desired outcome is that the hold notification is sent to all designated recipients through the merlin message system.
💻 Technical Criteria
Given A Merlin hold notification message has been generated
When The system processes notification distribution
Then The hold notification is sent to all designated recipients through the Merlin message system
R-GCX016E-cbl-00085 Generate Train Not Found Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Train Not Found Error', assuming that a train id from m10 segment does not exist in gcwtl train list, when the system attempts to process an hmi hold disposition, the desired outcome is that a train not found error is generated for the invalid train id.
💻 Technical Criteria
EXCLUDING A train ID from M10 segment does not exist in GCWTL train list
When The system attempts to process an HMI hold disposition
Then A train not found error is generated for the invalid train ID
R-GCX016E-cbl-00086 Send Error Message to Default Recipient
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Send Error Message to Default Recipient', assuming that a train not found error has been generated, when the system needs to notify about the processing error, the desired outcome is that the error message is sent to the default recipient for error handling and resolution.
💻 Technical Criteria
EXCLUDING A train not found error has been generated
When The system needs to notify about the processing error
Then The error message is sent to the default recipient for error handling and resolution
R-GCX016E-cbl-00091 Process Train-Level Hold Release
Decision Rules
📊 Business Logic Narrative
When the process 'Process Train-Level Hold Release' is invoked, and assuming that an hre disposition code is received and no vid segment is present in the message, when the system processes the hold release event, the desired outcome is that the system processes train-level hold release for the entire train.
💻 Technical Criteria
Given An HRE disposition code is received AND no VID segment is present in the message
When The system processes the hold release event
Then The system processes train-level hold release for the entire train
R-GCX016E-cbl-00092 Remove Train Hold Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Remove Train Hold Status Flag' is invoked, and assuming that train-level hold release is being processed, when the system processes the train hold release, the desired outcome is that the train hold status flag is removed from the train record.
💻 Technical Criteria
Given Train-level hold release is being processed
When The system processes the train hold release
Then The train hold status flag is removed from the train record
R-GCX016E-cbl-00094 Update Train Status in Database
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Status in Database' is invoked, and assuming that hold release action has been logged, when the system completes hold release processing, the desired outcome is that the train status is updated in the database with the current hold release information.
💻 Technical Criteria
Given Hold release action has been logged
When The system completes hold release processing
Then The train status is updated in the database with the current hold release information
R-GCX016E-cbl-00095 Generate Merlin Notification Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Merlin Notification Message' is invoked, and assuming that train status has been updated in the database, when the hold release processing is nearly complete, the desired outcome is that a merlin notification message is generated containing hold release details.
💻 Technical Criteria
Given Train status has been updated in the database
When The hold release processing is nearly complete
Then A Merlin notification message is generated containing hold release details
R-GCX016E-cbl-00096 Send Hold Release Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send Hold Release Notification' is invoked, and assuming that a merlin notification message has been generated, when the system is ready to send notifications, the desired outcome is that the hold release notification is transmitted to the designated recipients.
💻 Technical Criteria
Given A Merlin notification message has been generated
When The system is ready to send notifications
Then The hold release notification is transmitted to the designated recipients
R-GCX016E-cbl-00104 Set Train Arrived Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Train Arrived Status Flag' is invoked, and assuming that the train arrival date has been successfully assigned, when the system updates train status information, the desired outcome is that set the train arrived status flag to indicate the train has completed arrival processing.
💻 Technical Criteria
Given The train arrival date has been successfully assigned
When The system updates train status information
Then Set the train arrived status flag to indicate the train has completed arrival processing
R-GCX016E-cbl-00107 Send Email Notifications
Action Rules
📊 Business Logic Narrative
When the process 'Send Email Notifications' is invoked, and assuming that aei arrival messages have been sent, when the system processes notification distribution, the desired outcome is that send email notifications to configured recipients about the train arrival event.
💻 Technical Criteria
Given AEI arrival messages have been sent
When The system processes notification distribution
Then Send email notifications to configured recipients about the train arrival event
R-GCX016E-cbl-00108 Log Train Arrival Action
Action Rules
📊 Business Logic Narrative
When the process 'Log Train Arrival Action' is invoked, and assuming that k1 remark message processing for trains has been completed, when the system finalizes arrival processing, the desired outcome is that create a log entry documenting the train arrival action with relevant details.
💻 Technical Criteria
Given K1 remark message processing for trains has been completed
When The system finalizes arrival processing
Then Create a log entry documenting the train arrival action with relevant details
R-GCX016E-cbl-00109 Update Train Status in Database
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Status in Database' is invoked, and assuming that the train arrival action has been logged, when the system commits status changes, the desired outcome is that update the train status information in the database to reflect the completed arrival.
💻 Technical Criteria
Given The train arrival action has been logged
When The system commits status changes
Then Update the train status information in the database to reflect the completed arrival
R-GCX016E-cbl-00110 Generate Merlin Arrival Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Merlin Arrival Notification' is invoked, and assuming that the train status has been updated in the database, when the system generates external notifications, the desired outcome is that create and send a merlin arrival notification message to inform the merlin system of the train arrival.
💻 Technical Criteria
Given The train status has been updated in the database
When The system generates external notifications
Then Create and send a Merlin arrival notification message to inform the Merlin system of the train arrival
R-GCX016E-cbl-00111 Validate RC Disposition Code
Validation Rules
📊 Business Logic Narrative
When the process 'Validate RC Disposition Code' is invoked, and assuming that a v9 segment is received with a disposition code, when the system processes the v9 segment, the desired outcome is that the disposition code must be 'rc' to proceed with review complete processing.
💻 Technical Criteria
Given A V9 segment is received with a disposition code
When The system processes the V9 segment
Then The disposition code must be 'RC' to proceed with review complete processing
R-GCX016E-cbl-00115 Set Review Complete Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Review Complete Flag' is invoked, and assuming that a valid rc disposition code has been processed for a train, when the system updates the train status, the desired outcome is that the review complete flag is set to indicate completion of the review process.
💻 Technical Criteria
Given A valid RC disposition code has been processed for a train
When The system updates the train status
Then The review complete flag is set to indicate completion of the review process
R-GCX016E-cbl-00116 Update Train Status in GCWTL
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Status in GCWTL' is invoked, and assuming that the review complete flag has been set for a train, when the system updates the train records, the desired outcome is that the train status is updated in the gcwtl train list segments with the new review complete status.
💻 Technical Criteria
Given The review complete flag has been set for a train
When The system updates the train records
Then The train status is updated in the GCWTL train list segments with the new review complete status
R-GCX016E-cbl-00117 Log Review Complete Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Review Complete Action' is invoked, and assuming that a train review complete action has been processed, when the system completes the status update, the desired outcome is that the review complete action is logged with appropriate details for audit purposes.
💻 Technical Criteria
Given A train review complete action has been processed
When The system completes the status update
Then The review complete action is logged with appropriate details for audit purposes
R-GCX016E-cbl-00118 Generate Merlin Notification Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Merlin Notification Message' is invoked, and assuming that a train review complete action has been logged, when the system prepares notifications, the desired outcome is that a merlin notification message is generated containing the review complete details.
💻 Technical Criteria
Given A train review complete action has been logged
When The system prepares notifications
Then A Merlin notification message is generated containing the review complete details
R-GCX016E-cbl-00119 K1 Remark Message Present?
Decision Rules
📊 Business Logic Narrative
When the process 'K1 Remark Message Present?' is invoked, and assuming that a review complete notification is being prepared, when the system checks for additional remark information, the desired outcome is that if k1 remark messages are present, they are processed for inclusion in the notification, otherwise the notification proceeds without remarks.
💻 Technical Criteria
Given A review complete notification is being prepared
When The system checks for additional remark information
Then If K1 remark messages are present, they are processed for inclusion in the notification, otherwise the notification proceeds without remarks
R-GCX016E-cbl-00120 Process K1 Free-Form Text
Process Rules
📊 Business Logic Narrative
When the process 'Process K1 Free-Form Text' is invoked, and assuming that k1 remark messages are present in the transaction, when the system processes the k1 segments, the desired outcome is that the free-form text from k1 segments is extracted and formatted for inclusion in notifications.
💻 Technical Criteria
Given K1 remark messages are present in the transaction
When The system processes the K1 segments
Then The free-form text from K1 segments is extracted and formatted for inclusion in notifications
R-GCX016E-cbl-00121 Add K1 Comments to Notification
Action Rules
📊 Business Logic Narrative
When the process 'Add K1 Comments to Notification' is invoked, and assuming that k1 free-form text has been processed, when the system builds the notification message, the desired outcome is that the processed k1 comments are added to the notification message content.
💻 Technical Criteria
Given K1 free-form text has been processed
When The system builds the notification message
Then The processed K1 comments are added to the notification message content
R-GCX016E-cbl-00122 Send Review Complete Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send Review Complete Notification' is invoked, and assuming that a complete review complete notification message has been prepared, when the system sends the notification, the desired outcome is that the notification is transmitted through the merlin messaging system to appropriate recipients.
💻 Technical Criteria
Given A complete review complete notification message has been prepared
When The system sends the notification
Then The notification is transmitted through the Merlin messaging system to appropriate recipients
R-GCX016E-cbl-00123 Update Train Processing Status
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Processing Status' is invoked, and assuming that the review complete notification has been sent, when the system finalizes the review complete processing, the desired outcome is that the train processing status is updated to indicate successful completion of review complete processing.
💻 Technical Criteria
Given The review complete notification has been sent
When The system finalizes the review complete processing
Then The train processing status is updated to indicate successful completion of review complete processing
R-GCX016E-cbl-00124 Validate Train ID from M10 Segment
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Train ID from M10 Segment' is invoked, and assuming that a v9 segment with oca disposition code is received, when the system processes the m10 segment for train identification, the desired outcome is that the train id must be extracted and validated from the m10 segment data.
💻 Technical Criteria
Given A V9 segment with OCA disposition code is received
When The system processes the M10 segment for train identification
Then The train ID must be extracted and validated from the M10 segment data
R-GCX016E-cbl-00125 Train Found in System?
Decision Rules
📊 Business Logic Narrative
When the process 'Train Found in System?' is invoked, and assuming that a train id has been extracted from the m10 segment, when the system searches the train list database, the desired outcome is that if the train is not found in the system, processing should branch to warning generation, otherwise continue to status checking.
💻 Technical Criteria
Given A train ID has been extracted from the M10 segment
When The system searches the train list database
Then If the train is not found in the system, processing should branch to warning generation, otherwise continue to status checking
R-GCX016E-cbl-00126 Check Current Train Status
Action Rules
📊 Business Logic Narrative
When the process 'Check Current Train Status' is invoked, and assuming that a valid train id exists in the system, when the system accesses the train status information, the desired outcome is that the current train status must be retrieved for arrival status evaluation.
💻 Technical Criteria
Given A valid train ID exists in the system
When The system accesses the train status information
Then The current train status must be retrieved for arrival status evaluation
R-GCX016E-cbl-00127 Train Already Arrived?
Decision Rules
📊 Business Logic Narrative
When the process 'Train Already Arrived?' is invoked, and assuming that the current train status has been retrieved, when the system evaluates the train's arrival status, the desired outcome is that if the train has already arrived, generate a warning; if not arrived, proceed with oca disposition processing.
💻 Technical Criteria
Given The current train status has been retrieved
When The system evaluates the train's arrival status
Then If the train has already arrived, generate a warning; if not arrived, proceed with OCA disposition processing
R-GCX016E-cbl-00128 Generate Train Not Arrived Warning
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Train Not Arrived Warning', assuming that either the train is not found in the system or the train has already arrived, when an oca disposition code is processed, the desired outcome is that a train not arrived warning message must be generated and logged.
💻 Technical Criteria
EXCLUDING Either the train is not found in the system OR the train has already arrived
When An OCA disposition code is processed
Then A train not arrived warning message must be generated and logged
R-GCX016E-cbl-00129 Log OCA Disposition Action
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log OCA Disposition Action', assuming that a train exists in the system and has not yet arrived, when an oca disposition code is processed, the desired outcome is that the oca disposition action must be logged in the system audit trail.
💻 Technical Criteria
EXCLUDING A train exists in the system and has not yet arrived
When An OCA disposition code is processed
Then The OCA disposition action must be logged in the system audit trail
R-GCX016E-cbl-00130 Set Train Re-Arrival Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Train Re-Arrival Flag' is invoked, and assuming that an oca disposition has been successfully logged for a non-arrived train, when the system processes the arrival cancellation, the desired outcome is that a re-arrival flag must be set to enable future arrival processing for this train.
💻 Technical Criteria
Given An OCA disposition has been successfully logged for a non-arrived train
When The system processes the arrival cancellation
Then A re-arrival flag must be set to enable future arrival processing for this train
R-GCX016E-cbl-00131 Update Train Status to Not Arrived
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Status to Not Arrived' is invoked, and assuming that the re-arrival flag has been set for the train, when the system updates the train status database, the desired outcome is that the train status must be changed to 'not arrived' to reflect the cancelled arrival.
💻 Technical Criteria
Given The re-arrival flag has been set for the train
When The system updates the train status database
Then The train status must be changed to 'Not Arrived' to reflect the cancelled arrival
R-GCX016E-cbl-00132 Create Merlin Notification Message
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Create Merlin Notification Message', assuming that either a warning condition exists or the train status has been updated to not arrived, when the system prepares notifications, the desired outcome is that a merlin notification message must be created with appropriate train and disposition information.
💻 Technical Criteria
EXCLUDING Either a warning condition exists OR the train status has been updated to not arrived
When The system prepares notifications
Then A Merlin notification message must be created with appropriate train and disposition information
R-GCX016E-cbl-00133 Include K1 Remark Messages if Present
Process Rules
📊 Business Logic Narrative
When the process 'Include K1 Remark Messages if Present' is invoked, and assuming that a merlin notification message is being created, when k1 segment remark messages exist in the current transaction, the desired outcome is that the k1 remark messages must be included in the merlin notification message.
💻 Technical Criteria
Given A Merlin notification message is being created
When K1 segment remark messages exist in the current transaction
Then The K1 remark messages must be included in the Merlin notification message
R-GCX016E-cbl-00134 Send Warning to Operations Team
Action Rules
📊 Business Logic Narrative
When the process 'Send Warning to Operations Team' is invoked, and assuming that a merlin notification message has been created with or without k1 remarks, when the system delivers the notification, the desired outcome is that the warning message must be sent to the operations team via the merlin messaging system.
💻 Technical Criteria
Given A Merlin notification message has been created with or without K1 remarks
When The system delivers the notification
Then The warning message must be sent to the operations team via the Merlin messaging system
R-GCX016E-cbl-00135 Trigger Re-Arrival Process
Action Rules
📊 Business Logic Narrative
When the process 'Trigger Re-Arrival Process' is invoked, and assuming that the warning has been sent to the operations team, when the system completes the oca processing, the desired outcome is that the re-arrival process must be triggered to allow the train to be processed for arrival again in the future.
💻 Technical Criteria
Given The warning has been sent to the operations team
When The system completes the OCA processing
Then The re-arrival process must be triggered to allow the train to be processed for arrival again in the future
R-GCX016E-cbl-00136 Log Processing Complete
Process Rules
📊 Business Logic Narrative
When the process 'Log Processing Complete' is invoked, and assuming that the re-arrival process has been triggered, when all oca processing steps are completed, the desired outcome is that a processing complete log entry must be created to document the successful completion of oca handling.
💻 Technical Criteria
Given The re-arrival process has been triggered
When All OCA processing steps are completed
Then A processing complete log entry must be created to document the successful completion of OCA handling
R-GCX016E-cbl-00137 Continue to Next Message Segment
Process Rules
📊 Business Logic Narrative
When the process 'Continue to Next Message Segment' is invoked, and assuming that oca processing has been completed and logged, when the system finishes the current segment processing, the desired outcome is that processing must continue to the next message segment in the transaction.
💻 Technical Criteria
Given OCA processing has been completed and logged
When The system finishes the current segment processing
Then Processing must continue to the next message segment in the transaction
R-GCX016E-cbl-00138 V9 Segment with COC Disposition Code Received
Process Rules
📊 Business Logic Narrative
When the process 'V9 Segment with COC Disposition Code Received' is invoked, and assuming that a v9 segment is received with coc disposition code, when the system processes the v9 segment, the desired outcome is that the system initiates train arrival cancellation processing.
💻 Technical Criteria
Given A V9 segment is received with COC disposition code
When The system processes the V9 segment
Then The system initiates train arrival cancellation processing
R-GCX016E-cbl-00139 Validate Train ID from M10 Segment
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Train ID from M10 Segment' is invoked, and assuming that a train id is provided from m10 segment data, when the system validates the train identification, the desired outcome is that the system confirms train id is valid and accessible for cancellation processing.
💻 Technical Criteria
Given A train ID is provided from M10 segment data
When The system validates the train identification
Then The system confirms train ID is valid and accessible for cancellation processing
R-GCX016E-cbl-00140 Train Found in System?
Decision Rules
📊 Business Logic Narrative
When the process 'Train Found in System?' is invoked, and assuming that a train id has been validated from m10 segment, when the system searches for the train in the train list, the desired outcome is that the system determines if the train exists and can proceed with cancellation or must log an error.
💻 Technical Criteria
Given A train ID has been validated from M10 segment
When The system searches for the train in the train list
Then The system determines if the train exists and can proceed with cancellation or must log an error
R-GCX016E-cbl-00141 Log Train Not Found Error
Action Rules
📊 Business Logic Narrative
When the process 'Log Train Not Found Error' is invoked, and assuming that a train id cannot be found in the train management system, when the system attempts to process train arrival cancellation, the desired outcome is that the system logs a train not found error and terminates the cancellation process.
💻 Technical Criteria
Given A train ID cannot be found in the train management system
When The system attempts to process train arrival cancellation
Then The system logs a train not found error and terminates the cancellation process
R-GCX016E-cbl-00142 Check Current Train Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check Current Train Status' is invoked, and assuming that a valid train has been found in the system, when the system checks the train's current status, the desired outcome is that the system retrieves current train status information for cancellation decision making.
💻 Technical Criteria
Given A valid train has been found in the system
When The system checks the train's current status
Then The system retrieves current train status information for cancellation decision making
R-GCX016E-cbl-00143 Train Currently Arrived?
Decision Rules
📊 Business Logic Narrative
When the process 'Train Currently Arrived?' is invoked, and assuming that the current train status has been retrieved, when the system evaluates if the train is currently in arrived status, the desired outcome is that the system determines whether to proceed with arrival cancellation or log a warning for non-arrived trains.
💻 Technical Criteria
Given The current train status has been retrieved
When The system evaluates if the train is currently in arrived status
Then The system determines whether to proceed with arrival cancellation or log a warning for non-arrived trains
R-GCX016E-cbl-00144 Cancel Train Arrival Status
Action Rules
📊 Business Logic Narrative
When the process 'Cancel Train Arrival Status' is invoked, and assuming that a train is currently in arrived status and cancellation is requested, when the system processes the arrival cancellation, the desired outcome is that the system removes the arrival status from the train record.
💻 Technical Criteria
Given A train is currently in arrived status and cancellation is requested
When The system processes the arrival cancellation
Then The system removes the arrival status from the train record
R-GCX016E-cbl-00145 Update Train Arrival Date to Null
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Arrival Date to Null' is invoked, and assuming that train arrival status has been cancelled, when the system updates train arrival information, the desired outcome is that the system sets the train arrival date to null.
💻 Technical Criteria
Given Train arrival status has been cancelled
When The system updates train arrival information
Then The system sets the train arrival date to null
R-GCX016E-cbl-00146 Clear Train Arrival Flags
Action Rules
📊 Business Logic Narrative
When the process 'Clear Train Arrival Flags' is invoked, and assuming that train arrival date has been nullified, when the system completes arrival cancellation processing, the desired outcome is that the system clears all train arrival flags and indicators.
💻 Technical Criteria
Given Train arrival date has been nullified
When The system completes arrival cancellation processing
Then The system clears all train arrival flags and indicators
R-GCX016E-cbl-00147 Log COC Arrival Cancellation Action
Action Rules
📊 Business Logic Narrative
When the process 'Log COC Arrival Cancellation Action' is invoked, and assuming that train arrival flags have been cleared, when the system completes the cancellation process, the desired outcome is that the system logs the coc arrival cancellation action for audit purposes.
💻 Technical Criteria
Given Train arrival flags have been cleared
When The system completes the cancellation process
Then The system logs the COC arrival cancellation action for audit purposes
R-GCX016E-cbl-00148 Generate Train Arrival Cancellation Warning
Action Rules
📊 Business Logic Narrative
When the process 'Generate Train Arrival Cancellation Warning' is invoked, and assuming that coc arrival cancellation action has been logged, when the system generates operational notifications, the desired outcome is that the system creates a train arrival cancellation warning message.
💻 Technical Criteria
Given COC arrival cancellation action has been logged
When The system generates operational notifications
Then The system creates a train arrival cancellation warning message
R-GCX016E-cbl-00149 Log Warning - Train Not Previously Arrived
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Warning - Train Not Previously Arrived', assuming that a train is not currently in arrived status, when the system processes a coc cancellation request, the desired outcome is that the system logs a warning that the train was not previously arrived.
💻 Technical Criteria
EXCLUDING A train is not currently in arrived status
When The system processes a COC cancellation request
Then The system logs a warning that the train was not previously arrived
R-GCX016E-cbl-00150 Create Merlin Notification Message
Action Rules
📊 Business Logic Narrative
When the process 'Create Merlin Notification Message' is invoked, and assuming that train arrival cancellation warning has been generated or non-arrived warning has been logged, when the system prepares business notifications, the desired outcome is that the system creates a formatted merlin notification message.
💻 Technical Criteria
Given Train arrival cancellation warning has been generated or non-arrived warning has been logged
When The system prepares business notifications
Then The system creates a formatted Merlin notification message
R-GCX016E-cbl-00151 Send Notification to Business Users
Action Rules
📊 Business Logic Narrative
When the process 'Send Notification to Business Users' is invoked, and assuming that a merlin notification message has been created, when the system sends business notifications, the desired outcome is that the system delivers the notification to appropriate business users.
💻 Technical Criteria
Given A Merlin notification message has been created
When The system sends business notifications
Then The system delivers the notification to appropriate business users
R-GCX016E-cbl-00152 Update Train Status in Database
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Status in Database' is invoked, and assuming that notification has been sent to business users, when the system finalizes the cancellation process, the desired outcome is that the system updates the train status information in the database.
💻 Technical Criteria
Given Notification has been sent to business users
When The system finalizes the cancellation process
Then The system updates the train status information in the database
R-GCX016E-cbl-00153 Process Complete
Process Rules
📊 Business Logic Narrative
When the process 'Process Complete' is invoked, and assuming that train status has been updated in the database or error has been logged, when the system finishes all cancellation processing steps, the desired outcome is that the system marks the train arrival cancellation process as complete.
💻 Technical Criteria
Given Train status has been updated in the database or error has been logged
When The system finishes all cancellation processing steps
Then The system marks the train arrival cancellation process as complete
R-GCX016E-cbl-00154 Receive LCK Disposition Code for Train
Process Rules
📊 Business Logic Narrative
When the process 'Receive LCK Disposition Code for Train' is invoked, and assuming that a v9 segment contains event code lck for train lock processing, when the system processes the v9 segment with lck event code, the desired outcome is that the system initiates train lock processing workflow.
💻 Technical Criteria
Given A V9 segment contains event code LCK for train lock processing
When The system processes the V9 segment with LCK event code
Then The system initiates train lock processing workflow
R-GCX016E-cbl-00155 Validate Train ID from M10 Segment
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Train ID from M10 Segment' is invoked, and assuming that an m10 segment contains vessel/train information, when the system processes the m10 segment for train identification, the desired outcome is that the system extracts and validates the train id for further processing.
💻 Technical Criteria
Given An M10 segment contains vessel/train information
When The system processes the M10 segment for train identification
Then The system extracts and validates the train ID for further processing
R-GCX016E-cbl-00157 Retrieve Current Train Status
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Train Status' is invoked, and assuming that a train has been found in the system, when the system needs to process a lock request for the train, the desired outcome is that the system retrieves the current status information for the train.
💻 Technical Criteria
Given A train has been found in the system
When The system needs to process a lock request for the train
Then The system retrieves the current status information for the train
R-GCX016E-cbl-00158 Train Already Locked?
Decision Rules
📊 Business Logic Narrative
When the process 'Train Already Locked?' is invoked, and assuming that current train status has been retrieved, when the system evaluates the train's current lock status, the desired outcome is that the system determines if the train is already locked or proceeds with lock processing if not already locked.
💻 Technical Criteria
Given Current train status has been retrieved
When The system evaluates the train's current lock status
Then The system determines if the train is already locked OR proceeds with lock processing if not already locked
R-GCX016E-cbl-00159 Set Train Lock Status Flag
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Train Lock Status Flag', assuming that a train is not currently locked, when the system processes a lck disposition code for the train, the desired outcome is that the system sets the train locked status flag.
💻 Technical Criteria
EXCLUDING A train is not currently locked
When The system processes a LCK disposition code for the train
Then The system sets the train locked status flag
R-GCX016E-cbl-00160 Update Train Record in Database
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Record in Database' is invoked, and assuming that train lock status flag has been set, when the system commits the lock status change, the desired outcome is that the system updates the train record in the database with the new lock status.
💻 Technical Criteria
Given Train lock status flag has been set
When The system commits the lock status change
Then The system updates the train record in the database with the new lock status
R-GCX016E-cbl-00161 Log Train Lock Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Train Lock Action' is invoked, and assuming that train record has been updated with lock status, when the system completes the lock processing, the desired outcome is that the system logs the train lock action with relevant details.
💻 Technical Criteria
Given Train record has been updated with lock status
When The system completes the lock processing
Then The system logs the train lock action with relevant details
R-GCX016E-cbl-00162 Generate Merlin Notification Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Merlin Notification Message' is invoked, and assuming that train lock action has been logged, when the system processes notification requirements, the desired outcome is that the system generates a merlin notification message for the train lock event.
💻 Technical Criteria
Given Train lock action has been logged
When The system processes notification requirements
Then The system generates a Merlin notification message for the train lock event
R-GCX016E-cbl-00163 Send Lock Confirmation to Business Users
Action Rules
📊 Business Logic Narrative
When the process 'Send Lock Confirmation to Business Users' is invoked, and assuming that merlin notification message has been generated, when the system processes user notification requirements, the desired outcome is that the system sends lock confirmation to appropriate business users.
💻 Technical Criteria
Given Merlin notification message has been generated
When The system processes user notification requirements
Then The system sends lock confirmation to appropriate business users
R-GCX016E-cbl-00165 Generate Warning - Train Already Locked
Validation Rules
📊 Business Logic Narrative
When the process 'Generate Warning - Train Already Locked' is invoked, and assuming that a train's current status shows it is already locked, when the system processes a lck disposition code for the already locked train, the desired outcome is that the system generates a warning message indicating the train is already locked.
💻 Technical Criteria
Given A train's current status shows it is already locked
When The system processes a LCK disposition code for the already locked train
Then The system generates a warning message indicating the train is already locked
R-GCX016E-cbl-00166 Receive ULC Disposition Code in V9 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Receive ULC Disposition Code in V9 Segment' is invoked, and assuming that a v9 segment is received with event code ulc, when the system processes the v9 segment, the desired outcome is that the system initiates train unlock processing workflow.
💻 Technical Criteria
Given A V9 segment is received with event code ULC
When The system processes the V9 segment
Then The system initiates train unlock processing workflow
R-GCX016E-cbl-00167 Validate Train ID from M10 Segment
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Train ID from M10 Segment' is invoked, and assuming that an unlock request is being processed, when the system needs to identify the target train, the desired outcome is that the system retrieves and validates train identification from the m10 segment.
💻 Technical Criteria
Given An unlock request is being processed
When The system needs to identify the target train
Then The system retrieves and validates train identification from the M10 segment
R-GCX016E-cbl-00169 Retrieve Current Train Status
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Train Status' is invoked, and assuming that a valid train has been identified in the system, when the system needs to process an unlock request, the desired outcome is that the system retrieves the current lock status of the train.
💻 Technical Criteria
Given A valid train has been identified in the system
When The system needs to process an unlock request
Then The system retrieves the current lock status of the train
R-GCX016E-cbl-00170 Train Currently Locked?
Decision Rules
📊 Business Logic Narrative
When the process 'Train Currently Locked?' is invoked, and assuming that the current train status has been retrieved, when the system evaluates whether unlock operation should proceed, the desired outcome is that if train is locked, unlock proceeds; if not locked, a warning is generated.
💻 Technical Criteria
Given The current train status has been retrieved
When The system evaluates whether unlock operation should proceed
Then If train is locked, unlock proceeds; if not locked, a warning is generated
R-GCX016E-cbl-00171 Update Train Status to Unlocked
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Status to Unlocked' is invoked, and assuming that a train is currently in locked status, when a valid unlock request is processed, the desired outcome is that the system updates the train status to unlocked.
💻 Technical Criteria
Given A train is currently in locked status
When A valid unlock request is processed
Then The system updates the train status to unlocked
R-GCX016E-cbl-00172 Log Train Unlock Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Train Unlock Action' is invoked, and assuming that a train status has been successfully updated to unlocked, when the unlock operation completes, the desired outcome is that the system logs the unlock action with timestamp and train details.
💻 Technical Criteria
Given A train status has been successfully updated to unlocked
When The unlock operation completes
Then The system logs the unlock action with timestamp and train details
R-GCX016E-cbl-00173 Generate Merlin Notification Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Merlin Notification Message' is invoked, and assuming that a train unlock action has been logged, when the system needs to notify stakeholders, the desired outcome is that the system generates a merlin notification message with unlock details.
💻 Technical Criteria
Given A train unlock action has been logged
When The system needs to notify stakeholders
Then The system generates a Merlin notification message with unlock details
R-GCX016E-cbl-00174 Send Train Unlock Confirmation
Action Rules
📊 Business Logic Narrative
When the process 'Send Train Unlock Confirmation' is invoked, and assuming that a merlin notification message has been generated, when the system completes unlock processing, the desired outcome is that the system sends unlock confirmation to the requesting party.
💻 Technical Criteria
Given A Merlin notification message has been generated
When The system completes unlock processing
Then The system sends unlock confirmation to the requesting party
R-GCX016E-cbl-00176 Generate Warning - Train Not Locked
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Warning - Train Not Locked', assuming that a valid train has been identified for unlock processing, when the train is not currently in locked status, the desired outcome is that the system generates a warning message indicating train is not locked.
💻 Technical Criteria
EXCLUDING A valid train has been identified for unlock processing
When The train is not currently in locked status
Then The system generates a warning message indicating train is not locked
R-GCX016E-cbl-00177 SEI Disposition Code Received for Train
Decision Rules
📊 Business Logic Narrative
When the process 'SEI Disposition Code Received for Train' is invoked, and assuming that a v9 segment contains event code 'sei' for train seizure, when the system processes the v9 segment with sei event code, the desired outcome is that the system initiates train seizure processing workflow.
💻 Technical Criteria
Given A V9 segment contains event code 'SEI' for train seizure
When The system processes the V9 segment with SEI event code
Then The system initiates train seizure processing workflow
R-GCX016E-cbl-00178 Validate Train ID from M10 Segment
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Train ID from M10 Segment' is invoked, and assuming that an m10 segment contains vessel/train identification information, when the system processes the m10 segment for train seizure, the desired outcome is that the system extracts the train id and prepares it for validation.
💻 Technical Criteria
Given An M10 segment contains vessel/train identification information
When The system processes the M10 segment for train seizure
Then The system extracts the train ID and prepares it for validation
R-GCX016E-cbl-00180 Retrieve Current Train Status
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Train Status' is invoked, and assuming that a valid train has been found in the system, when the system needs to process a seizure request, the desired outcome is that the system retrieves the current train status including seizure flag.
💻 Technical Criteria
Given A valid train has been found in the system
When The system needs to process a seizure request
Then The system retrieves the current train status including seizure flag
R-GCX016E-cbl-00181 Train Already Seized?
Decision Rules
📊 Business Logic Narrative
When the process 'Train Already Seized?' is invoked, and assuming that the current train status has been retrieved, when the system checks if the train is already seized, the desired outcome is that if train seizure flag is 'y', skip processing; otherwise proceed with seizure.
💻 Technical Criteria
Given The current train status has been retrieved
When The system checks if the train is already seized
Then If train seizure flag is 'Y', skip processing; otherwise proceed with seizure
R-GCX016E-cbl-00183 Update Train Status in Database
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Status in Database' is invoked, and assuming that the train seizure flag has been set to 'y', when the system needs to save the status change, the desired outcome is that the system updates the train record in the database with the new seizure status.
💻 Technical Criteria
Given The train seizure flag has been set to 'Y'
When The system needs to save the status change
Then The system updates the train record in the database with the new seizure status
R-GCX016E-cbl-00184 Log Seizure Action with Timestamp
Process Rules
📊 Business Logic Narrative
When the process 'Log Seizure Action with Timestamp' is invoked, and assuming that a train has been successfully seized, when the system completes the seizure status update, the desired outcome is that the system logs the seizure action with current date and time.
💻 Technical Criteria
Given A train has been successfully seized
When The system completes the seizure status update
Then The system logs the seizure action with current date and time
R-GCX016E-cbl-00185 Generate Merlin Notification Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Merlin Notification Message' is invoked, and assuming that a train seizure has been logged successfully, when the system needs to notify stakeholders, the desired outcome is that the system generates a merlin notification message with seizure details.
💻 Technical Criteria
Given A train seizure has been logged successfully
When The system needs to notify stakeholders
Then The system generates a Merlin notification message with seizure details
R-GCX016E-cbl-00189 Process K1 Remark Messages if Present
Process Rules
📊 Business Logic Narrative
When the process 'Process K1 Remark Messages if Present' is invoked, and assuming that train seizure processing is in progress and k1 segments may be present, when the system checks for k1 remark segments, the desired outcome is that if k1 segments exist, the system processes the remark messages and includes them in seizure documentation.
💻 Technical Criteria
Given Train seizure processing is in progress and K1 segments may be present
When The system checks for K1 remark segments
Then If K1 segments exist, the system processes the remark messages and includes them in seizure documentation
R-GCX016E-cbl-00191 Skip Processing - Already Seized
Decision Rules
📊 Business Logic Narrative
When the process 'Skip Processing - Already Seized' is invoked, and assuming that a train is found in the system but is already seized, when the system checks the current seizure status, the desired outcome is that the system skips seizure processing and continues to completion.
💻 Technical Criteria
Given A train is found in the system but is already seized
When The system checks the current seizure status
Then The system skips seizure processing and continues to completion
R-GCX016E-cbl-00193 Receive SER Disposition Code for Train
Process Rules
📊 Business Logic Narrative
When the process 'Receive SER Disposition Code for Train' is invoked, and assuming that a v9 segment with event code ser is received for a train, when the system processes the ser disposition code, the desired outcome is that the train seizure release workflow is initiated.
💻 Technical Criteria
Given A V9 segment with event code SER is received for a train
When The system processes the SER disposition code
Then The train seizure release workflow is initiated
R-GCX016E-cbl-00194 Validate Train ID from M10 Segment
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Train ID from M10 Segment' is invoked, and assuming that an m10 segment contains train identification information, when the system processes seizure release for the train, the desired outcome is that the train id is extracted and validated from the m10 segment.
💻 Technical Criteria
Given An M10 segment contains train identification information
When The system processes seizure release for the train
Then The train ID is extracted and validated from the M10 segment
R-GCX016E-cbl-00196 Check Current Train Seizure Status
Decision Rules
📊 Business Logic Narrative
When the process 'Check Current Train Seizure Status' is invoked, and assuming that a valid train exists in the system, when the system processes a seizure release request, the desired outcome is that the current seizure status of the train is retrieved and evaluated.
💻 Technical Criteria
Given A valid train exists in the system
When The system processes a seizure release request
Then The current seizure status of the train is retrieved and evaluated
R-GCX016E-cbl-00197 Train Currently Seized?
Decision Rules
📊 Business Logic Narrative
When the process 'Train Currently Seized?' is invoked, and assuming that a train's current seizure status has been retrieved, when the system evaluates if seizure release is applicable, the desired outcome is that the system determines if the train is currently seized and can be released.
💻 Technical Criteria
Given A train's current seizure status has been retrieved
When The system evaluates if seizure release is applicable
Then The system determines if the train is currently seized and can be released
R-GCX016E-cbl-00198 Release Train from Seizure Status
Action Rules
📊 Business Logic Narrative
When the process 'Release Train from Seizure Status' is invoked, and assuming that a train is currently in seized status, when a valid seizure release request is processed, the desired outcome is that the train's seizure status is cleared and the train is released.
💻 Technical Criteria
Given A train is currently in seized status
When A valid seizure release request is processed
Then The train's seizure status is cleared and the train is released
R-GCX016E-cbl-00199 Update Train Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Status Flags' is invoked, and assuming that a train has been released from seizure status, when the seizure release processing continues, the desired outcome is that all relevant train status flags are updated to reflect the new status.
💻 Technical Criteria
Given A train has been released from seizure status
When The seizure release processing continues
Then All relevant train status flags are updated to reflect the new status
R-GCX016E-cbl-00200 Log Seizure Release Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Seizure Release Action' is invoked, and assuming that a train seizure release has been successfully processed, when the system completes the status update, the desired outcome is that the seizure release action is logged with relevant details.
💻 Technical Criteria
Given A train seizure release has been successfully processed
When The system completes the status update
Then The seizure release action is logged with relevant details
R-GCX016E-cbl-00207 Send Notification to Business Users
Action Rules
📊 Business Logic Narrative
When the process 'Send Notification to Business Users' is invoked, and assuming that a train seizure release notification has been generated, when the notification is ready for distribution, the desired outcome is that the notification is sent to appropriate business users.
💻 Technical Criteria
Given A train seizure release notification has been generated
When The notification is ready for distribution
Then The notification is sent to appropriate business users
R-GCX016E-cbl-00209 Log Warning - Train Not Seized
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Warning - Train Not Seized', assuming that a train exists but is not currently in seized status, when a seizure release request is processed, the desired outcome is that a warning is logged indicating the train is not seized and processing continues.
💻 Technical Criteria
EXCLUDING A train exists but is not currently in seized status
When A seizure release request is processed
Then A warning is logged indicating the train is not seized and processing continues
R-GCX016E-cbl-00210 Complete Seizure Release Processing
Process Rules
📊 Business Logic Narrative
When the process 'Complete Seizure Release Processing' is invoked, and assuming that all seizure release processing steps have been executed, when the workflow reaches completion, the desired outcome is that the seizure release processing is marked as complete.
💻 Technical Criteria
Given All seizure release processing steps have been executed
When The workflow reaches completion
Then The seizure release processing is marked as complete
R-GCX016E-cbl-00211 Receive CAE Disposition Code for Train
Process Rules
📊 Business Logic Narrative
When the process 'Receive CAE Disposition Code for Train' is invoked, and assuming that a cae disposition code is received for a specific train, when the system processes the cae event code, the desired outcome is that the train all clear processing is initiated.
💻 Technical Criteria
Given A CAE disposition code is received for a specific train
When The system processes the CAE event code
Then The train all clear processing is initiated
R-GCX016E-cbl-00212 Validate Train Exists in System
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Train Exists in System' is invoked, and assuming that a cae disposition code is being processed for a train, when the system checks the train list segments, the desired outcome is that the train existence is validated against the gcwtl train list.
💻 Technical Criteria
Given A CAE disposition code is being processed for a train
When The system checks the train list segments
Then The train existence is validated against the GCWTL train list
R-GCX016E-cbl-00213 Train Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Train Found?' is invoked, and assuming that train existence validation has been completed, when the system evaluates if the train was found in the train list, the desired outcome is that processing continues to set all clear status if train exists, otherwise error processing is initiated.
💻 Technical Criteria
Given Train existence validation has been completed
When The system evaluates if the train was found in the train list
Then Processing continues to set all clear status if train exists, otherwise error processing is initiated
R-GCX016E-cbl-00215 Clear Any Previous Hold Status
Action Rules
📊 Business Logic Narrative
When the process 'Clear Any Previous Hold Status' is invoked, and assuming that a train all clear status flag has been set, when the system processes the all clear action, the desired outcome is that any previous hold status flags are cleared to ensure clean all clear state.
💻 Technical Criteria
Given A train all clear status flag has been set
When The system processes the all clear action
Then Any previous hold status flags are cleared to ensure clean all clear state
R-GCX016E-cbl-00216 Update Train Status in Database
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Status in Database' is invoked, and assuming that train all clear status has been set and previous holds cleared, when the system commits the status changes, the desired outcome is that the train status is updated in the database with the new all clear status.
💻 Technical Criteria
Given Train all clear status has been set and previous holds cleared
When The system commits the status changes
Then The train status is updated in the database with the new all clear status
R-GCX016E-cbl-00217 Log All Clear Action
Action Rules
📊 Business Logic Narrative
When the process 'Log All Clear Action' is invoked, and assuming that train status has been successfully updated in the database, when the all clear processing is completed, the desired outcome is that an audit log entry is created documenting the all clear action with timestamp and train details.
💻 Technical Criteria
Given Train status has been successfully updated in the database
When The all clear processing is completed
Then An audit log entry is created documenting the all clear action with timestamp and train details
R-GCX016E-cbl-00218 Generate Merlin Notification Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Merlin Notification Message' is invoked, and assuming that all clear action has been logged successfully, when the system generates notifications, the desired outcome is that a merlin notification message is created containing train details and all clear status information.
💻 Technical Criteria
Given All clear action has been logged successfully
When The system generates notifications
Then A Merlin notification message is created containing train details and all clear status information
R-GCX016E-cbl-00219 Send All Clear Confirmation
Action Rules
📊 Business Logic Narrative
When the process 'Send All Clear Confirmation' is invoked, and assuming that merlin notification message has been generated, when the system sends the notification, the desired outcome is that the all clear confirmation is transmitted to the merlin system for distribution.
💻 Technical Criteria
Given Merlin notification message has been generated
When The system sends the notification
Then The all clear confirmation is transmitted to the Merlin system for distribution
R-GCX016E-cbl-00220 Generate Train Not Found Error
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Train Not Found Error', assuming that train validation has failed and train was not found, when the system processes the validation failure, the desired outcome is that a train not found error message is generated with relevant train identification details.
💻 Technical Criteria
EXCLUDING Train validation has failed and train was not found
When The system processes the validation failure
Then A train not found error message is generated with relevant train identification details
R-GCX016E-cbl-00221 Send Error Message to Merlin
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Send Error Message to Merlin', assuming that train not found error has been generated, when the system transmits the error notification, the desired outcome is that the error message is sent to merlin system to notify relevant parties of the processing failure.
💻 Technical Criteria
EXCLUDING Train not found error has been generated
When The system transmits the error notification
Then The error message is sent to Merlin system to notify relevant parties of the processing failure
R-GCX016E-cbl-00222 Process Complete
Process Rules
📊 Business Logic Narrative
When the process 'Process Complete' is invoked, and assuming that either all clear confirmation has been sent or error message has been transmitted, when the processing workflow reaches completion, the desired outcome is that the cae all clear processing is marked as complete and control returns to main processing flow.
💻 Technical Criteria
Given Either all clear confirmation has been sent or error message has been transmitted
When The processing workflow reaches completion
Then The CAE all clear processing is marked as complete and control returns to main processing flow
R-GCX016E-cbl-00274 Update Train Arrival Date from V9 Segment
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Arrival Date from V9 Segment' is invoked, and assuming that a train arrival is being processed and v9 segment contains date/time information, when the train arrival date needs to be recorded, the desired outcome is that extract and set the train arrival date from the v9 segment timestamp.
💻 Technical Criteria
Given A train arrival is being processed and V9 segment contains date/time information
When The train arrival date needs to be recorded
Then Extract and set the train arrival date from the V9 segment timestamp
R-GCX016E-cbl-00275 Clear Train Hold Status if Held
Decision Rules
📊 Business Logic Narrative
When the process 'Clear Train Hold Status if Held' is invoked, and assuming that a train is arriving and may have an existing hold status, when the train arrival is being processed, the desired outcome is that if the train is currently held, clear the hold status to allow normal processing.
💻 Technical Criteria
Given A train is arriving and may have an existing hold status
When The train arrival is being processed
Then If the train is currently held, clear the hold status to allow normal processing
R-GCX016E-cbl-00278 Send AEI Messages for Train Arrival
Action Rules
📊 Business Logic Narrative
When the process 'Send AEI Messages for Train Arrival' is invoked, and assuming that a train has arrived and aei notification is configured, when external systems need to be notified of the train arrival, the desired outcome is that generate and send aei messages containing train arrival information to configured recipients.
💻 Technical Criteria
Given A train has arrived and AEI notification is configured
When External systems need to be notified of the train arrival
Then Generate and send AEI messages containing train arrival information to configured recipients
R-GCX016E-cbl-00279 Update Train Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Status Flags' is invoked, and assuming that a train arrival has been processed, when train status information needs to be updated in the system, the desired outcome is that update all relevant train status flags including arrival status, hold status, and operational flags.
💻 Technical Criteria
Given A train arrival has been processed
When Train status information needs to be updated in the system
Then Update all relevant train status flags including arrival status, hold status, and operational flags
R-GCX016E-cbl-00280 Log Train Arrival Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Train Arrival Action' is invoked, and assuming that a train arrival has been successfully processed, when system audit trail needs to be maintained, the desired outcome is that create log entry documenting the train arrival action with timestamp and relevant details.
💻 Technical Criteria
Given A train arrival has been successfully processed
When System audit trail needs to be maintained
Then Create log entry documenting the train arrival action with timestamp and relevant details
R-GCX016E-cbl-00281 Generate Train Arrival Confirmation
Action Rules
📊 Business Logic Narrative
When the process 'Generate Train Arrival Confirmation' is invoked, and assuming that a train arrival has been completely processed, when confirmation of successful processing is required, the desired outcome is that generate train arrival confirmation message with processing results and status.
💻 Technical Criteria
Given A train arrival has been completely processed
When Confirmation of successful processing is required
Then Generate train arrival confirmation message with processing results and status
R-GCX016E-cbl-00295 Distribute AEI Messages
Action Rules
📊 Business Logic Narrative
When the process 'Distribute AEI Messages' is invoked, and assuming that email notifications have been created, when the system distributes aei messages, the desired outcome is that all aei messages and notifications are sent to their designated recipients and integrated systems.
💻 Technical Criteria
Given Email notifications have been created
When The system distributes AEI messages
Then All AEI messages and notifications are sent to their designated recipients and integrated systems
R-GCX016E-cbl-00296 Log AEI Processing Actions
Process Rules
📊 Business Logic Narrative
When the process 'Log AEI Processing Actions' is invoked, and assuming that aei messages have been distributed, when the system logs aei processing actions, the desired outcome is that all aei notification activities are recorded in the system log for audit and tracking purposes.
💻 Technical Criteria
Given AEI messages have been distributed
When The system logs AEI processing actions
Then All AEI notification activities are recorded in the system log for audit and tracking purposes
R-GCX016E-cbl-00297 Update Train Arrival Status
Process Rules
📊 Business Logic Narrative
When the process 'Update Train Arrival Status' is invoked, and assuming that aei processing actions have been logged, when the system updates train arrival status, the desired outcome is that the train's status is updated to indicate successful completion of aei notification processing.
💻 Technical Criteria
Given AEI processing actions have been logged
When The system updates train arrival status
Then The train's status is updated to indicate successful completion of AEI notification processing
R-GCX016E-cbl-00298 Complete AEI Notification Processing
Process Rules
📊 Business Logic Narrative
When the process 'Complete AEI Notification Processing' is invoked, and assuming that train arrival status has been updated, when the system completes aei notification processing, the desired outcome is that all aei notification processing activities are finalized and the workflow is marked as complete.
💻 Technical Criteria
Given Train arrival status has been updated
When The system completes AEI notification processing
Then All AEI notification processing activities are finalized and the workflow is marked as complete
R-GCX016E-cbl-02907 Check SCAC Unknown Scenarios
Validation Rules
📊 Business Logic Narrative
When the process 'Check SCAC Unknown Scenarios' is invoked, and assuming that cprs traffic is being processed, when the system validates the carrier information, the desired outcome is that scac is validated against carrier database and unknown scenarios are handled appropriately.
💻 Technical Criteria
Given CPRS traffic is being processed
When The system validates the carrier information
Then SCAC is validated against carrier database and unknown scenarios are handled appropriately
R-GCX016E-cbl-03167 Set CPRS Processing Flags
Action Rules
📊 Business Logic Narrative
When the process 'Set CPRS Processing Flags' is invoked, and assuming that cprs-specific fields have been initialized, when the system sets cprs processing flags, the desired outcome is that activate flags that control cprs-specific processing behavior throughout the system.
💻 Technical Criteria
Given CPRS-specific fields have been initialized
When the system sets CPRS processing flags
Then activate flags that control CPRS-specific processing behavior throughout the system
R-GCX016E-cbl-03168 Log CPRS Special Processing
Action Rules
📊 Business Logic Narrative
When the process 'Log CPRS Special Processing' is invoked, and assuming that cprs processing flags have been configured, when the system logs cprs special processing, the desired outcome is that create audit trail entries documenting cprs-specific processing actions and decisions.
💻 Technical Criteria
Given CPRS processing flags have been configured
When the system logs CPRS special processing
Then create audit trail entries documenting CPRS-specific processing actions and decisions
R-GCX016E-cbl-00327 Remove Counterpart Codes
Process Rules
📊 Business Logic Narrative
When the process 'Remove Counterpart Codes' is invoked, and assuming that a new disposition code is being added that has defined counterpart codes in the dc table, when the system processes the counterpart removal logic, the desired outcome is that remove all counterpart disposition codes from the status array before adding the new disposition code.
💻 Technical Criteria
Given A new disposition code is being added that has defined counterpart codes in the DC table
When The system processes the counterpart removal logic
Then Remove all counterpart disposition codes from the status array before adding the new disposition code
R-GCX016E-cbl-02916 43: Disposition Code Table Lookup
Validation Rules
📊 Business Logic Narrative
When the process '43: Disposition Code Table Lookup' is invoked, and assuming that a disposition code is received for processing, when the system looks up the disposition code in the gcstbrt disposition code table, the desired outcome is that if the code is not found in the table, generate a merlin error message and stop processing for this code.
💻 Technical Criteria
Given A disposition code is received for processing
When The system looks up the disposition code in the GCSTBRT disposition code table
Then If the code is not found in the table, generate a Merlin error message and stop processing for this code
R-GCX016E-cbl-02918 45: Counterpart Disposition Code Removal
Process Rules
📊 Business Logic Narrative
When the process '45: Counterpart Disposition Code Removal' is invoked, and assuming that a disposition code has counterpart codes defined in the disposition code table, when the system processes the new disposition code for addition to the status array, the desired outcome is that remove all existing counterpart disposition codes from the status array before adding the new code.
💻 Technical Criteria
Given A disposition code has counterpart codes defined in the disposition code table
When The system processes the new disposition code for addition to the status array
Then Remove all existing counterpart disposition codes from the status array before adding the new code
R-GCX016E-cbl-02921 157: Status Array Management and Processing
Computation Rules
📊 Business Logic Narrative
When the process '157: Status Array Management and Processing' is invoked, and assuming that the status array has been modified with additions or removals of disposition codes, when the system completes all array operations, the desired outcome is that update the status array counter to reflect the current number of active disposition codes in the array.
💻 Technical Criteria
Given The status array has been modified with additions or removals of disposition codes
When The system completes all array operations
Then Update the status array counter to reflect the current number of active disposition codes in the array
R-GCX016E-cbl-03169 Start Counterpart Disposition Code Removal
Process Rules
📊 Business Logic Narrative
When the process 'Start Counterpart Disposition Code Removal' is invoked, and assuming that a new disposition code needs to be processed, when the counterpart removal process is initiated, the desired outcome is that the system prepares to search the existing status array for conflicting codes.
💻 Technical Criteria
Given A new disposition code needs to be processed
When The counterpart removal process is initiated
Then The system prepares to search the existing status array for conflicting codes
R-GCX016E-cbl-03170 Receive New Disposition Code
Validation Rules
📊 Business Logic Narrative
When the process 'Receive New Disposition Code' is invoked, and assuming that a disposition code processing request is received, when the new disposition code is provided to the system, the desired outcome is that the system accepts the disposition code for counterpart analysis.
💻 Technical Criteria
Given A disposition code processing request is received
When The new disposition code is provided to the system
Then The system accepts the disposition code for counterpart analysis
R-GCX016E-cbl-03171 Search S09A Status Array for Existing Codes
Process Rules
📊 Business Logic Narrative
When the process 'Search S09A Status Array for Existing Codes' is invoked, and assuming that a new disposition code is received and the s09a status array exists, when the system searches for existing disposition codes in the status array, the desired outcome is that all existing disposition codes in the array are identified and made available for conflict analysis.
💻 Technical Criteria
Given A new disposition code is received and the S09A status array exists
When The system searches for existing disposition codes in the status array
Then All existing disposition codes in the array are identified and made available for conflict analysis
R-GCX016E-cbl-03172 Conflicting Codes Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Conflicting Codes Found?' is invoked, and assuming that the status array has been searched and existing codes are identified, when the system compares the new disposition code against existing codes, the desired outcome is that the system determines whether conflicting codes exist and proceeds accordingly.
💻 Technical Criteria
Given The status array has been searched and existing codes are identified
When The system compares the new disposition code against existing codes
Then The system determines whether conflicting codes exist and proceeds accordingly
R-GCX016E-cbl-03174 Code Type Analysis
Decision Rules
📊 Business Logic Narrative
When the process 'Code Type Analysis' is invoked, and assuming that counterpart code types have been identified, when the system performs code type analysis, the desired outcome is that the system determines the specific removal action based on code type relationships.
💻 Technical Criteria
Given Counterpart code types have been identified
When The system performs code type analysis
Then The system determines the specific removal action based on code type relationships
R-GCX016E-cbl-03175 Remove Hold Codes if Release Code Added
Action Rules
📊 Business Logic Narrative
When the process 'Remove Hold Codes if Release Code Added' is invoked, and assuming that a release disposition code is being added and hold codes exist in the status array, when the system processes the release code addition, the desired outcome is that all conflicting hold disposition codes are removed from the status array.
💻 Technical Criteria
Given A release disposition code is being added and hold codes exist in the status array
When The system processes the release code addition
Then All conflicting hold disposition codes are removed from the status array
R-GCX016E-cbl-03176 Remove Release Codes if Hold Code Added
Action Rules
📊 Business Logic Narrative
When the process 'Remove Release Codes if Hold Code Added' is invoked, and assuming that a hold disposition code is being added and release codes exist in the status array, when the system processes the hold code addition, the desired outcome is that all conflicting release disposition codes are removed from the status array.
💻 Technical Criteria
Given A hold disposition code is being added and release codes exist in the status array
When The system processes the hold code addition
Then All conflicting release disposition codes are removed from the status array
R-GCX016E-cbl-03177 Remove Proceed Codes if Cancel Code Added
Action Rules
📊 Business Logic Narrative
When the process 'Remove Proceed Codes if Cancel Code Added' is invoked, and assuming that a cancel disposition code is being added and proceed codes exist in the status array, when the system processes the cancel code addition, the desired outcome is that all conflicting proceed disposition codes are removed from the status array.
💻 Technical Criteria
Given A cancel disposition code is being added and proceed codes exist in the status array
When The system processes the cancel code addition
Then All conflicting proceed disposition codes are removed from the status array
R-GCX016E-cbl-03178 Remove Arrival Codes if Cancel Arrival Added
Action Rules
📊 Business Logic Narrative
When the process 'Remove Arrival Codes if Cancel Arrival Added' is invoked, and assuming that a cancel arrival disposition code is being added and arrival codes exist in the status array, when the system processes the cancel arrival code addition, the desired outcome is that all conflicting arrival disposition codes are removed from the status array.
💻 Technical Criteria
Given A cancel arrival disposition code is being added and arrival codes exist in the status array
When The system processes the cancel arrival code addition
Then All conflicting arrival disposition codes are removed from the status array
R-GCX016E-cbl-03180 Compress Status Array
Process Rules
📊 Business Logic Narrative
When the process 'Compress Status Array' is invoked, and assuming that disposition codes have been removed from the status array creating gaps, when the system compresses the status array, the desired outcome is that all remaining disposition codes are moved to eliminate gaps and maintain array continuity.
💻 Technical Criteria
Given Disposition codes have been removed from the status array creating gaps
When The system compresses the status array
Then All remaining disposition codes are moved to eliminate gaps and maintain array continuity
R-GCX016E-cbl-03183 Array Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Array Valid?' is invoked, and assuming that array integrity validation has been performed, when the system checks array validity, the desired outcome is that the system determines whether the array is valid and proceeds with success or error handling.
💻 Technical Criteria
Given Array integrity validation has been performed
When The system checks array validity
Then The system determines whether the array is valid and proceeds with success or error handling
R-GCX016E-cbl-03184 Log Removal Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Removal Action' is invoked, and assuming that counterpart disposition codes have been successfully removed and the array is valid, when the system logs the removal action, the desired outcome is that a record of the removed codes and the removal reason is created for audit purposes.
💻 Technical Criteria
Given Counterpart disposition codes have been successfully removed and the array is valid
When The system logs the removal action
Then A record of the removed codes and the removal reason is created for audit purposes
R-GCX016E-cbl-03185 Return Success Status
Process Rules
📊 Business Logic Narrative
When the process 'Return Success Status' is invoked, and assuming that the counterpart disposition code removal process has completed successfully, when the system returns success status, the desired outcome is that control is returned to the calling process with a successful completion indicator.
💻 Technical Criteria
Given The counterpart disposition code removal process has completed successfully
When The system returns success status
Then Control is returned to the calling process with a successful completion indicator
R-GCX016E-cbl-03186 Generate Error Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Error Message' is invoked, and assuming that array validation has failed during the counterpart removal process, when the system generates an error message, the desired outcome is that an appropriate error message is created describing the validation failure.
💻 Technical Criteria
Given Array validation has failed during the counterpart removal process
When The system generates an error message
Then An appropriate error message is created describing the validation failure
R-GCX016E-cbl-03187 Restore Previous Array State
Action Rules
📊 Business Logic Narrative
When the process 'Restore Previous Array State' is invoked, and assuming that an error has occurred during counterpart code removal and an error message has been generated, when the system restores the previous array state, the desired outcome is that the status array is returned to its state before the counterpart removal attempt began.
💻 Technical Criteria
Given An error has occurred during counterpart code removal and an error message has been generated
When The system restores the previous array state
Then The status array is returned to its state before the counterpart removal attempt began
R-GCX016E-cbl-03334 Initialize Search Parameters
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Search Parameters' is invoked, and assuming that a status array search operation is initiated, when the search process begins, the desired outcome is that all search parameters are initialized including duplicate flags, conflict flags, position counters, and removal lists are cleared.
💻 Technical Criteria
Given A status array search operation is initiated
When The search process begins
Then All search parameters are initialized including duplicate flags, conflict flags, position counters, and removal lists are cleared
R-GCX016E-cbl-03338 Begin Sequential Array Search
Process Rules
📊 Business Logic Narrative
When the process 'Begin Sequential Array Search' is invoked, and assuming that the s09a status array contains one or more entries, when the sequential search process is initiated, the desired outcome is that begin iterating through each status array entry starting from the first position.
💻 Technical Criteria
Given The S09A status array contains one or more entries
When The sequential search process is initiated
Then Begin iterating through each status array entry starting from the first position
R-GCX016E-cbl-03339 More Array Entries?
Decision Rules
📊 Business Logic Narrative
When the process 'More Array Entries?' is invoked, and assuming that a sequential search through the status array is in progress, when the current position in the array is evaluated, the desired outcome is that if more entries exist, continue to next entry; otherwise complete the array analysis.
💻 Technical Criteria
Given A sequential search through the status array is in progress
When The current position in the array is evaluated
Then If more entries exist, continue to next entry; otherwise complete the array analysis
R-GCX016E-cbl-03340 Get Next Status Entry
Action Rules
📊 Business Logic Narrative
When the process 'Get Next Status Entry' is invoked, and assuming that more entries exist in the status array to examine, when the next entry retrieval is executed, the desired outcome is that the next status array entry is loaded for disposition code analysis.
💻 Technical Criteria
Given More entries exist in the status array to examine
When The next entry retrieval is executed
Then The next status array entry is loaded for disposition code analysis
R-GCX016E-cbl-03341 Extract Disposition Code
Action Rules
📊 Business Logic Narrative
When the process 'Extract Disposition Code' is invoked, and assuming that a status array entry has been retrieved, when the disposition code extraction is performed, the desired outcome is that the disposition code is extracted from the entry for comparison purposes.
💻 Technical Criteria
Given A status array entry has been retrieved
When The disposition code extraction is performed
Then The disposition code is extracted from the entry for comparison purposes
R-GCX016E-cbl-03342 Code Matches Target?
Decision Rules
📊 Business Logic Narrative
When the process 'Code Matches Target?' is invoked, and assuming that a disposition code has been extracted from the current status entry and a target code is defined, when the code comparison is performed, the desired outcome is that if the extracted code matches the target code, mark as duplicate found; otherwise check for counterpart codes.
💻 Technical Criteria
Given A disposition code has been extracted from the current status entry and a target code is defined
When The code comparison is performed
Then If the extracted code matches the target code, mark as duplicate found; otherwise check for counterpart codes
R-GCX016E-cbl-03343 Mark Duplicate Found
Action Rules
📊 Business Logic Narrative
When the process 'Mark Duplicate Found' is invoked, and assuming that the extracted disposition code matches the target code being searched, when the duplicate marking process is executed, the desired outcome is that set the duplicate found flag to indicate an existing matching disposition code.
💻 Technical Criteria
Given The extracted disposition code matches the target code being searched
When The duplicate marking process is executed
Then Set the duplicate found flag to indicate an existing matching disposition code
R-GCX016E-cbl-03344 Record Entry Position
Action Rules
📊 Business Logic Narrative
When the process 'Record Entry Position' is invoked, and assuming that a duplicate disposition code has been identified in the status array, when the position recording is performed, the desired outcome is that record the current array position for potential future reference or removal operations.
💻 Technical Criteria
Given A duplicate disposition code has been identified in the status array
When The position recording is performed
Then Record the current array position for potential future reference or removal operations
R-GCX016E-cbl-03345 Check for Counterpart Codes
Validation Rules
📊 Business Logic Narrative
When the process 'Check for Counterpart Codes' is invoked, and assuming that a disposition code has been extracted from the status array entry, when the counterpart code analysis is performed, the desired outcome is that determine if the current code conflicts with existing codes and requires counterpart removal.
💻 Technical Criteria
Given A disposition code has been extracted from the status array entry
When The counterpart code analysis is performed
Then Determine if the current code conflicts with existing codes and requires counterpart removal
R-GCX016E-cbl-03346 Counterpart Code Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Counterpart Code Found?' is invoked, and assuming that the counterpart code analysis has been completed for the current disposition code, when the counterpart detection results are evaluated, the desired outcome is that if counterpart codes are found, mark for removal; otherwise continue with the search process.
💻 Technical Criteria
Given The counterpart code analysis has been completed for the current disposition code
When The counterpart detection results are evaluated
Then If counterpart codes are found, mark for removal; otherwise continue with the search process
R-GCX016E-cbl-03347 Mark for Removal
Action Rules
📊 Business Logic Narrative
When the process 'Mark for Removal' is invoked, and assuming that counterpart disposition codes have been identified that conflict with the current processing, when the removal marking process is executed, the desired outcome is that mark the conflicting codes for removal from the status array.
💻 Technical Criteria
Given Counterpart disposition codes have been identified that conflict with the current processing
When The removal marking process is executed
Then Mark the conflicting codes for removal from the status array
R-GCX016E-cbl-03348 Add to Removal List
Action Rules
📊 Business Logic Narrative
When the process 'Add to Removal List' is invoked, and assuming that disposition codes have been marked for removal due to conflicts, when the removal list update is performed, the desired outcome is that add the conflicting codes and their positions to the removal list for subsequent processing.
💻 Technical Criteria
Given Disposition codes have been marked for removal due to conflicts
When The removal list update is performed
Then Add the conflicting codes and their positions to the removal list for subsequent processing
R-GCX016E-cbl-03349 Continue Search
Process Rules
📊 Business Logic Narrative
When the process 'Continue Search' is invoked, and assuming that the current status array entry has been processed for duplicates and conflicts, when the search continuation is executed, the desired outcome is that move to the next array position to continue the sequential search process.
💻 Technical Criteria
Given The current status array entry has been processed for duplicates and conflicts
When The search continuation is executed
Then Move to the next array position to continue the sequential search process
R-GCX016E-cbl-03350 Complete Array Analysis
Process Rules
📊 Business Logic Narrative
When the process 'Complete Array Analysis' is invoked, and assuming that all entries in the s09a status array have been examined, when the array analysis completion is executed, the desired outcome is that prepare to evaluate the search results for duplicates and conflicts.
💻 Technical Criteria
Given All entries in the S09A status array have been examined
When The array analysis completion is executed
Then Prepare to evaluate the search results for duplicates and conflicts
R-GCX016E-cbl-03351 Duplicates Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Duplicates Found?' is invoked, and assuming that the complete status array has been searched for disposition codes, when the duplicate detection results are evaluated, the desired outcome is that if duplicates were found, set duplicate flag; otherwise proceed to check for conflicts.
💻 Technical Criteria
Given The complete status array has been searched for disposition codes
When The duplicate detection results are evaluated
Then If duplicates were found, set duplicate flag; otherwise proceed to check for conflicts
R-GCX016E-cbl-03352 Set Duplicate Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Duplicate Flag' is invoked, and assuming that duplicate disposition codes have been identified during the array search, when the duplicate flag setting is executed, the desired outcome is that set the duplicate flag to indicate that matching disposition codes already exist.
💻 Technical Criteria
Given Duplicate disposition codes have been identified during the array search
When The duplicate flag setting is executed
Then Set the duplicate flag to indicate that matching disposition codes already exist
R-GCX016E-cbl-03353 Conflicts Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Conflicts Found?' is invoked, and assuming that the status array search has been completed and duplicate analysis is done, when the conflict detection results are evaluated, the desired outcome is that if conflicts were found, set conflict flag; otherwise prepare search results.
💻 Technical Criteria
Given The status array search has been completed and duplicate analysis is done
When The conflict detection results are evaluated
Then If conflicts were found, set conflict flag; otherwise prepare search results
R-GCX016E-cbl-03354 Set Conflict Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Conflict Flag' is invoked, and assuming that conflicting counterpart disposition codes have been identified during the search, when the conflict flag setting is executed, the desired outcome is that set the conflict flag to indicate that counterpart codes need removal.
💻 Technical Criteria
Given Conflicting counterpart disposition codes have been identified during the search
When The conflict flag setting is executed
Then Set the conflict flag to indicate that counterpart codes need removal
R-GCX016E-cbl-03355 Prepare Search Results
Action Rules
📊 Business Logic Narrative
When the process 'Prepare Search Results' is invoked, and assuming that the status array search has been completed with duplicate and conflict analysis, when the search results preparation is executed, the desired outcome is that compile all search findings including duplicate flags, conflict flags, positions, and removal lists.
💻 Technical Criteria
Given The status array search has been completed with duplicate and conflict analysis
When The search results preparation is executed
Then Compile all search findings including duplicate flags, conflict flags, positions, and removal lists
R-GCX016E-cbl-03356 Return Search Status
Action Rules
📊 Business Logic Narrative
When the process 'Return Search Status' is invoked, and assuming that the search results have been prepared with all findings compiled, when the search status return is executed, the desired outcome is that return the complete search status including duplicate indicators, conflict indicators, and removal requirements.
💻 Technical Criteria
Given The search results have been prepared with all findings compiled
When The search status return is executed
Then Return the complete search status including duplicate indicators, conflict indicators, and removal requirements
R-GCX016E-cbl-03357 End Search Process
Process Rules
📊 Business Logic Narrative
When the process 'End Search Process' is invoked, and assuming that the search status has been returned to the calling process, when the search process termination is executed, the desired outcome is that end the status array search operation and return control to the disposition code processing logic.
💻 Technical Criteria
Given The search status has been returned to the calling process
When The search process termination is executed
Then End the status array search operation and return control to the disposition code processing logic
R-GCX016E-cbl-03465 Get Counterpart Code List
Action Rules
📊 Business Logic Narrative
When the process 'Get Counterpart Code List' is invoked, and assuming that a disposition code has been confirmed to have counterparts, when the system accesses the disposition code table counterpart fields, the desired outcome is that the system retrieves all defined counterpart codes for the current disposition code.
💻 Technical Criteria
Given A disposition code has been confirmed to have counterparts
When The system accesses the disposition code table counterpart fields
Then The system retrieves all defined counterpart codes for the current disposition code
R-GCX016E-cbl-03467 Counterpart Found in Array?
Decision Rules
📊 Business Logic Narrative
When the process 'Counterpart Found in Array?' is invoked, and assuming that the system has searched the status array for counterpart codes, when the search results are evaluated, the desired outcome is that the system determines whether any counterpart codes were found in the status array.
💻 Technical Criteria
Given The system has searched the status array for counterpart codes
When The search results are evaluated
Then The system determines whether any counterpart codes were found in the status array
R-GCX016E-cbl-03469 Current Code Supersedes Counterpart?
Decision Rules
📊 Business Logic Narrative
When the process 'Current Code Supersedes Counterpart?' is invoked, and assuming that regulatory hierarchy has been evaluated between current and counterpart codes, when the system applies supersession rules, the desired outcome is that the system determines if the current code supersedes the counterpart code requiring its removal.
💻 Technical Criteria
Given Regulatory hierarchy has been evaluated between current and counterpart codes
When The system applies supersession rules
Then The system determines if the current code supersedes the counterpart code requiring its removal
R-GCX016E-cbl-03470 Mark Counterpart for Removal
Action Rules
📊 Business Logic Narrative
When the process 'Mark Counterpart for Removal' is invoked, and assuming that the current disposition code supersedes a counterpart code, when the system processes the supersession rule, the desired outcome is that the system marks the counterpart code for removal from the status array.
💻 Technical Criteria
Given The current disposition code supersedes a counterpart code
When The system processes the supersession rule
Then The system marks the counterpart code for removal from the status array
R-GCX016E-cbl-03471 Log Counterpart Removal Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Counterpart Removal Action' is invoked, and assuming that a counterpart code has been marked for removal, when the system processes the removal action, the desired outcome is that the system logs the counterpart removal action with relevant details.
💻 Technical Criteria
Given A counterpart code has been marked for removal
When The system processes the removal action
Then The system logs the counterpart removal action with relevant details
R-GCX016E-cbl-03474 Reorganize Status Array Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Reorganize Status Array Sequence' is invoked, and assuming that all counterpart codes have been processed and removed, when the system reorganizes the status array, the desired outcome is that the system resequences the remaining status codes to eliminate gaps.
💻 Technical Criteria
Given All counterpart codes have been processed and removed
When The system reorganizes the status array
Then The system resequences the remaining status codes to eliminate gaps
R-GCX016E-cbl-03475 Update Status Array Indexes
Action Rules
📊 Business Logic Narrative
When the process 'Update Status Array Indexes' is invoked, and assuming that the status array has been reorganized after counterpart removals, when the system updates array management fields, the desired outcome is that the system updates status array indexes and occurrence counters to reflect the current array state.
💻 Technical Criteria
Given The status array has been reorganized after counterpart removals
When The system updates array management fields
Then The system updates status array indexes and occurrence counters to reflect the current array state
R-GCX016E-cbl-03191 Check Special V37 Entries
Validation Rules
📊 Business Logic Narrative
When the process 'Check Special V37 Entries' is invoked, and assuming that an entry number has passed standard validations, when the system checks for special v37 entry requirements, the desired outcome is that v37 entries must meet additional validation criteria specific to this entry type.
💻 Technical Criteria
Given An entry number has passed standard validations
When The system checks for special V37 entry requirements
Then V37 entries must meet additional validation criteria specific to this entry type
R-GCX016E-cbl-03192 Entry Number Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Entry Number Valid?' is invoked, and assuming that all entry number validations have been completed, when the system evaluates overall entry number validity, the desired outcome is that if all validations pass, proceed with entry type processing; if any validation fails, generate error.
💻 Technical Criteria
Given All entry number validations have been completed
When The system evaluates overall entry number validity
Then If all validations pass, proceed with entry type processing; if any validation fails, generate error
R-GCX016E-cbl-03193 Convert EDI Entry Type Code
Computation Rules
📊 Business Logic Narrative
When the process 'Convert EDI Entry Type Code' is invoked, and assuming that a valid entry number with edi entry type code, when the system processes the entry type code, the desired outcome is that convert edi entry type code to internal system format for further processing.
💻 Technical Criteria
Given A valid entry number with EDI entry type code
When The system processes the entry type code
Then Convert EDI entry type code to internal system format for further processing
R-GCX016E-cbl-03204 Generate Error - Invalid Entry Number
Action Rules
📊 Business Logic Narrative
When the process 'Generate Error - Invalid Entry Number' is invoked, and assuming that entry number validation has failed, when the system processes the validation failure, the desired outcome is that generate appropriate error message indicating invalid entry number and halt processing.
💻 Technical Criteria
Given Entry number validation has failed
When The system processes the validation failure
Then Generate appropriate error message indicating invalid entry number and halt processing
R-GCX016E-cbl-03359 Lookup EDI Code in Conversion Table
Action Rules
📊 Business Logic Narrative
When the process 'Lookup EDI Code in Conversion Table' is invoked, and assuming that an edi entry type code is present in the x4 segment and conversion arrays are initialized, when the system searches the edi entry type code conversion table for a matching code, the desired outcome is that the system locates the position of the edi code in the lookup array for further processing.
💻 Technical Criteria
Given An EDI entry type code is present in the X4 segment and conversion arrays are initialized
When The system searches the EDI entry type code conversion table for a matching code
Then The system locates the position of the EDI code in the lookup array for further processing
R-GCX016E-cbl-03369 Generate Error Message for Invalid Code
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error Message for Invalid Code', assuming that an entry type code cannot be found in the conversion table or validation fails, when the system generates an error message for the invalid entry type code, the desired outcome is that an error message is created indicating the entry type code is invalid and cannot be processed.
💻 Technical Criteria
EXCLUDING An entry type code cannot be found in the conversion table or validation fails
When The system generates an error message for the invalid entry type code
Then An error message is created indicating the entry type code is invalid and cannot be processed
R-GCX016E-cbl-00346 Generate Error Message - Invalid DC95
Validation Rules
📊 Business Logic Narrative
When the process 'Generate Error Message - Invalid DC95' is invoked, and assuming that a disposition code 95 is being processed, when the system cannot find dc95 in the disposition code table, the desired outcome is that an error message is generated indicating invalid disposition code 95.
💻 Technical Criteria
Given A disposition code 95 is being processed
When The system cannot find DC95 in the disposition code table
Then An error message is generated indicating invalid disposition code 95
R-GCX016E-cbl-00349 Validate Against Existing Broker Entry Numbers
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Against Existing Broker Entry Numbers' is invoked, and assuming that a valid entry number format has been confirmed, when the system checks against existing broker entry numbers, the desired outcome is that the entry number is validated for consistency with broker records.
💻 Technical Criteria
Given A valid entry number format has been confirmed
When The system checks against existing broker entry numbers
Then The entry number is validated for consistency with broker records
R-GCX016E-cbl-00351 Check Special V37 Entries
Validation Rules
📊 Business Logic Narrative
When the process 'Check Special V37 Entries' is invoked, and assuming that the entry number has passed standard validations, when the system checks for special v37 entry requirements, the desired outcome is that special v37 validation rules are applied if applicable.
💻 Technical Criteria
Given The entry number has passed standard validations
When The system checks for special V37 entry requirements
Then Special V37 validation rules are applied if applicable
R-GCX016E-cbl-00352 Entry Type Code?
Decision Rules
📊 Business Logic Narrative
When the process 'Entry Type Code?' is invoked, and assuming that all validations have been completed successfully, when the system evaluates the entry type code, the desired outcome is that the appropriate entry type specific processing path is selected (61, 62, 63, 69, or other).
💻 Technical Criteria
Given All validations have been completed successfully
When The system evaluates the entry type code
Then The appropriate entry type specific processing path is selected (61, 62, 63, 69, or Other)
R-GCX016E-cbl-00360 Generate Error Message
Process Rules
📊 Business Logic Narrative
When the process 'Generate Error Message' is invoked, and assuming that entry number validation has failed, when the system processes the validation failure, the desired outcome is that an appropriate error message is generated describing the validation failure.
💻 Technical Criteria
Given Entry number validation has failed
When The system processes the validation failure
Then An appropriate error message is generated describing the validation failure
R-GCX016E-cbl-00362 Entry Type Code Present?
Validation Rules
📊 Business Logic Narrative
When the process 'Entry Type Code Present?' is invoked, and assuming that an edi message is received for snp processing, when the system checks for the presence of an entry type code in the message, the desired outcome is that if entry type code is present, proceed to validation; if not present, skip entry type processing.
💻 Technical Criteria
Given An EDI message is received for SNP processing
When The system checks for the presence of an entry type code in the message
Then If entry type code is present, proceed to validation; if not present, skip entry type processing
R-GCX016E-cbl-00363 Valid EDI Format?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid EDI Format?' is invoked, and assuming that an entry type code is present in the edi message, when the system validates the format of the entry type code, the desired outcome is that if format is valid, proceed to conversion; if invalid, generate error message.
💻 Technical Criteria
Given An entry type code is present in the EDI message
When The system validates the format of the entry type code
Then If format is valid, proceed to conversion; if invalid, generate error message
R-GCX016E-cbl-00364 Code Found in Array?
Decision Rules
📊 Business Logic Narrative
When the process 'Code Found in Array?' is invoked, and assuming that a valid edi entry type code needs to be converted to internal format, when the system searches the conversion array for the edi code, the desired outcome is that if code is found in array, set internal entry type code; if not found, generate error message.
💻 Technical Criteria
Given A valid EDI entry type code needs to be converted to internal format
When The system searches the conversion array for the EDI code
Then If code is found in array, set internal entry type code; if not found, generate error message
R-GCX016E-cbl-00370 Log Entry Type Conversion
Process Rules
📊 Business Logic Narrative
When the process 'Log Entry Type Conversion' is invoked, and assuming that entry type conversion has been completed successfully, when the system logs the conversion activity, the desired outcome is that create audit log entry showing original edi code, converted internal code, and processing timestamp.
💻 Technical Criteria
Given Entry type conversion has been completed successfully
When The system logs the conversion activity
Then Create audit log entry showing original EDI code, converted internal code, and processing timestamp
R-GCX016E-cbl-00371 Generate Error Message
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error Message', assuming that entry type validation or conversion has failed, when the system encounters an invalid format or unknown code, the desired outcome is that generate appropriate error message indicating the nature of the entry type processing failure.
💻 Technical Criteria
EXCLUDING Entry type validation or conversion has failed
When The system encounters an invalid format or unknown code
Then Generate appropriate error message indicating the nature of the entry type processing failure
R-GCX016E-cbl-00383 Format FDA Reference Number with FDA PN Prefix
Computation Rules
📊 Business Logic Narrative
When the process 'Format FDA Reference Number with FDA PN Prefix' is invoked, and assuming that an a1 disposition code is being processed and n9 reference number segment is retrieved, when the system formats the fda reference number, the desired outcome is that the system applies fda pn prefix to the reference number.
💻 Technical Criteria
Given An A1 disposition code is being processed and N9 reference number segment is retrieved
When The system formats the FDA reference number
Then The system applies FDA PN prefix to the reference number
R-GCX016E-cbl-00384 Format FDA Reference Number with FDA Prefix
Computation Rules
📊 Business Logic Narrative
When the process 'Format FDA Reference Number with FDA Prefix' is invoked, and assuming that an a3 disposition code is being processed and n9 reference number segment is retrieved, when the system formats the fda reference number, the desired outcome is that the system applies fda prefix to the reference number.
💻 Technical Criteria
Given An A3 disposition code is being processed and N9 reference number segment is retrieved
When The system formats the FDA reference number
Then The system applies FDA prefix to the reference number
R-GCX016E-cbl-00385 Reposition Existing N9 Data
Process Rules
📊 Business Logic Narrative
When the process 'Reposition Existing N9 Data' is invoked, and assuming that fda reference number has been formatted with appropriate prefix, when the system updates the n9 segment, the desired outcome is that the system repositions existing n9 data to maintain proper segment structure.
💻 Technical Criteria
Given FDA reference number has been formatted with appropriate prefix
When The system updates the N9 segment
Then The system repositions existing N9 data to maintain proper segment structure
R-GCX016E-cbl-00386 Update N9 Reference Segment
Action Rules
📊 Business Logic Narrative
When the process 'Update N9 Reference Segment' is invoked, and assuming that n9 data has been repositioned and fda reference number is formatted, when the system updates the n9 reference segment, the desired outcome is that the system updates the n9 reference segment with the formatted fda reference number.
💻 Technical Criteria
Given N9 data has been repositioned and FDA reference number is formatted
When The system updates the N9 reference segment
Then The system updates the N9 reference segment with the formatted FDA reference number
R-GCX016E-cbl-00388 Log FDA Processing Action
Process Rules
📊 Business Logic Narrative
When the process 'Log FDA Processing Action' is invoked, and assuming that fda processing has been completed and n9 segment has been updated in database, when the system completes fda processing, the desired outcome is that the system logs the fda processing action for audit trail.
💻 Technical Criteria
Given FDA processing has been completed and N9 segment has been updated in database
When The system completes FDA processing
Then The system logs the FDA processing action for audit trail
R-GCX016E-cbl-00390 Freight Forwarder Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Freight Forwarder Found?' is invoked, and assuming that a search has been performed in the broker database for freight forwarder disposition codes, when the system evaluates the search results, the desired outcome is that if a freight forwarder is found, continue processing; otherwise, complete the process without further action.
💻 Technical Criteria
Given A search has been performed in the broker database for freight forwarder disposition codes
When The system evaluates the search results
Then If a freight forwarder is found, continue processing; otherwise, complete the process without further action
R-GCX016E-cbl-00395 Valid Email Address?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid Email Address?' is invoked, and assuming that an email address lookup has been performed for the freight forwarder, when the system evaluates the retrieved email address, the desired outcome is that if a valid email address exists, continue with email notification; otherwise, complete the process without sending email.
💻 Technical Criteria
Given An email address lookup has been performed for the freight forwarder
When The system evaluates the retrieved email address
Then If a valid email address exists, continue with email notification; otherwise, complete the process without sending email
R-GCX016E-cbl-00396 Build Comprehensive Email Content
Process Rules
📊 Business Logic Narrative
When the process 'Build Comprehensive Email Content' is invoked, and assuming that a valid email address has been found for the freight forwarder, when the system prepares the email notification, the desired outcome is that the system creates a structured email content framework ready for detailed information inclusion.
💻 Technical Criteria
Given A valid email address has been found for the freight forwarder
When The system prepares the email notification
Then The system creates a structured email content framework ready for detailed information inclusion
R-GCX016E-cbl-00402 Send Email Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send Email Notification' is invoked, and assuming that complete email content has been built with all required information, when the system attempts to send the email notification, the desired outcome is that the system transmits the email to the freight forwarder's email address.
💻 Technical Criteria
Given Complete email content has been built with all required information
When The system attempts to send the email notification
Then The system transmits the email to the freight forwarder's email address
R-GCX016E-cbl-00403 Email Delivery Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Email Delivery Successful?' is invoked, and assuming that an email notification has been sent to the freight forwarder, when the system receives delivery confirmation or failure notification, the desired outcome is that if delivery is successful, log the success; otherwise, initiate retry process.
💻 Technical Criteria
Given An email notification has been sent to the freight forwarder
When The system receives delivery confirmation or failure notification
Then If delivery is successful, log the success; otherwise, initiate retry process
R-GCX016E-cbl-00404 Log Successful Delivery
Process Rules
📊 Business Logic Narrative
When the process 'Log Successful Delivery' is invoked, and assuming that email delivery has been confirmed as successful, when the system processes the successful delivery confirmation, the desired outcome is that the system creates a log entry recording the successful email delivery with timestamp and recipient information.
💻 Technical Criteria
Given Email delivery has been confirmed as successful
When The system processes the successful delivery confirmation
Then The system creates a log entry recording the successful email delivery with timestamp and recipient information
R-GCX016E-cbl-00405 Retry Email Delivery
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Retry Email Delivery', assuming that email delivery has failed, when the system has not reached the retry limit, the desired outcome is that the system attempts to resend the email notification.
💻 Technical Criteria
EXCLUDING Email delivery has failed
When The system has not reached the retry limit
Then The system attempts to resend the email notification
R-GCX016E-cbl-00407 Log Delivery Failure
Process Rules
📊 Business Logic Narrative
When the process 'Log Delivery Failure' is invoked, and assuming that email delivery has failed and retry limit has been reached, when the system processes the final delivery failure, the desired outcome is that the system creates a log entry recording the email delivery failure with error details and attempted recipient information.
💻 Technical Criteria
Given Email delivery has failed and retry limit has been reached
When The system processes the final delivery failure
Then The system creates a log entry recording the email delivery failure with error details and attempted recipient information
R-GCX016E-cbl-00408 Process Complete
Process Rules
📊 Business Logic Narrative
When the process 'Process Complete' is invoked, and assuming that email notification process has reached a terminal state (success, failure, or no freight forwarder found), when the system finalizes the notification process, the desired outcome is that the system marks the freight forwarder notification process as complete and returns control to the calling process.
💻 Technical Criteria
Given Email notification process has reached a terminal state (success, failure, or no freight forwarder found)
When The system finalizes the notification process
Then The system marks the freight forwarder notification process as complete and returns control to the calling process
R-GCX016E-cbl-00413 Add New Status Entry to Array
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Add New Status Entry to Array', assuming that a disposition code is confirmed as new and not duplicate, when adding the code to the status array, the desired outcome is that the system creates a new status array entry with the disposition code, quantity, entry number, date/time, and assigns the next sequential number while incrementing the array occurrence count.
💻 Technical Criteria
EXCLUDING A disposition code is confirmed as new and not duplicate
When Adding the code to the status array
Then The system creates a new status array entry with the disposition code, quantity, entry number, date/time, and assigns the next sequential number while incrementing the array occurrence count
R-GCX016E-cbl-00415 Remove Counterpart Disposition Codes
Decision Rules
📊 Business Logic Narrative
When the process 'Remove Counterpart Disposition Codes' is invoked, and assuming that a disposition code has defined counterpart codes in the system, when adding the primary disposition code to the status array, the desired outcome is that the system identifies and removes any existing counterpart disposition codes from the status arrays and decrements the occurrence counts accordingly.
💻 Technical Criteria
Given A disposition code has defined counterpart codes in the system
When Adding the primary disposition code to the status array
Then The system identifies and removes any existing counterpart disposition codes from the status arrays and decrements the occurrence counts accordingly
R-GCX016E-cbl-00418 Convert Arrays to Database Format
Process Rules
📊 Business Logic Narrative
When the process 'Convert Arrays to Database Format' is invoked, and assuming that status arrays have been processed and finalized in memory, when preparing to update the database, the desired outcome is that the system converts the s09a status arrays into s09 database segment format with proper field mapping, data formatting, and segment structure.
💻 Technical Criteria
Given Status arrays have been processed and finalized in memory
When Preparing to update the database
Then The system converts the S09A status arrays into S09 database segment format with proper field mapping, data formatting, and segment structure
R-GCX016E-cbl-00426 Include Quantities in Message
Process Rules
📊 Business Logic Narrative
When the process 'Include Quantities in Message' is invoked, and assuming that a follower manifest message is being prepared and quantity information exists, when the message content is assembled, the desired outcome is that all relevant quantity information is included in the follower manifest message.
💻 Technical Criteria
Given A follower manifest message is being prepared AND quantity information exists
When The message content is assembled
Then All relevant quantity information is included in the follower manifest message
R-GCX016E-cbl-00428 Spawn GCT0162E Transaction for Follower Processing
Action Rules
📊 Business Logic Narrative
When the process 'Spawn GCT0162E Transaction for Follower Processing' is invoked, and assuming that a follower manifest message has been prepared with all required information, when the system is ready to process the follower manifest, the desired outcome is that a gct0162e transaction is spawned with the prepared message content for follower manifest processing.
💻 Technical Criteria
Given A follower manifest message has been prepared with all required information
When The system is ready to process the follower manifest
Then A GCT0162E transaction is spawned with the prepared message content for follower manifest processing
R-GCX016E-cbl-00445 Log Transit Processing
Process Rules
📊 Business Logic Narrative
When the process 'Log Transit Processing' is invoked, and assuming that transit notifications have been generated, when the system logs processing activities, the desired outcome is that all transit processing activities are logged with timestamps and details for audit trail and tracking purposes.
💻 Technical Criteria
Given Transit notifications have been generated
When The system logs processing activities
Then All transit processing activities are logged with timestamps and details for audit trail and tracking purposes
R-GCX016E-cbl-00471 Handle SCAC Unknown Scenarios
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Handle SCAC Unknown Scenarios', assuming that cprs traffic is being processed, when the scac code is unknown or not available, the desired outcome is that the system applies default scac handling rules and prepares for key renumbering.
💻 Technical Criteria
EXCLUDING CPRS traffic is being processed
When The SCAC code is unknown or not available
Then The system applies default SCAC handling rules and prepares for key renumbering
R-GCX016E-cbl-00499 Log Hold Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Hold Action' is invoked, and assuming that a disposition code is classified as a hold action type, when the system processes the hold disposition code, the desired outcome is that the system must log the hold action with disposition code details and action description.
💻 Technical Criteria
Given A disposition code is classified as a hold action type
When The system processes the hold disposition code
Then The system must log the hold action with disposition code details and action description
R-GCX016E-cbl-00500 Log Release Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Release Action' is invoked, and assuming that a disposition code is classified as a release action type, when the system processes the release disposition code, the desired outcome is that the system must log the release action with disposition code details and action description.
💻 Technical Criteria
Given A disposition code is classified as a release action type
When The system processes the release disposition code
Then The system must log the release action with disposition code details and action description
R-GCX016E-cbl-00501 Log Arrival Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Arrival Action' is invoked, and assuming that a disposition code is classified as an arrival action type, when the system processes the arrival disposition code, the desired outcome is that the system must log the arrival action with disposition code details and action description.
💻 Technical Criteria
Given A disposition code is classified as an arrival action type
When The system processes the arrival disposition code
Then The system must log the arrival action with disposition code details and action description
R-GCX016E-cbl-00503 Log Seizure Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Seizure Action' is invoked, and assuming that a disposition code is classified as a seizure action type, when the system processes the seizure disposition code, the desired outcome is that the system must log the seizure action with disposition code details and action description.
💻 Technical Criteria
Given A disposition code is classified as a seizure action type
When The system processes the seizure disposition code
Then The system must log the seizure action with disposition code details and action description
R-GCX016E-cbl-00504 Log Status Information
Process Rules
📊 Business Logic Narrative
When the process 'Log Status Information' is invoked, and assuming that a disposition code is classified as status information type, when the system processes the status information disposition code, the desired outcome is that the system must log the status information with disposition code details and action description.
💻 Technical Criteria
Given A disposition code is classified as status information type
When The system processes the status information disposition code
Then The system must log the status information with disposition code details and action description
R-GCX016E-cbl-00505 Log Cancellation Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Cancellation Action' is invoked, and assuming that a disposition code is classified as a cancellation action type, when the system processes the cancellation disposition code, the desired outcome is that the system must log the cancellation action with disposition code details and action description.
💻 Technical Criteria
Given A disposition code is classified as a cancellation action type
When The system processes the cancellation disposition code
Then The system must log the cancellation action with disposition code details and action description
R-GCX016E-cbl-00510 Add User Information
Process Rules
📊 Business Logic Narrative
When the process 'Add User Information' is invoked, and assuming that a log message has disposition code details added, when the system adds user information to the log message, the desired outcome is that the system must include the user id who initiated the disposition code action in the log message.
💻 Technical Criteria
Given A log message has disposition code details added
When The system adds user information to the log message
Then The system must include the user ID who initiated the disposition code action in the log message
R-GCX016E-cbl-00511 Spawn GCT1051E Transaction
Action Rules
📊 Business Logic Narrative
When the process 'Spawn GCT1051E Transaction' is invoked, and assuming that a complete log message with all required information has been prepared, when the system spawns gct1051e transaction for logging, the desired outcome is that the system must invoke gct1051e transaction with the complete log message for processing.
💻 Technical Criteria
Given A complete log message with all required information has been prepared
When The system spawns GCT1051E transaction for logging
Then The system must invoke GCT1051E transaction with the complete log message for processing
R-GCX016E-cbl-00513 Logging Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Logging Successful?' is invoked, and assuming that the audit trail write operation has been attempted, when the system validates logging success, the desired outcome is that the system must determine if the logging was successful or if an error occurred during the process.
💻 Technical Criteria
Given The audit trail write operation has been attempted
When The system validates logging success
Then The system must determine if the logging was successful or if an error occurred during the process
R-GCX016E-cbl-00518 Extract Free-Form Text
Process Rules
📊 Business Logic Narrative
When the process 'Extract Free-Form Text' is invoked, and assuming that a k1 segment contains free-form text data, when the system processes the k1 segment, the desired outcome is that the free-form text content is extracted and prepared for validation.
💻 Technical Criteria
Given A K1 segment contains free-form text data
When The system processes the K1 segment
Then The free-form text content is extracted and prepared for validation
R-GCX016E-cbl-00519 Text Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Text Valid?' is invoked, and assuming that free-form text has been extracted from k1 segment, when the system validates the text content, the desired outcome is that the text is either accepted as valid for further processing or rejected if it fails validation criteria.
💻 Technical Criteria
Given Free-form text has been extracted from K1 segment
When The system validates the text content
Then The text is either accepted as valid for further processing or rejected if it fails validation criteria
R-GCX016E-cbl-00520 Store K1 Message for Train
Process Rules
📊 Business Logic Narrative
When the process 'Store K1 Message for Train' is invoked, and assuming that a valid k1 message is classified as train-related, when the system processes the validated k1 content, the desired outcome is that the k1 message is stored in train message repository for inclusion in train notifications.
💻 Technical Criteria
Given A valid K1 message is classified as train-related
When The system processes the validated K1 content
Then The K1 message is stored in train message repository for inclusion in train notifications
R-GCX016E-cbl-00523 Associate with Disposition Code
Process Rules
📊 Business Logic Narrative
When the process 'Associate with Disposition Code' is invoked, and assuming that a k1 message has been logged and processed, when the system identifies related disposition codes, the desired outcome is that the k1 message is associated with the appropriate disposition code for combined processing.
💻 Technical Criteria
Given A K1 message has been logged and processed
When The system identifies related disposition codes
Then The K1 message is associated with the appropriate disposition code for combined processing
R-GCX016E-cbl-00538 Send Error to Merlin System
Action Rules
📊 Business Logic Narrative
When the process 'Send Error to Merlin System' is invoked, and assuming that the cprs error message is formatted and typed, when the system sends the error to merlin, the desired outcome is that the error message is transmitted to the merlin system for distribution.
💻 Technical Criteria
Given The CPRS error message is formatted and typed
When The system sends the error to Merlin
Then The error message is transmitted to the Merlin system for distribution
R-GCX016E-cbl-00539 Log CPRS Error for Audit
Process Rules
📊 Business Logic Narrative
When the process 'Log CPRS Error for Audit' is invoked, and assuming that the error message has been sent to merlin system, when the system performs audit logging, the desired outcome is that the cprs error is recorded in audit logs with appropriate details.
💻 Technical Criteria
Given The error message has been sent to Merlin system
When The system performs audit logging
Then The CPRS error is recorded in audit logs with appropriate details
R-GCX016E-cbl-00542 Validate Train ID from M10 Segment
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Train ID from M10 Segment' is invoked, and assuming that an oca disposition code is received for a train and m10 segment contains train identification information, when the system processes the m10 segment to extract and validate train id, the desired outcome is that the train id is validated against available train data for further processing.
💻 Technical Criteria
Given An OCA disposition code is received for a train AND M10 segment contains train identification information
When The system processes the M10 segment to extract and validate train ID
Then The train ID is validated against available train data for further processing
R-GCX016E-cbl-00543 Train Found in USCS System?
Decision Rules
📊 Business Logic Narrative
When the process 'Train Found in USCS System?' is invoked, and assuming that a validated train id from m10 segment processing, when the system searches for the train in uscs train list segments, the desired outcome is that if train is found, proceed to arrival status check or if train is not found, generate train not arrived warning.
💻 Technical Criteria
Given A validated train ID from M10 segment processing
When The system searches for the train in USCS train list segments
Then If train is found, proceed to arrival status check OR if train is not found, generate train not arrived warning
R-GCX016E-cbl-00544 Check Train Arrival Status
Action Rules
📊 Business Logic Narrative
When the process 'Check Train Arrival Status' is invoked, and assuming that a train exists in the uscs system, when the system checks the train's current arrival status information, the desired outcome is that the arrival status is retrieved and made available for arrival validation.
💻 Technical Criteria
Given A train exists in the USCS system
When The system checks the train's current arrival status information
Then The arrival status is retrieved and made available for arrival validation
R-GCX016E-cbl-00545 Train Already Arrived?
Decision Rules
📊 Business Logic Narrative
When the process 'Train Already Arrived?' is invoked, and assuming that train arrival status information is available, when the system evaluates if the train status indicates it has already arrived, the desired outcome is that if train has already arrived, end oca processing or if train has not arrived, generate train not arrived warning.
💻 Technical Criteria
Given Train arrival status information is available
When The system evaluates if the train status indicates it has already arrived
Then If train has already arrived, end OCA processing OR if train has not arrived, generate train not arrived warning
R-GCX016E-cbl-00546 Generate Train Not Arrived Warning
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Train Not Arrived Warning', assuming that train is not found in uscs system or train exists but has not arrived, when the system processes oca disposition code for the train, the desired outcome is that a train not arrived warning is generated for further processing.
💻 Technical Criteria
EXCLUDING Train is not found in USCS system OR train exists but has not arrived
When The system processes OCA disposition code for the train
Then A train not arrived warning is generated for further processing
R-GCX016E-cbl-00547 Log Warning Message with Train Details
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Warning Message with Train Details', assuming that a train not arrived warning has been generated, when the system logs the warning message, the desired outcome is that warning message is recorded with complete train details including train id and relevant context information.
💻 Technical Criteria
EXCLUDING A train not arrived warning has been generated
When The system logs the warning message
Then Warning message is recorded with complete train details including train ID and relevant context information
R-GCX016E-cbl-00548 Create Merlin Warning Notification
Action Rules
📊 Business Logic Narrative
When the process 'Create Merlin Warning Notification' is invoked, and assuming that warning message with train details has been logged, when the system creates merlin notification for the warning, the desired outcome is that merlin warning notification is created and prepared for delivery to operations team.
💻 Technical Criteria
Given Warning message with train details has been logged
When The system creates Merlin notification for the warning
Then Merlin warning notification is created and prepared for delivery to operations team
R-GCX016E-cbl-00551 Send Warning to Operations Team
Action Rules
📊 Business Logic Narrative
When the process 'Send Warning to Operations Team' is invoked, and assuming that warning notification is complete with train details and re-arrival flag is set, when the system sends the warning to operations team, the desired outcome is that warning notification is successfully delivered to operations team for immediate attention.
💻 Technical Criteria
Given Warning notification is complete with train details and re-arrival flag is set
When The system sends the warning to operations team
Then Warning notification is successfully delivered to operations team for immediate attention
R-GCX016E-cbl-00552 Update Train Status for Re-processing
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Status for Re-processing' is invoked, and assuming that warning has been sent to operations team, when the system updates train status for re-processing, the desired outcome is that train status is updated to indicate warning condition and readiness for re-processing upon actual arrival.
💻 Technical Criteria
Given Warning has been sent to operations team
When The system updates train status for re-processing
Then Train status is updated to indicate warning condition and readiness for re-processing upon actual arrival
R-GCX016E-cbl-00553 End OCA Processing
Process Rules
📊 Business Logic Narrative
When the process 'End OCA Processing' is invoked, and assuming that train has already arrived or train status has been updated for re-processing after warning, when the system completes oca processing, the desired outcome is that oca disposition code processing is completed and system is ready for next transaction.
💻 Technical Criteria
Given Train has already arrived OR train status has been updated for re-processing after warning
When The system completes OCA processing
Then OCA disposition code processing is completed and system is ready for next transaction
R-GCX016E-cbl-00554 Receive COC Disposition Code
Decision Rules
📊 Business Logic Narrative
When the process 'Receive COC Disposition Code' is invoked, and assuming that a message segment contains a disposition code, when the disposition code is 'coc', the desired outcome is that the system initiates train arrival cancellation processing.
💻 Technical Criteria
Given A message segment contains a disposition code
When The disposition code is 'COC'
Then The system initiates train arrival cancellation processing
R-GCX016E-cbl-00555 Validate Train ID from M10 Segment
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Train ID from M10 Segment' is invoked, and assuming that an m10 segment contains vessel/train information, when processing a coc disposition code, the desired outcome is that the system extracts the train id from the m10 segment for validation.
💻 Technical Criteria
Given An M10 segment contains vessel/train information
When Processing a COC disposition code
Then The system extracts the train ID from the M10 segment for validation
R-GCX016E-cbl-00557 Log Train Arrival Cancellation Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Train Arrival Cancellation Action' is invoked, and assuming that a valid train has been found in the system, when processing a coc disposition code for train arrival cancellation, the desired outcome is that the system logs the cancellation action with train details and timestamp.
💻 Technical Criteria
Given A valid train has been found in the system
When Processing a COC disposition code for train arrival cancellation
Then The system logs the cancellation action with train details and timestamp
R-GCX016E-cbl-00558 Update Train Status to Cancel Arrival
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Status to Cancel Arrival' is invoked, and assuming that a train arrival cancellation has been logged, when the train status needs to be updated, the desired outcome is that the system sets the train status to cancel arrival state.
💻 Technical Criteria
Given A train arrival cancellation has been logged
When The train status needs to be updated
Then The system sets the train status to cancel arrival state
R-GCX016E-cbl-00561 Generate CBP Cancellation Warning Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate CBP Cancellation Warning Message' is invoked, and assuming that a train arrival has been successfully cancelled, when cbp notification is required, the desired outcome is that the system generates a cbp cancellation warning message.
💻 Technical Criteria
Given A train arrival has been successfully cancelled
When CBP notification is required
Then The system generates a CBP cancellation warning message
R-GCX016E-cbl-00562 Format Warning with Train Details
Process Rules
📊 Business Logic Narrative
When the process 'Format Warning with Train Details' is invoked, and assuming that a cbp cancellation warning message needs to be created, when formatting the message content, the desired outcome is that the system includes train id, cancellation timestamp, and relevant train details in the message.
💻 Technical Criteria
Given A CBP cancellation warning message needs to be created
When Formatting the message content
Then The system includes train ID, cancellation timestamp, and relevant train details in the message
R-GCX016E-cbl-00563 Include Cancellation Reason from K1 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Include Cancellation Reason from K1 Segment' is invoked, and assuming that a k1 segment contains cancellation reason comments, when formatting the cbp warning message, the desired outcome is that the system includes the cancellation reason from the k1 segment in the warning message.
💻 Technical Criteria
Given A K1 segment contains cancellation reason comments
When Formatting the CBP warning message
Then The system includes the cancellation reason from the K1 segment in the warning message
R-GCX016E-cbl-00564 Send Warning to Merlin Message System
Action Rules
📊 Business Logic Narrative
When the process 'Send Warning to Merlin Message System' is invoked, and assuming that a formatted cbp cancellation warning message is ready, when the message needs to be transmitted, the desired outcome is that the system sends the warning message to the merlin message system.
💻 Technical Criteria
Given A formatted CBP cancellation warning message is ready
When The message needs to be transmitted
Then The system sends the warning message to the Merlin message system
R-GCX016E-cbl-00565 Log Cancellation Event for Audit Trail
Process Rules
📊 Business Logic Narrative
When the process 'Log Cancellation Event for Audit Trail' is invoked, and assuming that a train arrival cancellation has been processed and message sent, when creating audit trail records, the desired outcome is that the system logs the complete cancellation event with all relevant details for audit purposes.
💻 Technical Criteria
Given A train arrival cancellation has been processed and message sent
When Creating audit trail records
Then The system logs the complete cancellation event with all relevant details for audit purposes
R-GCX016E-cbl-00567 Send Error Message to Operations
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Send Error Message to Operations', assuming that a train not found error has been generated, when operations notification is required, the desired outcome is that the system sends the error message to operations personnel for resolution.
💻 Technical Criteria
EXCLUDING A train not found error has been generated
When Operations notification is required
Then The system sends the error message to operations personnel for resolution
R-GCX016E-cbl-00585 Status Array Modified?
Decision Rules
📊 Business Logic Narrative
When the process 'Status Array Modified?' is invoked, and assuming that status array updates have been processed, when the system checks for modifications, the desired outcome is that if arrays were modified, convert to database format and update; if not, end processing.
💻 Technical Criteria
Given Status array updates have been processed
When The system checks for modifications
Then If arrays were modified, convert to database format and update; if not, end processing
R-GCX016E-cbl-00586 Convert Status Arrays to Database Format
Process Rules
📊 Business Logic Narrative
When the process 'Convert Status Arrays to Database Format' is invoked, and assuming that status arrays have been modified during processing, when the system converts arrays to database format, the desired outcome is that status information is formatted into s09 segments ready for database storage.
💻 Technical Criteria
Given Status arrays have been modified during processing
When The system converts arrays to database format
Then Status information is formatted into S09 segments ready for database storage
R-GCX016E-cbl-00589 Confirm Status Segment Updates
Validation Rules
📊 Business Logic Narrative
When the process 'Confirm Status Segment Updates' is invoked, and assuming that status segments have been replaced in the database, when the system confirms the update operation, the desired outcome is that status segment processing is confirmed as complete and successful.
💻 Technical Criteria
Given Status segments have been replaced in the database
When The system confirms the update operation
Then Status segment processing is confirmed as complete and successful
R-GCX016E-cbl-02955 Database Segments Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Database Segments Found?' is invoked, and assuming that the system has attempted to retrieve s09 status segments from database, when the database query completes, the desired outcome is that the system determines if any status segments were found and branches processing accordingly.
💻 Technical Criteria
Given The system has attempted to retrieve S09 status segments from database
When The database query completes
Then The system determines if any status segments were found and branches processing accordingly
R-GCX016E-cbl-02958 Convert Database Segment to Array Format
Process Rules
📊 Business Logic Narrative
When the process 'Convert Database Segment to Array Format' is invoked, and assuming that a status segment exists in the database, when the system processes the segment for array population, the desired outcome is that the system converts the database segment format into the s09a array entry format.
💻 Technical Criteria
Given A status segment exists in the database
When The system processes the segment for array population
Then The system converts the database segment format into the S09A array entry format
R-GCX016E-cbl-02960 Populate Array Entry with Disposition Code
Process Rules
📊 Business Logic Narrative
When the process 'Populate Array Entry with Disposition Code' is invoked, and assuming that a database status segment contains a disposition code, when the segment is being converted to array format, the desired outcome is that the system populates the disposition code field in the corresponding array entry.
💻 Technical Criteria
Given A database status segment contains a disposition code
When The segment is being converted to array format
Then The system populates the disposition code field in the corresponding array entry
R-GCX016E-cbl-02961 Populate Array Entry with Date/Time
Process Rules
📊 Business Logic Narrative
When the process 'Populate Array Entry with Date/Time' is invoked, and assuming that a database status segment contains date and time information, when the segment is being converted to array format, the desired outcome is that the system populates the date and time fields in the corresponding array entry.
💻 Technical Criteria
Given A database status segment contains date and time information
When The segment is being converted to array format
Then The system populates the date and time fields in the corresponding array entry
R-GCX016E-cbl-02963 Populate Array Entry with Quantity Information
Process Rules
📊 Business Logic Narrative
When the process 'Populate Array Entry with Quantity Information' is invoked, and assuming that a database status segment contains quantity information, when the segment is being converted to array format, the desired outcome is that the system populates the quantity fields in the corresponding array entry.
💻 Technical Criteria
Given A database status segment contains quantity information
When The segment is being converted to array format
Then The system populates the quantity fields in the corresponding array entry
R-GCX016E-cbl-02964 More Database Segments?
Decision Rules
📊 Business Logic Narrative
When the process 'More Database Segments?' is invoked, and assuming that the system has processed one or more status segments, when a segment conversion is complete, the desired outcome is that the system checks if additional segments remain in the database for processing.
💻 Technical Criteria
Given The system has processed one or more status segments
When A segment conversion is complete
Then The system checks if additional segments remain in the database for processing
R-GCX016E-cbl-02965 Increment Array Index
Process Rules
📊 Business Logic Narrative
When the process 'Increment Array Index' is invoked, and assuming that a status segment has been successfully converted and stored in the array, when additional segments remain to be processed, the desired outcome is that the system increments the array index to the next available position.
💻 Technical Criteria
Given A status segment has been successfully converted and stored in the array
When Additional segments remain to be processed
Then The system increments the array index to the next available position
R-GCX016E-cbl-02966 Update Maximum Sequences Fetched Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Update Maximum Sequences Fetched Counter' is invoked, and assuming that all status segments have been processed from the database, when the segment processing loop completes, the desired outcome is that the system updates the maximum sequences fetched counter with the total number of segments processed.
💻 Technical Criteria
Given All status segments have been processed from the database
When The segment processing loop completes
Then The system updates the maximum sequences fetched counter with the total number of segments processed
R-GCX016E-cbl-03220 Segment Retrieved Successfully?
Validation Rules
📊 Business Logic Narrative
When the process 'Segment Retrieved Successfully?' is invoked, and assuming that an attempt has been made to retrieve s09 status segment from database, when the system checks the retrieval operation result, the desired outcome is that if segment was found and retrieved, proceed to format validation, otherwise initiate corrupted segment recovery.
💻 Technical Criteria
Given An attempt has been made to retrieve S09 status segment from database
When The system checks the retrieval operation result
Then If segment was found and retrieved, proceed to format validation, otherwise initiate corrupted segment recovery
R-GCX016E-cbl-03221 Check Segment Format Structure
Validation Rules
📊 Business Logic Narrative
When the process 'Check Segment Format Structure' is invoked, and assuming that an s09 status segment has been successfully retrieved from database, when the system examines the segment format structure, the desired outcome is that the segment structure is validated against expected format specifications.
💻 Technical Criteria
Given An S09 status segment has been successfully retrieved from database
When The system examines the segment format structure
Then The segment structure is validated against expected format specifications
R-GCX016E-cbl-03226 Data Integrity Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Data Integrity Valid?' is invoked, and assuming that data integrity fields in s09 segment have been checked, when the system evaluates data integrity validity, the desired outcome is that if data integrity is valid, initialize status array from segment, otherwise log integrity error and apply correction rules.
💻 Technical Criteria
Given Data integrity fields in S09 segment have been checked
When The system evaluates data integrity validity
Then If data integrity is valid, initialize status array from segment, otherwise log integrity error and apply correction rules
R-GCX016E-cbl-03230 Handle Corrupted Segment Recovery
Process Rules
📊 Business Logic Narrative
When the process 'Handle Corrupted Segment Recovery' is invoked, and assuming that s09 segment retrieval has failed or segment is corrupted, when the system detects segment unavailability or corruption, the desired outcome is that recovery procedures are initiated to attempt segment reconstruction.
💻 Technical Criteria
Given S09 segment retrieval has failed or segment is corrupted
When The system detects segment unavailability or corruption
Then Recovery procedures are initiated to attempt segment reconstruction
R-GCX016E-cbl-03231 Log Segment Format Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Segment Format Error', assuming that s09 segment format validation has failed, when the system detects invalid segment format, the desired outcome is that format error is logged with details for troubleshooting and segment reconstruction is attempted.
💻 Technical Criteria
EXCLUDING S09 segment format validation has failed
When The system detects invalid segment format
Then Format error is logged with details for troubleshooting and segment reconstruction is attempted
R-GCX016E-cbl-03237 Log Data Integrity Error
Process Rules
📊 Business Logic Narrative
When the process 'Log Data Integrity Error' is invoked, and assuming that data integrity validation has failed, when the system detects data integrity issues, the desired outcome is that data integrity error is logged and correction rules are applied.
💻 Technical Criteria
Given Data integrity validation has failed
When The system detects data integrity issues
Then Data integrity error is logged and correction rules are applied
R-GCX016E-cbl-03238 Apply Data Correction Rules
Process Rules
📊 Business Logic Narrative
When the process 'Apply Data Correction Rules' is invoked, and assuming that data integrity errors have been detected and logged, when the system applies data correction rules, the desired outcome is that data integrity issues are corrected and status array initialization proceeds.
💻 Technical Criteria
Given Data integrity errors have been detected and logged
When The system applies data correction rules
Then Data integrity issues are corrected and status array initialization proceeds
R-GCX016E-cbl-03240 Validation Failed - Segment Rejected
Process Rules
📊 Business Logic Narrative
When the process 'Validation Failed - Segment Rejected' is invoked, and assuming that s09 segment validation has failed and recovery attempts were unsuccessful, when the system cannot establish valid segment data, the desired outcome is that segment is rejected and default processing procedures are applied.
💻 Technical Criteria
Given S09 segment validation has failed and recovery attempts were unsuccessful
When The system cannot establish valid segment data
Then Segment is rejected and default processing procedures are applied
R-GCX016E-cbl-03381 Valid Segment Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid Segment Found?' is invoked, and assuming that a database query for s09 status segment has been executed, when the system checks if a valid segment was found, the desired outcome is that the system should determine if segment data exists and is accessible for processing.
💻 Technical Criteria
Given A database query for S09 status segment has been executed
When The system checks if a valid segment was found
Then The system should determine if segment data exists and is accessible for processing
R-GCX016E-cbl-03382 Validate Segment Structure
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Segment Structure' is invoked, and assuming that a status segment has been retrieved from the database, when the system validates the segment structure, the desired outcome is that the system should verify that the segment contains valid data fields, proper formatting, and required elements.
💻 Technical Criteria
Given A status segment has been retrieved from the database
When The system validates the segment structure
Then The system should verify that the segment contains valid data fields, proper formatting, and required elements
R-GCX016E-cbl-03383 Segment Structure Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Segment Structure Valid?' is invoked, and assuming that a status segment structure validation has been performed, when the system evaluates the validation results, the desired outcome is that the system should determine if the segment structure meets required standards for array population.
💻 Technical Criteria
Given A status segment structure validation has been performed
When The system evaluates the validation results
Then The system should determine if the segment structure meets required standards for array population
R-GCX016E-cbl-03384 Initialize S09A Status Array
Process Rules
📊 Business Logic Narrative
When the process 'Initialize S09A Status Array' is invoked, and assuming that a valid status segment has been retrieved and validated, when the system initializes the s09a status array, the desired outcome is that the system should set up the array structure with proper indexing and prepare it for data population.
💻 Technical Criteria
Given A valid status segment has been retrieved and validated
When The system initializes the S09A status array
Then The system should set up the array structure with proper indexing and prepare it for data population
R-GCX016E-cbl-03389 Set Array Initialization Complete Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Array Initialization Complete Flag' is invoked, and assuming that all available status segments have been processed, when the system completes array initialization, the desired outcome is that the system should set a completion flag indicating that status array population is finished.
💻 Technical Criteria
Given All available status segments have been processed
When The system completes array initialization
Then The system should set a completion flag indicating that status array population is finished
R-GCX016E-cbl-03390 Log Array Population Results
Process Rules
📊 Business Logic Narrative
When the process 'Log Array Population Results' is invoked, and assuming that status array initialization has been completed, when the system logs array population results, the desired outcome is that the system should record the number of segments processed, array entries created, and completion status.
💻 Technical Criteria
Given Status array initialization has been completed
When The system logs array population results
Then The system should record the number of segments processed, array entries created, and completion status
R-GCX016E-cbl-03391 Set Error Flag for Invalid Structure
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Error Flag for Invalid Structure', assuming that a status segment has failed structure validation, when the system handles the invalid structure, the desired outcome is that the system should set an error flag indicating that segment structure is invalid and cannot be processed.
💻 Technical Criteria
EXCLUDING A status segment has failed structure validation
When The system handles the invalid structure
Then The system should set an error flag indicating that segment structure is invalid and cannot be processed
R-GCX016E-cbl-03392 Handle Invalid Segment Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Handle Invalid Segment Error', assuming that an invalid status segment has been identified, when the system handles the invalid segment error, the desired outcome is that the system should process the error condition and take appropriate corrective action.
💻 Technical Criteria
EXCLUDING An invalid status segment has been identified
When The system handles the invalid segment error
Then The system should process the error condition and take appropriate corrective action
R-GCX016E-cbl-03490 Segment Retrieved Successfully?
Validation Rules
📊 Business Logic Narrative
When the process 'Segment Retrieved Successfully?' is invoked, and assuming that an attempt has been made to retrieve s09 segment from database, when the system checks the retrieval operation result, the desired outcome is that if segment is retrieved successfully, proceed to format validation, otherwise log validation error.
💻 Technical Criteria
Given An attempt has been made to retrieve S09 segment from database
When The system checks the retrieval operation result
Then If segment is retrieved successfully, proceed to format validation, otherwise log validation error
R-GCX016E-cbl-03491 Validate Segment Format Structure
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Segment Format Structure' is invoked, and assuming that an s09 segment has been successfully retrieved from database, when the system validates the segment format structure, the desired outcome is that the segment format must conform to s09 structure requirements to proceed to field integrity validation.
💻 Technical Criteria
Given An S09 segment has been successfully retrieved from database
When The system validates the segment format structure
Then The segment format must conform to S09 structure requirements to proceed to field integrity validation
R-GCX016E-cbl-03492 Format Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Format Valid?' is invoked, and assuming that s09 segment format structure has been validated, when the system evaluates format validity, the desired outcome is that if format is valid, proceed to field integrity check, otherwise log validation error.
💻 Technical Criteria
Given S09 segment format structure has been validated
When The system evaluates format validity
Then If format is valid, proceed to field integrity check, otherwise log validation error
R-GCX016E-cbl-03493 Check Field Integrity
Validation Rules
📊 Business Logic Narrative
When the process 'Check Field Integrity' is invoked, and assuming that s09 segment has valid format structure, when the system checks field integrity of the segment, the desired outcome is that all required fields must be present and properly formatted to proceed to data consistency validation.
💻 Technical Criteria
Given S09 segment has valid format structure
When The system checks field integrity of the segment
Then All required fields must be present and properly formatted to proceed to data consistency validation
R-GCX016E-cbl-03494 Fields Complete?
Decision Rules
📊 Business Logic Narrative
When the process 'Fields Complete?' is invoked, and assuming that s09 segment field integrity has been validated, when the system evaluates field completeness, the desired outcome is that if all fields are complete, proceed to data consistency validation, otherwise log validation error.
💻 Technical Criteria
Given S09 segment field integrity has been validated
When The system evaluates field completeness
Then If all fields are complete, proceed to data consistency validation, otherwise log validation error
R-GCX016E-cbl-03500 Status Codes Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Status Codes Valid?' is invoked, and assuming that s09 segment status codes have been validated, when the system evaluates status code validity, the desired outcome is that if status codes are valid, mark segment as valid, otherwise log validation error.
💻 Technical Criteria
Given S09 segment status codes have been validated
When The system evaluates status code validity
Then If status codes are valid, mark segment as valid, otherwise log validation error
R-GCX016E-cbl-03501 Mark Segment as Valid
Process Rules
📊 Business Logic Narrative
When the process 'Mark Segment as Valid' is invoked, and assuming that s09 segment has passed all validation checks including status codes, when the system marks the segment as valid, the desired outcome is that the segment is flagged as valid and ready for status array population processing.
💻 Technical Criteria
Given S09 segment has passed all validation checks including status codes
When The system marks the segment as valid
Then The segment is flagged as valid and ready for status array population processing
R-GCX016E-cbl-03502 Log Validation Error
Process Rules
📊 Business Logic Narrative
When the process 'Log Validation Error' is invoked, and assuming that s09 segment has failed any validation check during the validation process, when the system encounters a validation failure, the desired outcome is that a validation error is logged with appropriate error details for troubleshooting.
💻 Technical Criteria
Given S09 segment has failed any validation check during the validation process
When The system encounters a validation failure
Then A validation error is logged with appropriate error details for troubleshooting
R-GCX016E-cbl-03503 Set Error Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Error Flag' is invoked, and assuming that a validation error has been logged for the s09 segment, when the system sets the error flag, the desired outcome is that the error flag is set to indicate validation failure and prevent invalid segment processing.
💻 Technical Criteria
Given A validation error has been logged for the S09 segment
When The system sets the error flag
Then The error flag is set to indicate validation failure and prevent invalid segment processing
R-GCX016E-cbl-03505 Skip Invalid Segment
Process Rules
📊 Business Logic Narrative
When the process 'Skip Invalid Segment' is invoked, and assuming that s09 segment has failed validation and error flag has been set, when the system processes the validation result, the desired outcome is that the invalid segment is skipped and not used for status array population.
💻 Technical Criteria
Given S09 segment has failed validation and error flag has been set
When The system processes the validation result
Then The invalid segment is skipped and not used for status array population
R-GCX016E-cbl-02967 Initialize Database Segment Counter
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Database Segment Counter' is invoked, and assuming that status array conversion process is starting, when the conversion initialization is triggered, the desired outcome is that database segment counter is set to zero and work areas are cleared.
💻 Technical Criteria
Given Status array conversion process is starting
When The conversion initialization is triggered
Then Database segment counter is set to zero and work areas are cleared
R-GCX016E-cbl-02968 Clear Database Segment Work Area
Process Rules
📊 Business Logic Narrative
When the process 'Clear Database Segment Work Area' is invoked, and assuming that database conversion process is active, when a new database segment needs to be prepared, the desired outcome is that the database segment work area is cleared of all previous data.
💻 Technical Criteria
Given Database conversion process is active
When A new database segment needs to be prepared
Then The database segment work area is cleared of all previous data
R-GCX016E-cbl-02969 More Status Array Entries?
Decision Rules
📊 Business Logic Narrative
When the process 'More Status Array Entries?' is invoked, and assuming that status array conversion is in progress, when system checks for remaining entries to process, the desired outcome is that continue processing if entries exist, otherwise complete conversion.
💻 Technical Criteria
Given Status array conversion is in progress
When System checks for remaining entries to process
Then Continue processing if entries exist, otherwise complete conversion
R-GCX016E-cbl-02970 Get Next Status Array Entry
Process Rules
📊 Business Logic Narrative
When the process 'Get Next Status Array Entry' is invoked, and assuming that status array has remaining entries to process, when next entry retrieval is requested, the desired outcome is that the next status array entry is loaded for processing.
💻 Technical Criteria
Given Status array has remaining entries to process
When Next entry retrieval is requested
Then The next status array entry is loaded for processing
R-GCX016E-cbl-02971 Validate Disposition Code Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Disposition Code Format' is invoked, and assuming that a status array entry with disposition code is being processed, when disposition code format validation is performed, the desired outcome is that disposition code is checked against valid format criteria.
💻 Technical Criteria
Given A status array entry with disposition code is being processed
When Disposition code format validation is performed
Then Disposition code is checked against valid format criteria
R-GCX016E-cbl-02972 Disposition Code Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Disposition Code Valid?' is invoked, and assuming that disposition code format validation has been performed, when validity determination is made, the desired outcome is that valid codes proceed to formatting, invalid codes are skipped.
💻 Technical Criteria
Given Disposition code format validation has been performed
When Validity determination is made
Then Valid codes proceed to formatting, invalid codes are skipped
R-GCX016E-cbl-02973 Format Disposition Code for Database
Computation Rules
📊 Business Logic Narrative
When the process 'Format Disposition Code for Database' is invoked, and assuming that a valid disposition code exists in the status array entry, when database formatting is applied, the desired outcome is that disposition code is converted to proper database storage format.
💻 Technical Criteria
Given A valid disposition code exists in the status array entry
When Database formatting is applied
Then Disposition code is converted to proper database storage format
R-GCX016E-cbl-02974 Format Date/Time Information
Computation Rules
📊 Business Logic Narrative
When the process 'Format Date/Time Information' is invoked, and assuming that status array entry contains date and time information, when date/time formatting is applied, the desired outcome is that date and time data is converted to database storage format.
💻 Technical Criteria
Given Status array entry contains date and time information
When Date/time formatting is applied
Then Date and time data is converted to database storage format
R-GCX016E-cbl-02975 Format Status Information Code
Computation Rules
📊 Business Logic Narrative
When the process 'Format Status Information Code' is invoked, and assuming that status array entry contains status information codes, when status code formatting is applied, the desired outcome is that status information is converted to database-compatible format.
💻 Technical Criteria
Given Status array entry contains status information codes
When Status code formatting is applied
Then Status information is converted to database-compatible format
R-GCX016E-cbl-02976 Format Quantity Information
Computation Rules
📊 Business Logic Narrative
When the process 'Format Quantity Information' is invoked, and assuming that status array entry contains quantity information, when quantity formatting is applied, the desired outcome is that quantity data is converted to proper database storage format.
💻 Technical Criteria
Given Status array entry contains quantity information
When Quantity formatting is applied
Then Quantity data is converted to proper database storage format
R-GCX016E-cbl-02977 Move Formatted Data to Database Segment
Process Rules
📊 Business Logic Narrative
When the process 'Move Formatted Data to Database Segment' is invoked, and assuming that all data elements have been formatted for database storage, when data transfer to database segment is executed, the desired outcome is that formatted data is moved to the database segment work area.
💻 Technical Criteria
Given All data elements have been formatted for database storage
When Data transfer to database segment is executed
Then Formatted data is moved to the database segment work area
R-GCX016E-cbl-02978 Increment Database Segment Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment Database Segment Counter' is invoked, and assuming that data has been successfully moved to database segment, when counter increment is performed, the desired outcome is that database segment counter is increased by one.
💻 Technical Criteria
Given Data has been successfully moved to database segment
When Counter increment is performed
Then Database segment counter is increased by one
R-GCX016E-cbl-02979 Segment Full or Array Complete?
Decision Rules
📊 Business Logic Narrative
When the process 'Segment Full or Array Complete?' is invoked, and assuming that database segment has received new data entry, when segment status evaluation is performed, the desired outcome is that continue adding entries if segment has space and array has entries, otherwise complete segment.
💻 Technical Criteria
Given Database segment has received new data entry
When Segment status evaluation is performed
Then Continue adding entries if segment has space and array has entries, otherwise complete segment
R-GCX016E-cbl-02980 Prepare Database Segment for Storage
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Database Segment for Storage' is invoked, and assuming that database segment is full or all array entries are processed, when segment preparation is initiated, the desired outcome is that database segment is prepared for storage with proper formatting.
💻 Technical Criteria
Given Database segment is full or all array entries are processed
When Segment preparation is initiated
Then Database segment is prepared for storage with proper formatting
R-GCX016E-cbl-02985 Mark Segment Ready for Database Write
Process Rules
📊 Business Logic Narrative
When the process 'Mark Segment Ready for Database Write' is invoked, and assuming that database segment has been fully prepared with all required data, when ready status marking is applied, the desired outcome is that segment is flagged as ready for database write operation.
💻 Technical Criteria
Given Database segment has been fully prepared with all required data
When Ready status marking is applied
Then Segment is flagged as ready for database write operation
R-GCX016E-cbl-02986 Continue to Next Segment
Process Rules
📊 Business Logic Narrative
When the process 'Continue to Next Segment' is invoked, and assuming that current database segment processing is complete, when continuation to next segment is initiated, the desired outcome is that system proceeds to process next segment or remaining status array entries.
💻 Technical Criteria
Given Current database segment processing is complete
When Continuation to next segment is initiated
Then System proceeds to process next segment or remaining status array entries
R-GCX016E-cbl-02987 Log Conversion Completion
Process Rules
📊 Business Logic Narrative
When the process 'Log Conversion Completion' is invoked, and assuming that all status array entries have been processed and converted, when conversion completion logging is performed, the desired outcome is that successful conversion completion is recorded in system logs.
💻 Technical Criteria
Given All status array entries have been processed and converted
When Conversion completion logging is performed
Then Successful conversion completion is recorded in system logs
R-GCX016E-cbl-00590 Search DC Table for Disposition Code
Validation Rules
📊 Business Logic Narrative
When the process 'Search DC Table for Disposition Code' is invoked, and assuming that a disposition code is received from an x4 segment, when the system searches the dc table for the disposition code, the desired outcome is that the system retrieves disposition code information if found or flags as invalid if not found.
💻 Technical Criteria
Given A disposition code is received from an X4 segment
When The system searches the DC table for the disposition code
Then The system retrieves disposition code information if found or flags as invalid if not found
R-GCX016E-cbl-00591 Set Valid Disposition Code Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Valid Disposition Code Flag' is invoked, and assuming that a disposition code has been found in the dc table, when the disposition code information is successfully retrieved, the desired outcome is that the system sets the valid disposition code flag to allow continued processing.
💻 Technical Criteria
Given A disposition code has been found in the DC table
When The disposition code information is successfully retrieved
Then The system sets the valid disposition code flag to allow continued processing
R-GCX016E-cbl-00592 Generate Merlin Error Message
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Merlin Error Message', assuming that a disposition code is not found in the dc table, when the table lookup returns no matching record, the desired outcome is that the system generates a merlin error message and sets invalid disposition code flag.
💻 Technical Criteria
EXCLUDING A disposition code is not found in the DC table
When The table lookup returns no matching record
Then The system generates a Merlin error message and sets invalid disposition code flag
R-GCX016E-cbl-00593 Validate Code Processing Rules
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Code Processing Rules' is invoked, and assuming that a valid disposition code is found in the dc table, when the system validates the code processing rules, the desired outcome is that the system confirms the code can be processed according to established business rules.
💻 Technical Criteria
Given A valid disposition code is found in the DC table
When The system validates the code processing rules
Then The system confirms the code can be processed according to established business rules
R-GCX016E-cbl-00594 Log Unknown Disposition Code
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Unknown Disposition Code', assuming that an invalid disposition code flag has been set, when the system processes the invalid code, the desired outcome is that the system logs the unknown disposition code for audit and monitoring purposes.
💻 Technical Criteria
EXCLUDING An invalid disposition code flag has been set
When The system processes the invalid code
Then The system logs the unknown disposition code for audit and monitoring purposes
R-GCX016E-cbl-02988 Search DC Table for Disposition Code
Validation Rules
📊 Business Logic Narrative
When the process 'Search DC Table for Disposition Code' is invoked, and assuming that a disposition code is received from x4 segment processing, when the system performs table lookup using gcctbio to search the dc table for the disposition code, the desired outcome is that the system determines if the disposition code exists in the table and sets appropriate validation flags.
💻 Technical Criteria
Given A disposition code is received from X4 segment processing
When The system performs table lookup using GCCTBIO to search the DC table for the disposition code
Then The system determines if the disposition code exists in the table and sets appropriate validation flags
R-GCX016E-cbl-02989 Extract Processing Rules from Table
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Processing Rules from Table' is invoked, and assuming that a disposition code has been found valid in the dc table, when the system extracts processing rules from the table entry, the desired outcome is that the system retrieves action type (add/subtract), hold/release indicator, status information flag, and removal processing flag for the disposition code.
💻 Technical Criteria
Given A disposition code has been found valid in the DC table
When The system extracts processing rules from the table entry
Then The system retrieves action type (add/subtract), hold/release indicator, status information flag, and removal processing flag for the disposition code
R-GCX016E-cbl-02990 Set Disposition Code Valid Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Disposition Code Valid Flag' is invoked, and assuming that a disposition code has been successfully found in the dc table, when the system completes table lookup validation, the desired outcome is that the system sets the disposition code valid flag to true to enable further processing.
💻 Technical Criteria
Given A disposition code has been successfully found in the DC table
When The system completes table lookup validation
Then The system sets the disposition code valid flag to true to enable further processing
R-GCX016E-cbl-02991 Extract Action Type - Add/Subtract
Computation Rules
📊 Business Logic Narrative
When the process 'Extract Action Type - Add/Subtract' is invoked, and assuming that a valid disposition code entry exists in the dc table, when the system extracts action type information from the table entry, the desired outcome is that the system identifies whether the disposition code should add to or subtract from release quantities.
💻 Technical Criteria
Given A valid disposition code entry exists in the DC table
When The system extracts action type information from the table entry
Then The system identifies whether the disposition code should add to or subtract from release quantities
R-GCX016E-cbl-02992 Extract Hold/Release Indicator
Decision Rules
📊 Business Logic Narrative
When the process 'Extract Hold/Release Indicator' is invoked, and assuming that a valid disposition code entry exists in the dc table, when the system extracts hold/release indicator from the table entry, the desired outcome is that the system identifies whether the disposition code represents a hold or release action.
💻 Technical Criteria
Given A valid disposition code entry exists in the DC table
When The system extracts hold/release indicator from the table entry
Then The system identifies whether the disposition code represents a hold or release action
R-GCX016E-cbl-02993 Extract Status Information Flag
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Status Information Flag' is invoked, and assuming that a valid disposition code entry exists in the dc table, when the system extracts status information flag from the table entry, the desired outcome is that the system identifies whether the disposition code is informational only or requires active processing.
💻 Technical Criteria
Given A valid disposition code entry exists in the DC table
When The system extracts status information flag from the table entry
Then The system identifies whether the disposition code is informational only or requires active processing
R-GCX016E-cbl-02994 Extract Removal Processing Flag
Process Rules
📊 Business Logic Narrative
When the process 'Extract Removal Processing Flag' is invoked, and assuming that a valid disposition code entry exists in the dc table, when the system extracts removal processing flag from the table entry, the desired outcome is that the system identifies whether existing disposition codes should be removed before processing the current code.
💻 Technical Criteria
Given A valid disposition code entry exists in the DC table
When The system extracts removal processing flag from the table entry
Then The system identifies whether existing disposition codes should be removed before processing the current code
R-GCX016E-cbl-02995 Set Processing Rules in Working Storage
Process Rules
📊 Business Logic Narrative
When the process 'Set Processing Rules in Working Storage' is invoked, and assuming that all processing rules have been extracted from the dc table entry, when the system completes rule extraction process, the desired outcome is that the system stores action type, hold/release indicator, status flag, and removal flag in working storage variables.
💻 Technical Criteria
Given All processing rules have been extracted from the DC table entry
When The system completes rule extraction process
Then The system stores action type, hold/release indicator, status flag, and removal flag in working storage variables
R-GCX016E-cbl-02997 Set Disposition Code Invalid Flag
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Disposition Code Invalid Flag', assuming that a disposition code is not found in the dc table, when the system completes table lookup validation with negative result, the desired outcome is that the system sets the disposition code invalid flag to prevent downstream processing of the invalid code.
💻 Technical Criteria
EXCLUDING A disposition code is not found in the DC table
When The system completes table lookup validation with negative result
Then The system sets the disposition code invalid flag to prevent downstream processing of the invalid code
R-GCX016E-cbl-02998 Log Unknown Disposition Code
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Unknown Disposition Code', assuming that a disposition code has been determined invalid and error message generated, when the system processes the invalid disposition code, the desired outcome is that the system logs the unknown disposition code details for audit and debugging purposes.
💻 Technical Criteria
EXCLUDING A disposition code has been determined invalid and error message generated
When The system processes the invalid disposition code
Then The system logs the unknown disposition code details for audit and debugging purposes
R-GCX016E-cbl-03241 Lookup Disposition Code in DC Table
Action Rules
📊 Business Logic Narrative
When the process 'Lookup Disposition Code in DC Table' is invoked, and assuming that a disposition code has been received for processing, when the system looks up the disposition code in the dc table, the desired outcome is that the system retrieves the corresponding processing rules including action type, quantity impact, and removal requirements.
💻 Technical Criteria
Given A disposition code has been received for processing
When The system looks up the disposition code in the DC table
Then The system retrieves the corresponding processing rules including action type, quantity impact, and removal requirements
R-GCX016E-cbl-03242 Code Found in Table?
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Code Found in Table?', assuming that a disposition code lookup has been performed in the dc table, when the disposition code is not found in the table, the desired outcome is that the system generates an error message for the unknown disposition code.
💻 Technical Criteria
EXCLUDING A disposition code lookup has been performed in the DC table
When The disposition code is not found in the table
Then The system generates an error message for the unknown disposition code
R-GCX016E-cbl-03243 Set Hold Indicator
Decision Rules
📊 Business Logic Narrative
When the process 'Set Hold Indicator' is invoked, and assuming that a disposition code has been successfully looked up in the dc table, when the action type from the dc table indicates a hold operation, the desired outcome is that the system sets the hold indicator flag for subsequent processing.
💻 Technical Criteria
Given A disposition code has been successfully looked up in the DC table
When The action type from the DC table indicates a hold operation
Then The system sets the hold indicator flag for subsequent processing
R-GCX016E-cbl-03244 Set Release Indicator
Decision Rules
📊 Business Logic Narrative
When the process 'Set Release Indicator' is invoked, and assuming that a disposition code has been successfully looked up in the dc table, when the action type from the dc table indicates a release operation, the desired outcome is that the system sets the release indicator flag for subsequent processing.
💻 Technical Criteria
Given A disposition code has been successfully looked up in the DC table
When The action type from the DC table indicates a release operation
Then The system sets the release indicator flag for subsequent processing
R-GCX016E-cbl-03245 Set Status Info Indicator
Decision Rules
📊 Business Logic Narrative
When the process 'Set Status Info Indicator' is invoked, and assuming that a disposition code has been successfully looked up in the dc table, when the action type from the dc table indicates a status information operation, the desired outcome is that the system sets the status info indicator flag for subsequent processing.
💻 Technical Criteria
Given A disposition code has been successfully looked up in the DC table
When The action type from the DC table indicates a status information operation
Then The system sets the status info indicator flag for subsequent processing
R-GCX016E-cbl-03246 Set Removal Indicator
Decision Rules
📊 Business Logic Narrative
When the process 'Set Removal Indicator' is invoked, and assuming that a disposition code has been successfully looked up in the dc table, when the action type from the dc table indicates a removal operation, the desired outcome is that the system sets the removal indicator flag for subsequent processing.
💻 Technical Criteria
Given A disposition code has been successfully looked up in the DC table
When The action type from the DC table indicates a removal operation
Then The system sets the removal indicator flag for subsequent processing
R-GCX016E-cbl-03247 Set Quantity Add Flag
Computation Rules
📊 Business Logic Narrative
When the process 'Set Quantity Add Flag' is invoked, and assuming that disposition code processing rules have been extracted from the dc table, when the quantity impact flag indicates the disposition code adds to release quantity, the desired outcome is that the system sets the quantity add flag to increase release quantities during processing.
💻 Technical Criteria
Given Disposition code processing rules have been extracted from the DC table
When The quantity impact flag indicates the disposition code adds to release quantity
Then The system sets the quantity add flag to increase release quantities during processing
R-GCX016E-cbl-03248 Set Quantity Subtract Flag
Computation Rules
📊 Business Logic Narrative
When the process 'Set Quantity Subtract Flag' is invoked, and assuming that disposition code processing rules have been extracted from the dc table, when the quantity impact flag indicates the disposition code subtracts from release quantity, the desired outcome is that the system sets the quantity subtract flag to decrease release quantities during processing.
💻 Technical Criteria
Given Disposition code processing rules have been extracted from the DC table
When The quantity impact flag indicates the disposition code subtracts from release quantity
Then The system sets the quantity subtract flag to decrease release quantities during processing
R-GCX016E-cbl-03249 Set No Quantity Impact
Computation Rules
📊 Business Logic Narrative
When the process 'Set No Quantity Impact' is invoked, and assuming that disposition code processing rules have been extracted from the dc table, when the quantity impact flag indicates the disposition code has no effect on release quantity, the desired outcome is that the system sets the no quantity impact flag to maintain current release quantities during processing.
💻 Technical Criteria
Given Disposition code processing rules have been extracted from the DC table
When The quantity impact flag indicates the disposition code has no effect on release quantity
Then The system sets the no quantity impact flag to maintain current release quantities during processing
R-GCX016E-cbl-03250 Set Counterpart Removal Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Counterpart Removal Flag' is invoked, and assuming that disposition code removal processing requirements have been extracted from the dc table, when the removal requirements indicate counterpart disposition codes must be removed, the desired outcome is that the system sets the counterpart removal flag to remove conflicting disposition codes before applying the new code.
💻 Technical Criteria
Given Disposition code removal processing requirements have been extracted from the DC table
When The removal requirements indicate counterpart disposition codes must be removed
Then The system sets the counterpart removal flag to remove conflicting disposition codes before applying the new code
R-GCX016E-cbl-03251 Set Standard Processing Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Standard Processing Flag' is invoked, and assuming that disposition code removal processing requirements have been extracted from the dc table, when the removal requirements indicate no counterpart removal is needed, the desired outcome is that the system sets the standard processing flag to apply the disposition code using normal processing rules.
💻 Technical Criteria
Given Disposition code removal processing requirements have been extracted from the DC table
When The removal requirements indicate no counterpart removal is needed
Then The system sets the standard processing flag to apply the disposition code using normal processing rules
R-GCX016E-cbl-03393 Call GCCTBIO Table Lookup
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCTBIO Table Lookup' is invoked, and assuming that a disposition code from x4 segment needs to be validated, when the system calls gcctbio table lookup service with the disposition code, the desired outcome is that the system searches the dc table and initiates the lookup process.
💻 Technical Criteria
Given A disposition code from X4 segment needs to be validated
When The system calls GCCTBIO table lookup service with the disposition code
Then The system searches the DC table and initiates the lookup process
R-GCX016E-cbl-03394 Code Found in DC Table?
Validation Rules
📊 Business Logic Narrative
When the process 'Code Found in DC Table?' is invoked, and assuming that a disposition code has been searched in the dc table, when the table lookup is completed, the desired outcome is that the system determines if the code exists and branches to either retrieve processing rules or handle invalid code scenario.
💻 Technical Criteria
Given A disposition code has been searched in the DC table
When The table lookup is completed
Then The system determines if the code exists and branches to either retrieve processing rules or handle invalid code scenario
R-GCX016E-cbl-03395 Retrieve Processing Rules
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Processing Rules' is invoked, and assuming that a disposition code exists in the dc table, when the code is successfully found during table lookup, the desired outcome is that the system retrieves the processing rules, extracts code description, sets valid code flag, and returns processing rules to caller.
💻 Technical Criteria
Given A disposition code exists in the DC table
When The code is successfully found during table lookup
Then The system retrieves the processing rules, extracts code description, sets valid code flag, and returns processing rules to caller
R-GCX016E-cbl-03396 Set Invalid Code Flag
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Invalid Code Flag', assuming that a disposition code does not exist in the dc table, when the table lookup fails to find the code, the desired outcome is that the system sets invalid code flag, generates merlin error message, logs unknown code error, and continues processing with error status.
💻 Technical Criteria
EXCLUDING A disposition code does not exist in the DC table
When The table lookup fails to find the code
Then The system sets invalid code flag, generates Merlin error message, logs unknown code error, and continues processing with error status
R-GCX016E-cbl-03506 Lookup Disposition Code in DC Table
Validation Rules
📊 Business Logic Narrative
When the process 'Lookup Disposition Code in DC Table' is invoked, and assuming that a disposition code is received for processing, when the system looks up the disposition code in the dc table, the desired outcome is that the system determines if the code exists in the table and proceeds with appropriate processing path.
💻 Technical Criteria
Given A disposition code is received for processing
When The system looks up the disposition code in the DC table
Then The system determines if the code exists in the table and proceeds with appropriate processing path
R-GCX016E-cbl-03507 Continue Normal Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue Normal Processing' is invoked, and assuming that a disposition code has been received and validated against the dc table, when the disposition code is found in the dc table, the desired outcome is that the system continues with normal disposition code processing workflow.
💻 Technical Criteria
Given A disposition code has been received and validated against the DC table
When The disposition code is found in the DC table
Then The system continues with normal disposition code processing workflow
R-GCX016E-cbl-03508 Generate Merlin Error Message
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Merlin Error Message', assuming that a disposition code has been received for processing, when the disposition code is not found in the dc table, the desired outcome is that the system initiates generation of a merlin error message for the unknown code.
💻 Technical Criteria
EXCLUDING A disposition code has been received for processing
When The disposition code is not found in the DC table
Then The system initiates generation of a Merlin error message for the unknown code
R-GCX016E-cbl-03510 Include Processing Context Information
Process Rules
📊 Business Logic Narrative
When the process 'Include Processing Context Information' is invoked, and assuming that an error message is being formatted for an unknown disposition code, when the system adds processing context information, the desired outcome is that the error message includes relevant context such as processing stage, transaction details, and timing information.
💻 Technical Criteria
Given An error message is being formatted for an unknown disposition code
When The system adds processing context information
Then The error message includes relevant context such as processing stage, transaction details, and timing information
R-GCX016E-cbl-03512 Set Error Message Type
Process Rules
📊 Business Logic Narrative
When the process 'Set Error Message Type' is invoked, and assuming that an error message has been formatted with all required details, when the system sets the message type, the desired outcome is that the error message is classified with the appropriate error type indicator for disposition code validation failures.
💻 Technical Criteria
Given An error message has been formatted with all required details
When The system sets the message type
Then The error message is classified with the appropriate error type indicator for disposition code validation failures
R-GCX016E-cbl-03515 Continue Processing Next Code
Process Rules
📊 Business Logic Narrative
When the process 'Continue Processing Next Code' is invoked, and assuming that an unknown disposition code error has been processed and logged, when the system completes error handling, the desired outcome is that the system continues processing the next disposition code in the sequence without stopping the overall transaction.
💻 Technical Criteria
Given An unknown disposition code error has been processed and logged
When The system completes error handling
Then The system continues processing the next disposition code in the sequence without stopping the overall transaction
R-GCX016E-cbl-00601 Duplicate Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Duplicate Found?' is invoked, and assuming that completed search through status array with duplicate detection flags, when the system evaluates whether any duplicate conditions were identified during the search, the desired outcome is that if any duplicate was found (exact or temporal), set duplicate detection flag and prepare duplicate handling, otherwise return no duplicate status.
💻 Technical Criteria
Given Completed search through status array with duplicate detection flags
When The system evaluates whether any duplicate conditions were identified during the search
Then If any duplicate was found (exact or temporal), set duplicate detection flag and prepare duplicate handling, otherwise return no duplicate status
R-GCX016E-cbl-00602 More Array Entries?
Process Rules
📊 Business Logic Narrative
When the process 'More Array Entries?' is invoked, and assuming that a status array with multiple entries and current search position, when the system checks if there are remaining entries to process in the array, the desired outcome is that if more entries exist, get next status entry for comparison, otherwise proceed to duplicate evaluation.
💻 Technical Criteria
Given A status array with multiple entries and current search position
When The system checks if there are remaining entries to process in the array
Then If more entries exist, get next status entry for comparison, otherwise proceed to duplicate evaluation
R-GCX016E-cbl-00612 Validate Disposition Code in DC Table
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Disposition Code in DC Table' is invoked, and assuming that a manual release request is received with a disposition code, when the system looks up the disposition code in the dc table, the desired outcome is that the system confirms the code exists and is valid for manual release processing.
💻 Technical Criteria
Given A manual release request is received with a disposition code
When The system looks up the disposition code in the DC table
Then The system confirms the code exists and is valid for manual release processing
R-GCX016E-cbl-00613 Valid Manual Release Code?
Authorization Rules
📊 Business Logic Narrative
When the process 'Valid Manual Release Code?' is invoked, and assuming that a disposition code has been validated in the dc table, when the system checks if the code type allows manual release operations, the desired outcome is that processing continues if authorized, otherwise an error is generated.
💻 Technical Criteria
Given A disposition code has been validated in the DC table
When The system checks if the code type allows manual release operations
Then Processing continues if authorized, otherwise an error is generated
R-GCX016E-cbl-00614 Duplicate Code Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Duplicate Code Found?' is invoked, and assuming that a valid manual release code is being processed, when the system searches existing status arrays for the same disposition code, the desired outcome is that processing is skipped if duplicate found, otherwise continues with adding the code.
💻 Technical Criteria
Given A valid manual release code is being processed
When The system searches existing status arrays for the same disposition code
Then Processing is skipped if duplicate found, otherwise continues with adding the code
R-GCX016E-cbl-00618 Log Manual Release Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Manual Release Action' is invoked, and assuming that release quantities have been updated for manual release, when the system completes the manual release processing, the desired outcome is that an audit record is created documenting the manual release action with timestamp and user information.
💻 Technical Criteria
Given Release quantities have been updated for manual release
When The system completes the manual release processing
Then An audit record is created documenting the manual release action with timestamp and user information
R-GCX016E-cbl-00623 Generate Error Message
Validation Rules
📊 Business Logic Narrative
When the process 'Generate Error Message' is invoked, and assuming that a manual release request contains an invalid disposition code, when the disposition code validation fails, the desired outcome is that an error message is generated indicating the invalid code and processing is terminated.
💻 Technical Criteria
Given A manual release request contains an invalid disposition code
When The disposition code validation fails
Then An error message is generated indicating the invalid code and processing is terminated
R-GCX016E-cbl-00626 Validate Removal Request Parameters
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Removal Request Parameters' is invoked, and assuming that a disposition code removal request is received, when the system validates the removal request parameters, the desired outcome is that the request must contain valid disposition code, entry number, and quantity information to proceed with removal processing.
💻 Technical Criteria
Given A disposition code removal request is received
When The system validates the removal request parameters
Then The request must contain valid disposition code, entry number, and quantity information to proceed with removal processing
R-GCX016E-cbl-00630 Remove Code from Status Array
Action Rules
📊 Business Logic Narrative
When the process 'Remove Code from Status Array' is invoked, and assuming that an authorized disposition code removal request with located array position, when the system executes the removal operation, the desired outcome is that the disposition code must be completely removed from the status array while preserving array integrity.
💻 Technical Criteria
Given An authorized disposition code removal request with located array position
When The system executes the removal operation
Then The disposition code must be completely removed from the status array while preserving array integrity
R-GCX016E-cbl-00631 Reorganize Status Array Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Reorganize Status Array Sequence' is invoked, and assuming that a status array with a removed disposition code creating a gap in sequence, when the system reorganizes the array structure, the desired outcome is that all remaining disposition codes must be resequenced to eliminate gaps and maintain proper chronological order.
💻 Technical Criteria
Given A status array with a removed disposition code creating a gap in sequence
When The system reorganizes the array structure
Then All remaining disposition codes must be resequenced to eliminate gaps and maintain proper chronological order
R-GCX016E-cbl-00632 Update Array Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Update Array Counter' is invoked, and assuming that a reorganized status array with one less disposition code, when the system updates array management counters, the desired outcome is that the status array counter must be decremented by one to accurately reflect the current number of active disposition codes.
💻 Technical Criteria
Given A reorganized status array with one less disposition code
When The system updates array management counters
Then The status array counter must be decremented by one to accurately reflect the current number of active disposition codes
R-GCX016E-cbl-00638 Generate Error Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Error Message' is invoked, and assuming that a disposition code removal request that cannot be processed due to validation failure or authorization denial, when the system generates an error message, the desired outcome is that an error message must be created explaining why the removal failed and what corrective action is needed.
💻 Technical Criteria
Given A disposition code removal request that cannot be processed due to validation failure or authorization denial
When The system generates an error message
Then An error message must be created explaining why the removal failed and what corrective action is needed
R-GCX016E-cbl-00644 Insert New Status Information Code
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Insert New Status Information Code', assuming that a status information disposition code is not found in the existing status array and there is available space in the status array, when the system processes the status information disposition code, the desired outcome is that the system inserts the new status information code into the next available position in the status array.
💻 Technical Criteria
EXCLUDING A status information disposition code is not found in the existing status array AND there is available space in the status array
When The system processes the status information disposition code
Then The system inserts the new status information code into the next available position in the status array
R-GCX016E-cbl-00645 Update Status Array Sequence Counter
Process Rules
📊 Business Logic Narrative
When the process 'Update Status Array Sequence Counter' is invoked, and assuming that a new status information disposition code has been successfully inserted into the status array, when the insertion is completed, the desired outcome is that the system increments the status array sequence counter to reflect the new entry count.
💻 Technical Criteria
Given A new status information disposition code has been successfully inserted into the status array
When The insertion is completed
Then The system increments the status array sequence counter to reflect the new entry count
R-GCX016E-cbl-00652 Remove Counterpart Codes
Process Rules
📊 Business Logic Narrative
When the process 'Remove Counterpart Codes' is invoked, and assuming that a new hold or release code is being added to the status array, when the system identifies counterpart codes that conflict with the new code, the desired outcome is that all conflicting counterpart codes are removed from the status array before adding the new code.
💻 Technical Criteria
Given A new hold or release code is being added to the status array
When The system identifies counterpart codes that conflict with the new code
Then All conflicting counterpart codes are removed from the status array before adding the new code
R-GCX016E-cbl-00656 Remove Conflicting Hold Codes
Process Rules
📊 Business Logic Narrative
When the process 'Remove Conflicting Hold Codes' is invoked, and assuming that a release disposition code is being processed, when the system identifies conflicting hold codes in the status array, the desired outcome is that all hold codes that conflict with the release are removed from the status array before processing the release.
💻 Technical Criteria
Given A release disposition code is being processed
When The system identifies conflicting hold codes in the status array
Then All hold codes that conflict with the release are removed from the status array before processing the release
R-GCX016E-cbl-00659 Manual Release?
Decision Rules
📊 Business Logic Narrative
When the process 'Manual Release?' is invoked, and assuming that a release disposition code is being evaluated, when the system checks if the code represents a manual release, the desired outcome is that the code is identified as manual release if it originates from transaction gct1071e or has manual release indicators.
💻 Technical Criteria
Given A release disposition code is being evaluated
When The system checks if the code represents a manual release
Then The code is identified as manual release if it originates from transaction GCT1071E or has manual release indicators
R-GCX016E-cbl-00660 Process Manual Release Request
Process Rules
📊 Business Logic Narrative
When the process 'Process Manual Release Request' is invoked, and assuming that a manual release disposition code is identified, when the system processes the manual release request, the desired outcome is that the manual release is processed with special validation, broker verification, and immediate release status setting.
💻 Technical Criteria
Given A manual release disposition code is identified
When The system processes the manual release request
Then The manual release is processed with special validation, broker verification, and immediate release status setting
R-GCX016E-cbl-00661 Log Manual Release Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Manual Release Action' is invoked, and assuming that a manual release request has been processed, when the system logs the manual release action, the desired outcome is that the manual release action is logged with user information, timestamp, release details, and audit trail information.
💻 Technical Criteria
Given A manual release request has been processed
When The system logs the manual release action
Then The manual release action is logged with user information, timestamp, release details, and audit trail information
R-GCX016E-cbl-00662 Auto Release?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Auto Release?', assuming that a release disposition code is being evaluated and is not a manual release, when the system checks if the code represents an automatic release, the desired outcome is that the code is identified as automatic release if it has arl (auto release) indicators or meets automatic release criteria.
💻 Technical Criteria
EXCLUDING A release disposition code is being evaluated and is not a manual release
When The system checks if the code represents an automatic release
Then The code is identified as automatic release if it has ARL (Auto Release) indicators or meets automatic release criteria
R-GCX016E-cbl-00663 Process Automatic Release
Process Rules
📊 Business Logic Narrative
When the process 'Process Automatic Release' is invoked, and assuming that an automatic release disposition code is identified, when the system processes the automatic release, the desired outcome is that the automatic release is processed with system validation, automatic broker assignment, and immediate release status setting.
💻 Technical Criteria
Given An automatic release disposition code is identified
When The system processes the automatic release
Then The automatic release is processed with system validation, automatic broker assignment, and immediate release status setting
R-GCX016E-cbl-00694 Log Arrival Action
Action Rules
📊 Business Logic Narrative
When the process 'Log Arrival Action' is invoked, and assuming that aei notification message has been sent, when the system processes audit and logging requirements, the desired outcome is that the arrival action is logged for audit trail and historical tracking.
💻 Technical Criteria
Given AEI notification message has been sent
When The system processes audit and logging requirements
Then The arrival action is logged for audit trail and historical tracking
R-GCX016E-cbl-00729 Send Merlin Notification Message
Action Rules
📊 Business Logic Narrative
When the process 'Send Merlin Notification Message' is invoked, and assuming that audit trail has been updated with cancellation transaction, when merlin message transmission is initiated, the desired outcome is that system sends arrival cancellation notification message through merlin system to appropriate recipients.
💻 Technical Criteria
Given Audit trail has been updated with cancellation transaction
When Merlin message transmission is initiated
Then System sends arrival cancellation notification message through Merlin system to appropriate recipients
R-GCX016E-cbl-00744 Lookup Disposition Code in DC Table
Action Rules
📊 Business Logic Narrative
When the process 'Lookup Disposition Code in DC Table' is invoked, and assuming that a disposition code has been extracted from the status array, when the system needs to determine the disposition code's action type, the desired outcome is that the disposition code is looked up in the dc table to retrieve its configuration.
💻 Technical Criteria
Given A disposition code has been extracted from the status array
When The system needs to determine the disposition code's action type
Then The disposition code is looked up in the DC table to retrieve its configuration
R-GCX016E-cbl-00745 Disposition Code Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Disposition Code Found?' is invoked, and assuming that a disposition code lookup has been performed in the dc table, when the system checks if the disposition code was found, the desired outcome is that if the disposition code is not found, an error message is generated for unknown disposition code.
💻 Technical Criteria
Given A disposition code lookup has been performed in the DC table
When The system checks if the disposition code was found
Then If the disposition code is not found, an error message is generated for unknown disposition code
R-GCX016E-cbl-00746 Get Disposition Code Action Type
Action Rules
📊 Business Logic Narrative
When the process 'Get Disposition Code Action Type' is invoked, and assuming that a valid disposition code exists in the dc table, when the system processes the disposition code, the desired outcome is that the action type is retrieved from the dc table configuration.
💻 Technical Criteria
Given A valid disposition code exists in the DC table
When The system processes the disposition code
Then The action type is retrieved from the DC table configuration
R-GCX016E-cbl-00747 Action Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Action Type?' is invoked, and assuming that a disposition code action type has been determined, when the system processes the quantity impact, the desired outcome is that if action type is 'add', quantity is added to release quantity; if action type is 'subtract', quantity is subtracted from release quantity; if action type is 'status info only', no quantity change is made.
💻 Technical Criteria
Given A disposition code action type has been determined
When The system processes the quantity impact
Then If action type is 'Add', quantity is added to release quantity; if action type is 'Subtract', quantity is subtracted from release quantity; if action type is 'Status Info Only', no quantity change is made
R-GCX016E-cbl-00748 Add to Release Quantity
Computation Rules
📊 Business Logic Narrative
When the process 'Add to Release Quantity' is invoked, and assuming that a disposition code has action type 'add', when the quantity impact is processed, the desired outcome is that the disposition code quantity is added to the current release quantity.
💻 Technical Criteria
Given A disposition code has action type 'Add'
When The quantity impact is processed
Then The disposition code quantity is added to the current release quantity
R-GCX016E-cbl-00749 Subtract from Release Quantity
Computation Rules
📊 Business Logic Narrative
When the process 'Subtract from Release Quantity' is invoked, and assuming that a disposition code has action type 'subtract', when the quantity impact is processed, the desired outcome is that the disposition code quantity is subtracted from the current release quantity.
💻 Technical Criteria
Given A disposition code has action type 'Subtract'
When The quantity impact is processed
Then The disposition code quantity is subtracted from the current release quantity
R-GCX016E-cbl-00750 No Quantity Change
Decision Rules
📊 Business Logic Narrative
When the process 'No Quantity Change' is invoked, and assuming that a disposition code has action type 'status info only', when the quantity impact is processed, the desired outcome is that no change is made to the current release quantity.
💻 Technical Criteria
Given A disposition code has action type 'Status Info Only'
When The quantity impact is processed
Then No change is made to the current release quantity
R-GCX016E-cbl-00755 Set Release Quantity = 0
Validation Rules
📊 Business Logic Narrative
When the process 'Set Release Quantity = 0' is invoked, and assuming that the calculated release quantity is less than zero, when the system applies minimum quantity validation, the desired outcome is that the release quantity is set to zero.
💻 Technical Criteria
Given The calculated release quantity is less than zero
When The system applies minimum quantity validation
Then The release quantity is set to zero
R-GCX016E-cbl-00760 Generate Merlin Notification with Quantity Impact
Action Rules
📊 Business Logic Narrative
When the process 'Generate Merlin Notification with Quantity Impact' is invoked, and assuming that quantity change has been logged in audit trail, when generating notifications, the desired outcome is that a merlin notification message is generated including the quantity impact details.
💻 Technical Criteria
Given Quantity change has been logged in audit trail
When Generating notifications
Then A Merlin notification message is generated including the quantity impact details
R-GCX016E-cbl-00761 Generate Error Message for Unknown Disposition Code
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error Message for Unknown Disposition Code', assuming that a disposition code lookup in the dc table has failed, when the disposition code is not found, the desired outcome is that an error message is generated indicating unknown disposition code.
💻 Technical Criteria
EXCLUDING A disposition code lookup in the DC table has failed
When The disposition code is not found
Then An error message is generated indicating unknown disposition code
R-GCX016E-cbl-03000 Get Disposition Code Action Type
Decision Rules
📊 Business Logic Narrative
When the process 'Get Disposition Code Action Type' is invoked, and assuming that a disposition code is being processed, when the system evaluates the disposition code action requirements, the desired outcome is that the action type is classified as add, subtract, or status info only based on disposition code characteristics.
💻 Technical Criteria
Given A disposition code is being processed
When The system evaluates the disposition code action requirements
Then The action type is classified as Add, Subtract, or Status Info Only based on disposition code characteristics
R-GCX016E-cbl-03001 Add Quantity Action
Action Rules
📊 Business Logic Narrative
When the process 'Add Quantity Action' is invoked, and assuming that a disposition code with add action type is being processed, when the system determines quantity changes are required, the desired outcome is that the disposition code quantity is marked for addition to current release quantity.
💻 Technical Criteria
Given A disposition code with Add action type is being processed
When The system determines quantity changes are required
Then The disposition code quantity is marked for addition to current release quantity
R-GCX016E-cbl-03002 Subtract Quantity Action
Action Rules
📊 Business Logic Narrative
When the process 'Subtract Quantity Action' is invoked, and assuming that a disposition code with subtract action type is being processed, when the system determines quantity reduction is required, the desired outcome is that the disposition code quantity is marked for subtraction from current release quantity.
💻 Technical Criteria
Given A disposition code with Subtract action type is being processed
When The system determines quantity reduction is required
Then The disposition code quantity is marked for subtraction from current release quantity
R-GCX016E-cbl-03003 No Quantity Change Action
Action Rules
📊 Business Logic Narrative
When the process 'No Quantity Change Action' is invoked, and assuming that a disposition code with status info only action type is being processed, when the system determines no quantity changes are required, the desired outcome is that the processing completes without modifying release quantities.
💻 Technical Criteria
Given A disposition code with Status Info Only action type is being processed
When The system determines no quantity changes are required
Then The processing completes without modifying release quantities
R-GCX016E-cbl-03004 Calculate New Release Quantity
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate New Release Quantity' is invoked, and assuming that current release quantity and disposition code action are available, when the system performs quantity calculation, the desired outcome is that new release quantity is computed by adding or subtracting the disposition code quantity from current release quantity.
💻 Technical Criteria
Given Current release quantity and disposition code action are available
When The system performs quantity calculation
Then New release quantity is computed by adding or subtracting the disposition code quantity from current release quantity
R-GCX016E-cbl-03007 Set Release Qty = 0
Validation Rules
📊 Business Logic Narrative
When the process 'Set Release Qty = 0' is invoked, and assuming that calculated release quantity is less than zero, when the system applies quantity validation rules, the desired outcome is that release quantity is set to zero.
💻 Technical Criteria
Given Calculated release quantity is less than zero
When The system applies quantity validation rules
Then Release quantity is set to zero
R-GCX016E-cbl-03009 Log Quantity Change
Process Rules
📊 Business Logic Narrative
When the process 'Log Quantity Change' is invoked, and assuming that release quantity has been updated, when the system completes quantity processing, the desired outcome is that a log entry is created documenting the quantity change transaction.
💻 Technical Criteria
Given Release quantity has been updated
When The system completes quantity processing
Then A log entry is created documenting the quantity change transaction
R-GCX016E-cbl-03010 Create Before/After Comparison
Process Rules
📊 Business Logic Narrative
When the process 'Create Before/After Comparison' is invoked, and assuming that original and new release quantities are available, when the system documents quantity changes, the desired outcome is that a before and after comparison record is created showing quantity differences.
💻 Technical Criteria
Given Original and new release quantities are available
When The system documents quantity changes
Then A before and after comparison record is created showing quantity differences
R-GCX016E-cbl-03011 Generate Quantity Impact Message
Process Rules
📊 Business Logic Narrative
When the process 'Generate Quantity Impact Message' is invoked, and assuming that quantity changes have been processed and documented, when the system generates impact notifications, the desired outcome is that a quantity impact message is created showing the effect of disposition code on release quantities.
💻 Technical Criteria
Given Quantity changes have been processed and documented
When The system generates impact notifications
Then A quantity impact message is created showing the effect of disposition code on release quantities
R-GCX016E-cbl-00768 Lookup Disposition Code Description
Action Rules
📊 Business Logic Narrative
When the process 'Lookup Disposition Code Description' is invoked, and assuming that disposition code details are being collected, when the system looks up disposition codes in the dc table, the desired outcome is that descriptive text for each disposition code is retrieved and made available for notification.
💻 Technical Criteria
Given Disposition code details are being collected
When The system looks up disposition codes in the DC table
Then Descriptive text for each disposition code is retrieved and made available for notification
R-GCX016E-cbl-00769 Get Hold Reason Details
Process Rules
📊 Business Logic Narrative
When the process 'Get Hold Reason Details' is invoked, and assuming that disposition code descriptions have been retrieved, when the system analyzes disposition codes for hold-specific information, the desired outcome is that detailed hold reasons and explanatory information are extracted for notification purposes.
💻 Technical Criteria
Given Disposition code descriptions have been retrieved
When The system analyzes disposition codes for hold-specific information
Then Detailed hold reasons and explanatory information are extracted for notification purposes
R-GCX016E-cbl-00782 Create Comprehensive Hold Message
Process Rules
📊 Business Logic Narrative
When the process 'Create Comprehensive Hold Message' is invoked, and assuming that all message components including date and time have been formatted, when the system combines all elements into a final message, the desired outcome is that a comprehensive hold notification message is created with all required information properly structured.
💻 Technical Criteria
Given All message components including date and time have been formatted
When The system combines all elements into a final message
Then A comprehensive hold notification message is created with all required information properly structured
R-GCX016E-cbl-00784 Apply Message Template
Process Rules
📊 Business Logic Narrative
When the process 'Apply Message Template' is invoked, and assuming that all message elements have been combined, when the system applies the standard hold notification template, the desired outcome is that the message conforms to established format standards and includes all required sections.
💻 Technical Criteria
Given All message elements have been combined
When The system applies the standard hold notification template
Then The message conforms to established format standards and includes all required sections
R-GCX016E-cbl-00785 Validate Message Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Message Format' is invoked, and assuming that message template has been applied to the notification, when the system validates the message format and content, the desired outcome is that the message is confirmed to meet all format requirements and contains all mandatory information.
💻 Technical Criteria
Given Message template has been applied to the notification
When The system validates the message format and content
Then The message is confirmed to meet all format requirements and contains all mandatory information
R-GCX016E-cbl-00790 More Status Entries?
Decision Rules
📊 Business Logic Narrative
When the process 'More Status Entries?' is invoked, and assuming that the system is processing s09a status array entries, when the current entry position is evaluated, the desired outcome is that if more entries exist, continue processing; otherwise proceed to status evaluation.
💻 Technical Criteria
Given The system is processing S09A status array entries
When The current entry position is evaluated
Then If more entries exist, continue processing; otherwise proceed to status evaluation
R-GCX016E-cbl-00791 Analyze Individual Status Entry
Process Rules
📊 Business Logic Narrative
When the process 'Analyze Individual Status Entry' is invoked, and assuming that a status entry exists in the s09a array, when the entry is being processed, the desired outcome is that the disposition code, quantity, entry number, and other status data are extracted for analysis.
💻 Technical Criteria
Given A status entry exists in the S09A array
When The entry is being processed
Then The disposition code, quantity, entry number, and other status data are extracted for analysis
R-GCX016E-cbl-00792 Status Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Status Type?' is invoked, and assuming that a status entry with a disposition code is being analyzed, when the disposition code type is evaluated, the desired outcome is that the entry is classified as hold, release, proceed, or information type based on the disposition code characteristics.
💻 Technical Criteria
Given A status entry with a disposition code is being analyzed
When The disposition code type is evaluated
Then The entry is classified as Hold, Release, Proceed, or Information type based on the disposition code characteristics
R-GCX016E-cbl-00794 Process Release Disposition Code
Process Rules
📊 Business Logic Narrative
When the process 'Process Release Disposition Code' is invoked, and assuming that a status entry contains a release-type disposition code, when the release disposition code is processed, the desired outcome is that release-specific data including quantity, entry number, and release authority are extracted and processed.
💻 Technical Criteria
Given A status entry contains a release-type disposition code
When The release disposition code is processed
Then Release-specific data including quantity, entry number, and release authority are extracted and processed
R-GCX016E-cbl-00798 Update Release Status Flags
Process Rules
📊 Business Logic Narrative
When the process 'Update Release Status Flags' is invoked, and assuming that a release disposition code has been processed, when release status flags are updated, the desired outcome is that appropriate release flags are set including manual release, auto release, or ptt release based on the disposition code.
💻 Technical Criteria
Given A release disposition code has been processed
When Release status flags are updated
Then Appropriate release flags are set including manual release, auto release, or PTT release based on the disposition code
R-GCX016E-cbl-00800 Update Information Status Flags
Process Rules
📊 Business Logic Narrative
When the process 'Update Information Status Flags' is invoked, and assuming that an information disposition code has been processed, when information status flags are updated, the desired outcome is that information flags are set to record status details without affecting processing decisions.
💻 Technical Criteria
Given An information disposition code has been processed
When Information status flags are updated
Then Information flags are set to record status details without affecting processing decisions
R-GCX016E-cbl-00801 Evaluate Combined Status Conditions
Decision Rules
📊 Business Logic Narrative
When the process 'Evaluate Combined Status Conditions' is invoked, and assuming that all status entries have been processed and flags updated, when combined status evaluation occurs, the desired outcome is that the system evaluates the combination of hold, release, proceed, and information flags to determine final status.
💻 Technical Criteria
Given All status entries have been processed and flags updated
When Combined status evaluation occurs
Then The system evaluates the combination of hold, release, proceed, and information flags to determine final status
R-GCX016E-cbl-00803 Has Release Codes?
Decision Rules
📊 Business Logic Narrative
When the process 'Has Release Codes?' is invoked, and assuming that hold code evaluation is complete, when release code presence is evaluated, the desired outcome is that if release flags are set and override hold conditions, set released status; otherwise maintain hold status.
💻 Technical Criteria
Given Hold code evaluation is complete
When Release code presence is evaluated
Then If release flags are set and override hold conditions, set released status; otherwise maintain hold status
R-GCX016E-cbl-00804 Has Proceed Codes?
Decision Rules
📊 Business Logic Narrative
When the process 'Has Proceed Codes?' is invoked, and assuming that release code evaluation is complete and no overriding release found, when proceed code presence is evaluated, the desired outcome is that if proceed flags are set, set proceed status; otherwise set information-only status.
💻 Technical Criteria
Given Release code evaluation is complete and no overriding release found
When Proceed code presence is evaluated
Then If proceed flags are set, set proceed status; otherwise set information-only status
R-GCX016E-cbl-00809 Calculate Release Quantities
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Release Quantities' is invoked, and assuming that final status has been determined, when release quantity calculation occurs, the desired outcome is that all release quantities from disposition codes are summed to determine total released amount.
💻 Technical Criteria
Given Final status has been determined
When Release quantity calculation occurs
Then All release quantities from disposition codes are summed to determine total released amount
R-GCX016E-cbl-00815 Analyze Disposition Code
Decision Rules
📊 Business Logic Narrative
When the process 'Analyze Disposition Code' is invoked, and assuming that a status array entry contains a disposition code, when the system analyzes the disposition code, the desired outcome is that the disposition code is categorized as hold, release, proceed, or status info type.
💻 Technical Criteria
Given A status array entry contains a disposition code
When The system analyzes the disposition code
Then The disposition code is categorized as Hold, Release, Proceed, or Status Info type
R-GCX016E-cbl-00816 Code Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Code Type?' is invoked, and assuming that a disposition code has been analyzed and categorized, when the system determines the code type (hold, release, proceed, or status info), the desired outcome is that the appropriate processing path is selected based on the code type.
💻 Technical Criteria
Given A disposition code has been analyzed and categorized
When The system determines the code type (Hold, Release, Proceed, or Status Info)
Then The appropriate processing path is selected based on the code type
R-GCX016E-cbl-00817 Set Hold Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Hold Flag' is invoked, and assuming that a disposition code is categorized as a hold type, when the system processes the hold disposition code, the desired outcome is that the hold status flag is set to true for subsequent hold condition evaluation.
💻 Technical Criteria
Given A disposition code is categorized as a Hold type
When The system processes the hold disposition code
Then The hold status flag is set to true for subsequent hold condition evaluation
R-GCX016E-cbl-00818 Set Release Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Release Flag' is invoked, and assuming that a disposition code is categorized as a release type, when the system processes the release disposition code, the desired outcome is that the release status flag is set to true for subsequent release condition evaluation.
💻 Technical Criteria
Given A disposition code is categorized as a Release type
When The system processes the release disposition code
Then The release status flag is set to true for subsequent release condition evaluation
R-GCX016E-cbl-00819 Set Proceed Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Proceed Flag' is invoked, and assuming that a disposition code is categorized as a proceed type, when the system processes the proceed disposition code, the desired outcome is that the proceed status flag is set to true for subsequent proceed condition evaluation.
💻 Technical Criteria
Given A disposition code is categorized as a Proceed type
When The system processes the proceed disposition code
Then The proceed status flag is set to true for subsequent proceed condition evaluation
R-GCX016E-cbl-00820 Set Status Info Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Status Info Flag' is invoked, and assuming that a disposition code is categorized as status info type, when the system processes the informational disposition code, the desired outcome is that the status info flag is set and processing continues to next entry without further evaluation.
💻 Technical Criteria
Given A disposition code is categorized as Status Info type
When The system processes the informational disposition code
Then The status info flag is set and processing continues to next entry without further evaluation
R-GCX016E-cbl-00830 Evaluate Manual Release
Decision Rules
📊 Business Logic Narrative
When the process 'Evaluate Manual Release' is invoked, and assuming that proceed evaluation is complete or proceed status flag has been set, when the system checks for manual release disposition codes in the status array, the desired outcome is that manual release conditions are evaluated to determine if manual release business flag should be set.
💻 Technical Criteria
Given Proceed evaluation is complete or proceed status flag has been set
When The system checks for manual release disposition codes in the status array
Then Manual release conditions are evaluated to determine if manual release business flag should be set
R-GCX016E-cbl-03267 Release Overrides Hold?
Authorization Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Release Overrides Hold?', assuming that both hold and release conditions are present and hold does not take absolute precedence, when the system evaluates if release authorization can override the hold, the desired outcome is that the system determines if release conditions have sufficient authority to override hold conditions based on regulatory rules.
💻 Technical Criteria
EXCLUDING Both hold and release conditions are present and hold does not take absolute precedence
When The system evaluates if release authorization can override the hold
Then The system determines if release conditions have sufficient authority to override hold conditions based on regulatory rules
R-GCX016E-cbl-03269 Proceed Conditions Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Proceed Conditions Valid?' is invoked, and assuming that proceed conditions are present and neither hold nor release take precedence, when the system validates proceed condition legitimacy, the desired outcome is that the system determines if proceed conditions meet all regulatory requirements and can be applied as final status.
💻 Technical Criteria
Given Proceed conditions are present and neither hold nor release take precedence
When The system validates proceed condition legitimacy
Then The system determines if proceed conditions meet all regulatory requirements and can be applied as final status
R-GCX016E-cbl-03271 Arrival Status Valid?
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Arrival Status Valid?', assuming that arrival conditions are present and higher precedence conditions do not apply, when the system validates arrival status legitimacy, the desired outcome is that the system determines if arrival conditions meet all requirements and can be applied as final status.
💻 Technical Criteria
EXCLUDING Arrival conditions are present and higher precedence conditions do not apply
When The system validates arrival status legitimacy
Then The system determines if arrival conditions meet all requirements and can be applied as final status
R-GCX016E-cbl-03398 Identify New Disposition Code
Validation Rules
📊 Business Logic Narrative
When the process 'Identify New Disposition Code' is invoked, and assuming that a new disposition code is received from x4 segment processing, when the disposition code is ready for regulatory hierarchy evaluation, the desired outcome is that the system identifies the disposition code type and prepares it for hierarchy processing.
💻 Technical Criteria
Given A new disposition code is received from X4 segment processing
When The disposition code is ready for regulatory hierarchy evaluation
Then The system identifies the disposition code type and prepares it for hierarchy processing
R-GCX016E-cbl-03399 Check Disposition Code Type
Decision Rules
📊 Business Logic Narrative
When the process 'Check Disposition Code Type' is invoked, and assuming that a disposition code is identified for processing, when the system evaluates the disposition code characteristics, the desired outcome is that the disposition code is classified as hold code, release code, proceed code, or status info based on its regulatory function.
💻 Technical Criteria
Given A disposition code is identified for processing
When The system evaluates the disposition code characteristics
Then The disposition code is classified as Hold Code, Release Code, Proceed Code, or Status Info based on its regulatory function
R-GCX016E-cbl-03401 Apply Release Code Hierarchy
Policy Rules
📊 Business Logic Narrative
When the process 'Apply Release Code Hierarchy' is invoked, and assuming that a disposition code is classified as a release code type, when regulatory hierarchy processing is applied, the desired outcome is that the system applies release-specific precedence rules including manual releases, auto releases, and ptt releases with quantity validation requirements.
💻 Technical Criteria
Given A disposition code is classified as a Release Code type
When Regulatory hierarchy processing is applied
Then The system applies release-specific precedence rules including manual releases, auto releases, and PTT releases with quantity validation requirements
R-GCX016E-cbl-03404 Check for Conflicting Codes
Validation Rules
📊 Business Logic Narrative
When the process 'Check for Conflicting Codes' is invoked, and assuming that a new disposition code is processed and existing status array contains disposition codes, when the system evaluates code compatibility, the desired outcome is that the system identifies if conflicts exist between the new code and existing codes based on regulatory business rules.
💻 Technical Criteria
Given A new disposition code is processed and existing status array contains disposition codes
When The system evaluates code compatibility
Then The system identifies if conflicts exist between the new code and existing codes based on regulatory business rules
R-GCX016E-cbl-03405 Identify Counterpart Codes
Decision Rules
📊 Business Logic Narrative
When the process 'Identify Counterpart Codes' is invoked, and assuming that conflicting disposition codes are detected in the status array, when the system processes counterpart code logic, the desired outcome is that the system identifies specific counterpart codes that must be removed based on regulatory requirements and business logic.
💻 Technical Criteria
Given Conflicting disposition codes are detected in the status array
When The system processes counterpart code logic
Then The system identifies specific counterpart codes that must be removed based on regulatory requirements and business logic
R-GCX016E-cbl-03407 Higher Priority Code?
Decision Rules
📊 Business Logic Narrative
When the process 'Higher Priority Code?' is invoked, and assuming that regulatory precedence rules are applied to conflicting disposition codes, when the system evaluates priority levels, the desired outcome is that the system determines if the new disposition code has higher priority than existing codes based on regulatory hierarchy.
💻 Technical Criteria
Given Regulatory precedence rules are applied to conflicting disposition codes
When The system evaluates priority levels
Then The system determines if the new disposition code has higher priority than existing codes based on regulatory hierarchy
R-GCX016E-cbl-03408 Remove Lower Priority Code
Action Rules
📊 Business Logic Narrative
When the process 'Remove Lower Priority Code' is invoked, and assuming that a disposition code is determined to have lower priority than a conflicting code, when priority resolution is executed, the desired outcome is that the system removes the lower priority disposition code from the status array and maintains audit trail.
💻 Technical Criteria
Given A disposition code is determined to have lower priority than a conflicting code
When Priority resolution is executed
Then The system removes the lower priority disposition code from the status array and maintains audit trail
R-GCX016E-cbl-03409 Keep Higher Priority Code
Action Rules
📊 Business Logic Narrative
When the process 'Keep Higher Priority Code' is invoked, and assuming that a disposition code is determined to have higher priority than conflicting codes, when priority resolution is executed, the desired outcome is that the system retains the higher priority disposition code in the status array and proceeds with processing.
💻 Technical Criteria
Given A disposition code is determined to have higher priority than conflicting codes
When Priority resolution is executed
Then The system retains the higher priority disposition code in the status array and proceeds with processing
R-GCX016E-cbl-03410 Validate Final Code Combination
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Final Code Combination' is invoked, and assuming that disposition code conflicts are resolved and final codes are determined, when final validation is performed, the desired outcome is that the system validates that the final combination of disposition codes is legally compliant and business-rule compliant.
💻 Technical Criteria
Given Disposition code conflicts are resolved and final codes are determined
When Final validation is performed
Then The system validates that the final combination of disposition codes is legally compliant and business-rule compliant
R-GCX016E-cbl-03412 Apply Default Regulatory Action
Policy Rules
📊 Business Logic Narrative
When the process 'Apply Default Regulatory Action' is invoked, and assuming that final disposition code combination fails regulatory compliance check, when default regulatory action is triggered, the desired outcome is that the system applies predefined default actions to ensure regulatory compliance including hold placement or status correction.
💻 Technical Criteria
Given Final disposition code combination fails regulatory compliance check
When Default regulatory action is triggered
Then The system applies predefined default actions to ensure regulatory compliance including hold placement or status correction
R-GCX016E-cbl-03414 Log Regulatory Decision
Process Rules
📊 Business Logic Narrative
When the process 'Log Regulatory Decision' is invoked, and assuming that regulatory hierarchy processing is completed and status array is updated, when audit logging is performed, the desired outcome is that the system logs the regulatory decisions made, codes removed or added, and rationale for compliance and audit purposes.
💻 Technical Criteria
Given Regulatory hierarchy processing is completed and status array is updated
When Audit logging is performed
Then The system logs the regulatory decisions made, codes removed or added, and rationale for compliance and audit purposes
R-GCX016E-cbl-03518 Check for Conflicting Codes?
Decision Rules
📊 Business Logic Narrative
When the process 'Check for Conflicting Codes?' is invoked, and assuming that a new disposition code and existing status array with current disposition codes, when the system checks for regulatory conflicts between codes, the desired outcome is that the system determines if conflicting codes exist that require precedence rule application.
💻 Technical Criteria
Given A new disposition code and existing status array with current disposition codes
When The system checks for regulatory conflicts between codes
Then The system determines if conflicting codes exist that require precedence rule application
R-GCX016E-cbl-03520 Higher Priority Code Exists?
Decision Rules
📊 Business Logic Narrative
When the process 'Higher Priority Code Exists?' is invoked, and assuming that regulatory hierarchy has been applied to conflicting disposition codes, when the system evaluates code priorities, the desired outcome is that the system determines if an existing code has higher regulatory priority than the new code.
💻 Technical Criteria
Given Regulatory hierarchy has been applied to conflicting disposition codes
When The system evaluates code priorities
Then The system determines if an existing code has higher regulatory priority than the new code
R-GCX016E-cbl-03521 Remove Lower Priority Code
Action Rules
📊 Business Logic Narrative
When the process 'Remove Lower Priority Code' is invoked, and assuming that a higher priority disposition code exists compared to a lower priority code, when the system applies precedence rules, the desired outcome is that the system removes the lower priority code from the status array.
💻 Technical Criteria
Given A higher priority disposition code exists compared to a lower priority code
When The system applies precedence rules
Then The system removes the lower priority code from the status array
R-GCX016E-cbl-03522 Keep Higher Priority Code
Action Rules
📊 Business Logic Narrative
When the process 'Keep Higher Priority Code' is invoked, and assuming that an existing disposition code has higher priority than the new code, when the system applies precedence rules, the desired outcome is that the system keeps the existing higher priority code and may reject or modify the new code.
💻 Technical Criteria
Given An existing disposition code has higher priority than the new code
When The system applies precedence rules
Then The system keeps the existing higher priority code and may reject or modify the new code
R-GCX016E-cbl-03524 Precedence Rules Satisfied?
Decision Rules
📊 Business Logic Narrative
When the process 'Precedence Rules Satisfied?' is invoked, and assuming that regulatory compliance validation has been performed, when the system checks if precedence rules are satisfied, the desired outcome is that the system determines if all precedence requirements have been met successfully.
💻 Technical Criteria
Given Regulatory compliance validation has been performed
When The system checks if precedence rules are satisfied
Then The system determines if all precedence requirements have been met successfully
R-GCX016E-cbl-03526 Log Precedence Decision
Process Rules
📊 Business Logic Narrative
When the process 'Log Precedence Decision' is invoked, and assuming that precedence rules have been applied and status array updated, when the system logs the precedence decision, the desired outcome is that the system records the precedence actions, removed codes, and regulatory justification for audit purposes.
💻 Technical Criteria
Given Precedence rules have been applied and status array updated
When The system logs the precedence decision
Then The system records the precedence actions, removed codes, and regulatory justification for audit purposes
R-GCX016E-cbl-03527 Generate Conflict Warning
Action Rules
📊 Business Logic Narrative
When the process 'Generate Conflict Warning' is invoked, and assuming that precedence rules cannot be satisfied or regulatory conflicts exist, when the system encounters unresolvable precedence issues, the desired outcome is that the system generates appropriate conflict warnings for manual review and intervention.
💻 Technical Criteria
Given Precedence rules cannot be satisfied or regulatory conflicts exist
When The system encounters unresolvable precedence issues
Then The system generates appropriate conflict warnings for manual review and intervention
R-GCX016E-cbl-03528 Apply Default Precedence Rule
Policy Rules
📊 Business Logic Narrative
When the process 'Apply Default Precedence Rule' is invoked, and assuming that specific precedence rules cannot resolve disposition code conflicts, when the system applies default precedence rules, the desired outcome is that the system uses predefined default hierarchy to resolve conflicts and proceed with processing.
💻 Technical Criteria
Given Specific precedence rules cannot resolve disposition code conflicts
When The system applies default precedence rules
Then The system uses predefined default hierarchy to resolve conflicts and proceed with processing
R-GCX016E-cbl-00880 Preserve Previous Status for Audit
Policy Rules
📊 Business Logic Narrative
When the process 'Preserve Previous Status for Audit' is invoked, and assuming that release cancellation has been detected, when processing the cancellation event, the desired outcome is that the system preserves previous status information in audit records.
💻 Technical Criteria
Given Release cancellation has been detected
When Processing the cancellation event
Then The system preserves previous status information in audit records
R-GCX016E-cbl-00881 Generate Cancel Release Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Cancel Release Notification' is invoked, and assuming that release cancellation has been confirmed and previous status preserved, when notification generation is triggered, the desired outcome is that the system creates a cancel release notification message.
💻 Technical Criteria
Given Release cancellation has been confirmed and previous status preserved
When Notification generation is triggered
Then The system creates a cancel release notification message
R-GCX016E-cbl-00882 Format Notification Message
Process Rules
📊 Business Logic Narrative
When the process 'Format Notification Message' is invoked, and assuming that cancel release notification needs to be generated, when message formatting process begins, the desired outcome is that the system formats notification message with proper structure and headers.
💻 Technical Criteria
Given Cancel release notification needs to be generated
When Message formatting process begins
Then The system formats notification message with proper structure and headers
R-GCX016E-cbl-00888 Log Cancel Release Action
Policy Rules
📊 Business Logic Narrative
When the process 'Log Cancel Release Action' is invoked, and assuming that cancel release notification has been sent to business recipients, when action logging is performed, the desired outcome is that the system logs cancel release action with timestamp and recipient information.
💻 Technical Criteria
Given Cancel release notification has been sent to business recipients
When Action logging is performed
Then The system logs cancel release action with timestamp and recipient information
R-GCX016E-cbl-00964 Format Date/Time Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Date/Time Information' is invoked, and assuming that current system date and time are available, when the system prepares release notification content, the desired outcome is that the system formats date and time in the required format for inclusion in the notification message.
💻 Technical Criteria
Given Current system date and time are available
When The system prepares release notification content
Then The system formats date and time in the required format for inclusion in the notification message
R-GCX016E-cbl-00965 Include Release Quantity Impact
Process Rules
📊 Business Logic Narrative
When the process 'Include Release Quantity Impact' is invoked, and assuming that release quantities have been calculated, when the system prepares the notification message content, the desired outcome is that the system includes details about quantity changes and impact of the release action in the message.
💻 Technical Criteria
Given Release quantities have been calculated
When The system prepares the notification message content
Then The system includes details about quantity changes and impact of the release action in the message
R-GCX016E-cbl-00966 Add Before/After Quantity Comparison
Process Rules
📊 Business Logic Narrative
When the process 'Add Before/After Quantity Comparison' is invoked, and assuming that quantity impact information has been prepared, when the system finalizes notification message content, the desired outcome is that the system includes before and after quantity comparison data to show the effect of the release.
💻 Technical Criteria
Given Quantity impact information has been prepared
When The system finalizes notification message content
Then The system includes before and after quantity comparison data to show the effect of the release
R-GCX016E-cbl-00971 Prepare Message for Distribution
Action Rules
📊 Business Logic Narrative
When the process 'Prepare Message for Distribution' is invoked, and assuming that a complete release message with proper type assignment exists, when the system prepares for message distribution, the desired outcome is that the system readies the message for delivery through appropriate notification channels including merlin routing and email systems.
💻 Technical Criteria
Given A complete release message with proper type assignment exists
When The system prepares for message distribution
Then The system readies the message for delivery through appropriate notification channels including Merlin routing and email systems
R-GCX016E-cbl-01003 Include Date/Time Information
Process Rules
📊 Business Logic Narrative
When the process 'Include Date/Time Information' is invoked, and assuming that an arrival notification is being formatted, when the system includes date/time information, the desired outcome is that the system adds arrival date, arrival time, and processing timestamp to the notification message.
💻 Technical Criteria
Given An arrival notification is being formatted
When The system includes date/time information
Then The system adds arrival date, arrival time, and processing timestamp to the notification message
R-GCX016E-cbl-01004 Add Disposition Code Details
Process Rules
📊 Business Logic Narrative
When the process 'Add Disposition Code Details' is invoked, and assuming that an arrival notification is being formatted, when the system adds disposition code details, the desired outcome is that the system includes the disposition code, code description, and any associated quantities or references in the notification message.
💻 Technical Criteria
Given An arrival notification is being formatted
When The system adds disposition code details
Then The system includes the disposition code, code description, and any associated quantities or references in the notification message
R-GCX016E-cbl-01006 Message Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Message Type?' is invoked, and assuming that an arrival notification is ready for distribution, when the system determines message type, the desired outcome is that the system classifies the message as arrcanl (arrival cancellation) or other arrival type for proper routing.
💻 Technical Criteria
Given An arrival notification is ready for distribution
When The system determines message type
Then The system classifies the message as ARRCANL (arrival cancellation) or other arrival type for proper routing
R-GCX016E-cbl-01009 Log Arrival Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Arrival Action' is invoked, and assuming that an arrival notification has been successfully distributed, when the system logs the arrival action, the desired outcome is that the system creates a log entry recording the arrival event, processing details, and distribution results.
💻 Technical Criteria
Given An arrival notification has been successfully distributed
When The system logs the arrival action
Then The system creates a log entry recording the arrival event, processing details, and distribution results
R-GCX016E-cbl-01010 Update Audit Trail
Process Rules
📊 Business Logic Narrative
When the process 'Update Audit Trail' is invoked, and assuming that an arrival action has been logged, when the system updates the audit trail, the desired outcome is that the system records the arrival processing in the audit trail with timestamp, user information, and processing results.
💻 Technical Criteria
Given An arrival action has been logged
When The system updates the audit trail
Then The system records the arrival processing in the audit trail with timestamp, user information, and processing results
R-GCX016E-cbl-01025 Extract SCAC Code from M10
Process Rules
📊 Business Logic Narrative
When the process 'Extract SCAC Code from M10' is invoked, and assuming that an m10 input segment is received containing carrier information, when the system processes the m10 segment for scac code extraction, the desired outcome is that the scac code is extracted from the designated field position in the m10 segment.
💻 Technical Criteria
Given An M10 input segment is received containing carrier information
When The system processes the M10 segment for SCAC code extraction
Then The SCAC code is extracted from the designated field position in the M10 segment
R-GCX016E-cbl-01027 Extract Country Code from M10
Process Rules
📊 Business Logic Narrative
When the process 'Extract Country Code from M10' is invoked, and assuming that an m10 input segment is received containing country information, when the system processes the m10 segment for country code extraction, the desired outcome is that the country code is extracted from the designated field position in the m10 segment.
💻 Technical Criteria
Given An M10 input segment is received containing country information
When The system processes the M10 segment for country code extraction
Then The country code is extracted from the designated field position in the M10 segment
R-GCX016E-cbl-01028 Extract Vessel Details from M10
Process Rules
📊 Business Logic Narrative
When the process 'Extract Vessel Details from M10' is invoked, and assuming that an m10 input segment is received containing vessel information, when the system processes the m10 segment for vessel details extraction, the desired outcome is that the vessel name and related details are extracted from the designated field positions in the m10 segment.
💻 Technical Criteria
Given An M10 input segment is received containing vessel information
When The system processes the M10 segment for vessel details extraction
Then The vessel name and related details are extracted from the designated field positions in the M10 segment
R-GCX016E-cbl-01030 Set Default SCAC if Invalid
Decision Rules
📊 Business Logic Narrative
When the process 'Set Default SCAC if Invalid' is invoked, and assuming that the extracted scac code has failed validation, when the system needs to assign a scac code for processing, the desired outcome is that a default scac code is assigned to ensure processing can continue.
💻 Technical Criteria
Given The extracted SCAC code has failed validation
When The system needs to assign a SCAC code for processing
Then A default SCAC code is assigned to ensure processing can continue
R-GCX016E-cbl-01034 Set Default Country Code
Decision Rules
📊 Business Logic Narrative
When the process 'Set Default Country Code' is invoked, and assuming that the extracted country code has failed validation, when the system needs to assign a country code for processing, the desired outcome is that a default country code is assigned to ensure processing can continue.
💻 Technical Criteria
Given The extracted country code has failed validation
When The system needs to assign a country code for processing
Then A default country code is assigned to ensure processing can continue
R-GCX016E-cbl-01041 Log Incomplete Manifest Warning
Process Rules
📊 Business Logic Narrative
When the process 'Log Incomplete Manifest Warning' is invoked, and assuming that the m10 segment has failed completeness validation, when the system processes the incomplete segment, the desired outcome is that a warning message is logged indicating the manifest is incomplete but processing continues.
💻 Technical Criteria
Given The M10 segment has failed completeness validation
When The system processes the incomplete segment
Then A warning message is logged indicating the manifest is incomplete but processing continues
R-GCX016E-cbl-01056 Insert Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'Insert Successful?' is invoked, and assuming that a database insert operation has been executed, when the system evaluates the insert operation result, the desired outcome is that the insert operation is classified as either successful or failed based on the database response.
💻 Technical Criteria
Given A database insert operation has been executed
When The system evaluates the insert operation result
Then The insert operation is classified as either successful or failed based on the database response
R-GCX016E-cbl-01064 Retrieve Key Station Data
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Key Station Data' is invoked, and assuming that a key station lookup is required, when the system processes the key station request, the desired outcome is that the system initiates retrieval of key station data from the ks table.
💻 Technical Criteria
Given A key station lookup is required
When The system processes the key station request
Then The system initiates retrieval of key station data from the KS table
R-GCX016E-cbl-01065 Call Generic Table I/O Interface
Action Rules
📊 Business Logic Narrative
When the process 'Call Generic Table I/O Interface' is invoked, and assuming that station data retrieval is required from either ds or ks table, when the system needs to access table data, the desired outcome is that the system calls the generic table i/o interface to facilitate data access.
💻 Technical Criteria
Given Station data retrieval is required from either DS or KS table
When The system needs to access table data
Then The system calls the generic table I/O interface to facilitate data access
R-GCX016E-cbl-01067 Access KS Table via GCCTBIO
Action Rules
📊 Business Logic Narrative
When the process 'Access KS Table via GCCTBIO' is invoked, and assuming that key station data is required, when the system executes table access through gcctbio, the desired outcome is that the system retrieves data from the ks table containing key station information.
💻 Technical Criteria
Given Key station data is required
When The system executes table access through GCCTBIO
Then The system retrieves data from the KS table containing key station information
R-GCX016E-cbl-01069 Extract Station Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Station Information' is invoked, and assuming that a station record has been found in the table, when the system processes the retrieved station data, the desired outcome is that the system extracts the relevant station information fields for further processing.
💻 Technical Criteria
Given A station record has been found in the table
When The system processes the retrieved station data
Then The system extracts the relevant station information fields for further processing
R-GCX016E-cbl-01071 Set Station Data Fields
Process Rules
📊 Business Logic Narrative
When the process 'Set Station Data Fields' is invoked, and assuming that station information has been validated successfully, when the system processes the validated station data, the desired outcome is that the system sets the appropriate station data fields with the retrieved information.
💻 Technical Criteria
Given Station information has been validated successfully
When The system processes the validated station data
Then The system sets the appropriate station data fields with the retrieved information
R-GCX016E-cbl-01072 Handle Station Not Found
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Handle Station Not Found', assuming that a station lookup has been performed, when the requested station is not found in the table, the desired outcome is that the system initiates error handling procedures for the missing station.
💻 Technical Criteria
EXCLUDING A station lookup has been performed
When The requested station is not found in the table
Then The system initiates error handling procedures for the missing station
R-GCX016E-cbl-01073 Return Station Information
Process Rules
📊 Business Logic Narrative
When the process 'Return Station Information' is invoked, and assuming that station data processing has been completed (either successfully or with error handling), when the system finalizes the station lookup process, the desired outcome is that the system returns the station information or error status to the requesting process.
💻 Technical Criteria
Given Station data processing has been completed (either successfully or with error handling)
When The system finalizes the station lookup process
Then The system returns the station information or error status to the requesting process
R-GCX016E-cbl-01074 Log Station Lookup Error
Process Rules
📊 Business Logic Narrative
When the process 'Log Station Lookup Error' is invoked, and assuming that a station lookup error has occurred, when the system processes the error condition, the desired outcome is that the system logs the station lookup error for audit and troubleshooting purposes.
💻 Technical Criteria
Given A station lookup error has occurred
When The system processes the error condition
Then The system logs the station lookup error for audit and troubleshooting purposes
R-GCX016E-cbl-01078 Call Generic Table I/O Interface - GCCTBIO
Action Rules
📊 Business Logic Narrative
When the process 'Call Generic Table I/O Interface - GCCTBIO' is invoked, and assuming that the ds table type is configured for station lookup, when the system needs to retrieve station information, the desired outcome is that the generic table i/o interface gcctbio is called to access station data.
💻 Technical Criteria
Given The DS table type is configured for station lookup
When The system needs to retrieve station information
Then The generic table I/O interface GCCTBIO is called to access station data
R-GCX016E-cbl-01079 Station Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Station Record Found?' is invoked, and assuming that the generic table interface has been called for station lookup, when the system checks the lookup results, the desired outcome is that if station record is found, proceed with station data retrieval, otherwise generate station not found error.
💻 Technical Criteria
Given The generic table interface has been called for station lookup
When The system checks the lookup results
Then If station record is found, proceed with station data retrieval, otherwise generate station not found error
R-GCX016E-cbl-01082 Validate Station Information
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Station Information' is invoked, and assuming that station name and routing data have been extracted, when the system validates the station information, the desired outcome is that the station information is checked for completeness and validity.
💻 Technical Criteria
Given Station name and routing data have been extracted
When The system validates the station information
Then The station information is checked for completeness and validity
R-GCX016E-cbl-01083 Station Valid for Routing?
Decision Rules
📊 Business Logic Narrative
When the process 'Station Valid for Routing?' is invoked, and assuming that station information has been validated, when the system checks station validity for routing, the desired outcome is that if station is valid for routing, set station data in working storage, otherwise log station lookup failure.
💻 Technical Criteria
Given Station information has been validated
When The system checks station validity for routing
Then If station is valid for routing, set station data in working storage, otherwise log station lookup failure
R-GCX016E-cbl-01085 Log Station Lookup Success
Process Rules
📊 Business Logic Narrative
When the process 'Log Station Lookup Success' is invoked, and assuming that station data has been successfully set in working storage, when the station lookup operation completes successfully, the desired outcome is that a success message is logged for the station lookup operation.
💻 Technical Criteria
Given Station data has been successfully set in working storage
When The station lookup operation completes successfully
Then A success message is logged for the station lookup operation
R-GCX016E-cbl-01087 Log Station Lookup Failure
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Station Lookup Failure', assuming that station lookup has failed due to invalid station information or station not found, when the station lookup operation encounters an error, the desired outcome is that a failure message is logged for the station lookup operation.
💻 Technical Criteria
EXCLUDING Station lookup has failed due to invalid station information or station not found
When The station lookup operation encounters an error
Then A failure message is logged for the station lookup operation
R-GCX016E-cbl-01096 Continue with Validated Station Data
Process Rules
📊 Business Logic Narrative
When the process 'Continue with Validated Station Data' is invoked, and assuming that key station lookup processing has completed with either valid station data or error condition, when the system continues with subsequent processing steps, the desired outcome is that processing continues using the validated station data or appropriate error handling for missing stations.
💻 Technical Criteria
Given Key station lookup processing has completed with either valid station data or error condition
When The system continues with subsequent processing steps
Then Processing continues using the validated station data or appropriate error handling for missing stations
R-GCX016E-cbl-01099 Key Station Lookup - KS Table
Process Rules
📊 Business Logic Narrative
When the process 'Key Station Lookup - KS Table' is invoked, and assuming that a request for key station data lookup is received with a station identifier, when the system accesses the ks table in gcstbrt, the desired outcome is that the system retrieves key station operational data and configuration information.
💻 Technical Criteria
Given A request for key station data lookup is received with a station identifier
When The system accesses the KS table in GCSTBRT
Then The system retrieves key station operational data and configuration information
R-GCX016E-cbl-01100 Disposition Code Lookup - DC Table
Validation Rules
📊 Business Logic Narrative
When the process 'Disposition Code Lookup - DC Table' is invoked, and assuming that a disposition code lookup request is received with a specific disposition code, when the system accesses the dc table in gcstbrt, the desired outcome is that the system retrieves disposition code details including processing instructions, status implications, and validation rules.
💻 Technical Criteria
Given A disposition code lookup request is received with a specific disposition code
When The system accesses the DC table in GCSTBRT
Then The system retrieves disposition code details including processing instructions, status implications, and validation rules
R-GCX016E-cbl-01101 Broker Information Lookup
Process Rules
📊 Business Logic Narrative
When the process 'Broker Information Lookup' is invoked, and assuming that a broker information lookup request is received with broker identification, when the system accesses the broker table in gcst2rt, the desired outcome is that the system retrieves broker contact information, credentials, and processing preferences.
💻 Technical Criteria
Given A broker information lookup request is received with broker identification
When The system accesses the broker table in GCST2RT
Then The system retrieves broker contact information, credentials, and processing preferences
R-GCX016E-cbl-01103 Validate Table Key
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Table Key' is invoked, and assuming that a table lookup key is provided for validation, when the system performs key validation checks, the desired outcome is that the system verifies the key format, length, and content validity before proceeding with table access.
💻 Technical Criteria
Given A table lookup key is provided for validation
When The system performs key validation checks
Then The system verifies the key format, length, and content validity before proceeding with table access
R-GCX016E-cbl-01104 Table Record Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Table Record Found?' is invoked, and assuming that a validated table key has been used to search the target table, when the system checks for record existence, the desired outcome is that the system returns true if a matching record is found, false if no record exists for the given key.
💻 Technical Criteria
Given A validated table key has been used to search the target table
When The system checks for record existence
Then The system returns true if a matching record is found, false if no record exists for the given key
R-GCX016E-cbl-01105 Retrieve Table Data
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Table Data' is invoked, and assuming that a matching table record has been located, when the system retrieves the record data, the desired outcome is that the system extracts all relevant fields and formats them for return to the requesting process.
💻 Technical Criteria
Given A matching table record has been located
When The system retrieves the record data
Then The system extracts all relevant fields and formats them for return to the requesting process
R-GCX016E-cbl-01106 Return Table Information
Process Rules
📊 Business Logic Narrative
When the process 'Return Table Information' is invoked, and assuming that table data has been successfully retrieved and formatted, when the system prepares to return the information, the desired outcome is that the system returns the complete table information with success status to the calling process.
💻 Technical Criteria
Given Table data has been successfully retrieved and formatted
When The system prepares to return the information
Then The system returns the complete table information with success status to the calling process
R-GCX016E-cbl-01107 Generate Table Not Found Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Table Not Found Error', assuming that a table lookup has been performed but no matching record was found, when the system needs to handle the not found condition, the desired outcome is that the system generates a table not found error with relevant details about the failed lookup.
💻 Technical Criteria
EXCLUDING A table lookup has been performed but no matching record was found
When The system needs to handle the not found condition
Then The system generates a table not found error with relevant details about the failed lookup
R-GCX016E-cbl-01108 Return Error Status
Process Rules
📊 Business Logic Narrative
When the process 'Return Error Status' is invoked, and assuming that a table lookup operation has failed or no record was found, when the system needs to communicate the failure to the calling process, the desired outcome is that the system returns error status with descriptive information about the failure reason.
💻 Technical Criteria
Given A table lookup operation has failed or no record was found
When The system needs to communicate the failure to the calling process
Then The system returns error status with descriptive information about the failure reason
R-GCX016E-cbl-01121 Prepare Message for Distribution
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Message for Distribution' is invoked, and assuming that a complete merlin message with assigned type and priority is ready for distribution, when the system prepares the message for distribution, the desired outcome is that the system finalizes message routing, determines delivery methods, and prepares the message for transmission to appropriate recipients.
💻 Technical Criteria
Given A complete Merlin message with assigned type and priority is ready for distribution
When The system prepares the message for distribution
Then The system finalizes message routing, determines delivery methods, and prepares the message for transmission to appropriate recipients
R-GCX016E-cbl-03032 Format Disposition Code and Description
Process Rules
📊 Business Logic Narrative
When the process 'Format Disposition Code and Description' is invoked, and assuming that disposition code information is available, when the system formats message content, the desired outcome is that disposition code and description are formatted for merlin message display.
💻 Technical Criteria
Given Disposition code information is available
When The system formats message content
Then Disposition code and description are formatted for Merlin message display
R-GCX016E-cbl-03033 Calculate Release Quantity Impact
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Release Quantity Impact' is invoked, and assuming that a disposition code with quantity information exists, when the system processes quantity impact analysis, the desired outcome is that the impact on release quantity is calculated and determined.
💻 Technical Criteria
Given A disposition code with quantity information exists
When The system processes quantity impact analysis
Then The impact on release quantity is calculated and determined
R-GCX016E-cbl-03037 Add Quantity Change Details
Process Rules
📊 Business Logic Narrative
When the process 'Add Quantity Change Details' is invoked, and assuming that before and after release quantities have been displayed, when the system processes quantity change details, the desired outcome is that detailed quantity change information is added to the message content.
💻 Technical Criteria
Given Before and after release quantities have been displayed
When The system processes quantity change details
Then Detailed quantity change information is added to the message content
R-GCX016E-cbl-03039 Add Free-Form Text Messages
Process Rules
📊 Business Logic Narrative
When the process 'Add Free-Form Text Messages' is invoked, and assuming that free-form text messages exist from disposition code processing, when the system assembles message content, the desired outcome is that free-form text messages are added to the merlin message content.
💻 Technical Criteria
Given Free-form text messages exist from disposition code processing
When The system assembles message content
Then Free-form text messages are added to the Merlin message content
R-GCX016E-cbl-03045 Format Date and Time Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Date and Time Information' is invoked, and assuming that processing date and time information is available, when the system formats message content, the desired outcome is that date and time information is formatted according to merlin message standards.
💻 Technical Criteria
Given Processing date and time information is available
When The system formats message content
Then Date and time information is formatted according to Merlin message standards
R-GCX016E-cbl-03046 Add USCS Processing Time
Process Rules
📊 Business Logic Narrative
When the process 'Add USCS Processing Time' is invoked, and assuming that uscs processing time is available, when the system adds time information, the desired outcome is that uscs processing time is included in the merlin message content.
💻 Technical Criteria
Given USCS processing time is available
When The system adds time information
Then USCS processing time is included in the Merlin message content
R-GCX016E-cbl-03047 Add System Processing Time
Process Rules
📊 Business Logic Narrative
When the process 'Add System Processing Time' is invoked, and assuming that system processing time is available, when the system adds time information, the desired outcome is that system processing time is included in the merlin message content.
💻 Technical Criteria
Given System processing time is available
When The system adds time information
Then System processing time is included in the Merlin message content
R-GCX016E-cbl-03050 Finalize Merlin Message
Process Rules
📊 Business Logic Narrative
When the process 'Finalize Merlin Message' is invoked, and assuming that message format has been validated successfully, when the system finalizes the message, the desired outcome is that merlin message is finalized and ready for transmission.
💻 Technical Criteria
Given Message format has been validated successfully
When The system finalizes the message
Then Merlin message is finalized and ready for transmission
R-GCX016E-cbl-03278 Extract Free-Form Text Content
Process Rules
📊 Business Logic Narrative
When the process 'Extract Free-Form Text Content' is invoked, and assuming that a valid k1 segment has been received, when the system processes the k1 segment to extract message content, the desired outcome is that the free-form text content is extracted and made available for comment type determination.
💻 Technical Criteria
Given A valid K1 segment has been received
When The system processes the K1 segment to extract message content
Then The free-form text content is extracted and made available for comment type determination
R-GCX016E-cbl-03279 Determine Comment Type
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Comment Type' is invoked, and assuming that free-form text content has been extracted from a k1 segment, when the system analyzes the content to determine comment classification, the desired outcome is that the comment is classified as either special comment type or standard comment type based on content analysis.
💻 Technical Criteria
Given Free-form text content has been extracted from a K1 segment
When The system analyzes the content to determine comment classification
Then The comment is classified as either special comment type or standard comment type based on content analysis
R-GCX016E-cbl-03281 Store K1 Comment in Memory
Process Rules
📊 Business Logic Narrative
When the process 'Store K1 Comment in Memory' is invoked, and assuming that a k1 comment has been processed and classified, when the system stores the comment for integration with disposition processing, the desired outcome is that the k1 comment is stored in memory with up to 4 lines of comment text available for notification integration.
💻 Technical Criteria
Given A K1 comment has been processed and classified
When The system stores the comment for integration with disposition processing
Then The K1 comment is stored in memory with up to 4 lines of comment text available for notification integration
R-GCX016E-cbl-03282 Associate with Current Disposition Code
Process Rules
📊 Business Logic Narrative
When the process 'Associate with Current Disposition Code' is invoked, and assuming that a k1 comment is stored in memory and a disposition code is being processed, when the system associates the comment with the current disposition code context, the desired outcome is that the k1 comment becomes available for inclusion in disposition code notifications and merlin messages.
💻 Technical Criteria
Given A K1 comment is stored in memory and a disposition code is being processed
When The system associates the comment with the current disposition code context
Then The K1 comment becomes available for inclusion in disposition code notifications and Merlin messages
R-GCX016E-cbl-03285 Include in Release Quantity Impact Message
Process Rules
📊 Business Logic Narrative
When the process 'Include in Release Quantity Impact Message' is invoked, and assuming that k1 comments are integrated with merlin messages and release quantity impacts are being calculated, when the system generates messages showing quantity impact of disposition codes, the desired outcome is that k1 comments are included to provide additional context about how release quantities will be affected (add/subtract).
💻 Technical Criteria
Given K1 comments are integrated with Merlin messages and release quantity impacts are being calculated
When The system generates messages showing quantity impact of disposition codes
Then K1 comments are included to provide additional context about how release quantities will be affected (add/subtract)
R-GCX016E-cbl-03286 Log Invalid K1 Segment
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Invalid K1 Segment', assuming that a k1 segment fails format validation, when the system processes the invalid segment, the desired outcome is that the invalid k1 segment is logged for audit purposes and processing continues without including the invalid comment.
💻 Technical Criteria
EXCLUDING A K1 segment fails format validation
When The system processes the invalid segment
Then The invalid K1 segment is logged for audit purposes and processing continues without including the invalid comment
R-GCX016E-cbl-03420 Set Standard Comment Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Standard Comment Flag' is invoked, and assuming that a k1 comment has been identified as a standard comment, when the system processes the comment classification, the desired outcome is that a standard comment flag is set to indicate this comment follows normal processing procedures.
💻 Technical Criteria
Given A K1 comment has been identified as a standard comment
When The system processes the comment classification
Then A standard comment flag is set to indicate this comment follows normal processing procedures
R-GCX016E-cbl-03421 Store Comment for Processing
Process Rules
📊 Business Logic Narrative
When the process 'Store Comment for Processing' is invoked, and assuming that a k1 comment has been classified and flagged appropriately, when the system prepares the comment for processing, the desired outcome is that the comment text and its classification flags are stored in the appropriate processing structures.
💻 Technical Criteria
Given A K1 comment has been classified and flagged appropriately
When The system prepares the comment for processing
Then The comment text and its classification flags are stored in the appropriate processing structures
R-GCX016E-cbl-03531 Train Disposition Comment Pattern
Decision Rules
📊 Business Logic Narrative
When the process 'Train Disposition Comment Pattern' is invoked, and assuming that k1 segment comment text content is available for analysis, when the comment contains train-related disposition information, the desired outcome is that the system identifies this as a train disposition comment pattern and sets the train comment processing flag.
💻 Technical Criteria
Given K1 segment comment text content is available for analysis
When The comment contains train-related disposition information
Then The system identifies this as a train disposition comment pattern and sets the train comment processing flag
R-GCX016E-cbl-03535 Set Train Comment Processing Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Train Comment Processing Flag' is invoked, and assuming that train disposition comment pattern has been detected in the comment, when the system processes the pattern detection result, the desired outcome is that the train comment processing flag is set to indicate special train processing is required.
💻 Technical Criteria
Given Train disposition comment pattern has been detected in the comment
When The system processes the pattern detection result
Then The train comment processing flag is set to indicate special train processing is required
R-GCX016E-cbl-03537 Set General Comment Processing Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set General Comment Processing Flag' is invoked, and assuming that general comment pattern has been detected in the comment, when the system processes the pattern detection result, the desired outcome is that the general comment processing flag is set to indicate standard comment processing is required.
💻 Technical Criteria
Given General comment pattern has been detected in the comment
When The system processes the pattern detection result
Then The general comment processing flag is set to indicate standard comment processing is required
R-GCX016E-cbl-03539 Store Comment for Merlin Integration
Process Rules
📊 Business Logic Narrative
When the process 'Store Comment for Merlin Integration' is invoked, and assuming that processing requirements have been determined for the comment, when the system prepares the comment for downstream processing, the desired outcome is that the comment is stored in the appropriate format for merlin integration.
💻 Technical Criteria
Given Processing requirements have been determined for the comment
When The system prepares the comment for downstream processing
Then The comment is stored in the appropriate format for Merlin integration
R-GCX016E-cbl-01133 Identify Disposition Code Type
Definitional Rules
📊 Business Logic Narrative
When the process 'Identify Disposition Code Type' is invoked, and assuming that a disposition code is being processed, when the system needs to determine quantity impact, the desired outcome is that the disposition code type and characteristics are identified from the dc table.
💻 Technical Criteria
Given A disposition code is being processed
When The system needs to determine quantity impact
Then The disposition code type and characteristics are identified from the DC table
R-GCX016E-cbl-01134 Disposition Code Affects Release Quantity?
Decision Rules
📊 Business Logic Narrative
When the process 'Disposition Code Affects Release Quantity?' is invoked, and assuming that a disposition code with defined characteristics, when the system evaluates quantity impact potential, the desired outcome is that the system determines if the disposition code affects release quantities based on code type and action flags.
💻 Technical Criteria
Given A disposition code with defined characteristics
When The system evaluates quantity impact potential
Then The system determines if the disposition code affects release quantities based on code type and action flags
R-GCX016E-cbl-01136 Determine Add or Subtract Action
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Add or Subtract Action' is invoked, and assuming that a disposition code with calculated quantity impact, when the system determines the direction of quantity change, the desired outcome is that the system identifies whether the action is to add or subtract from current release quantity based on disposition code action type.
💻 Technical Criteria
Given A disposition code with calculated quantity impact
When The system determines the direction of quantity change
Then The system identifies whether the action is to add or subtract from current release quantity based on disposition code action type
R-GCX016E-cbl-01137 Add to Release Quantity
Computation Rules
📊 Business Logic Narrative
When the process 'Add to Release Quantity' is invoked, and assuming that a disposition code that increases release quantity and calculated impact amount, when the action type is determined to be addition, the desired outcome is that the calculated amount is added to the current release quantity.
💻 Technical Criteria
Given A disposition code that increases release quantity and calculated impact amount
When The action type is determined to be addition
Then The calculated amount is added to the current release quantity
R-GCX016E-cbl-01138 Subtract from Release Quantity
Computation Rules
📊 Business Logic Narrative
When the process 'Subtract from Release Quantity' is invoked, and assuming that a disposition code that decreases release quantity and calculated impact amount, when the action type is determined to be subtraction, the desired outcome is that the calculated amount is subtracted from the current release quantity.
💻 Technical Criteria
Given A disposition code that decreases release quantity and calculated impact amount
When The action type is determined to be subtraction
Then The calculated amount is subtracted from the current release quantity
R-GCX016E-cbl-01139 Calculate New Release Quantity
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate New Release Quantity' is invoked, and assuming that current release quantity and calculated quantity impact with determined action, when final quantity calculation is performed, the desired outcome is that the system calculates the new release quantity by applying the add or subtract action to the current quantity.
💻 Technical Criteria
Given Current release quantity and calculated quantity impact with determined action
When Final quantity calculation is performed
Then The system calculates the new release quantity by applying the add or subtract action to the current quantity
R-GCX016E-cbl-01143 Create Quantity Impact Message
Process Rules
📊 Business Logic Narrative
When the process 'Create Quantity Impact Message' is invoked, and assuming that formatted before quantity, after quantity, and disposition code description, when impact message creation is performed, the desired outcome is that the system creates a formatted message showing the quantity impact of the disposition code.
💻 Technical Criteria
Given Formatted before quantity, after quantity, and disposition code description
When Impact message creation is performed
Then The system creates a formatted message showing the quantity impact of the disposition code
R-GCX016E-cbl-01144 Include Impact Details in Merlin Message
Process Rules
📊 Business Logic Narrative
When the process 'Include Impact Details in Merlin Message' is invoked, and assuming that created quantity impact message and existing merlin message structure, when merlin message assembly is performed, the desired outcome is that the quantity impact details are included in the merlin message for stakeholder notification.
💻 Technical Criteria
Given Created quantity impact message and existing Merlin message structure
When Merlin message assembly is performed
Then The quantity impact details are included in the Merlin message for stakeholder notification
R-GCX016E-cbl-01145 Add Special Comments if Available
Process Rules
📊 Business Logic Narrative
When the process 'Add Special Comments if Available' is invoked, and assuming that quantity impact message and available k1 segment comments, when special comments are available for inclusion, the desired outcome is that the system adds up to the maximum allowed special comments to the impact message.
💻 Technical Criteria
Given Quantity impact message and available K1 segment comments
When Special comments are available for inclusion
Then The system adds up to the maximum allowed special comments to the impact message
R-GCX016E-cbl-01160 Search Broker Database for Freight Forwarder Codes
Validation Rules
📊 Business Logic Narrative
When the process 'Search Broker Database for Freight Forwarder Codes' is invoked, and assuming that a disposition code needs to be validated for freight forwarder processing, when the system searches the gcst2rt broker database for freight forwarder disposition codes, the desired outcome is that the system identifies whether the disposition code exists in the freight forwarder records.
💻 Technical Criteria
Given A disposition code needs to be validated for freight forwarder processing
When The system searches the GCST2RT broker database for freight forwarder disposition codes
Then The system identifies whether the disposition code exists in the freight forwarder records
R-GCX016E-cbl-01161 Disposition Code Found in Broker Database?
Decision Rules
📊 Business Logic Narrative
When the process 'Disposition Code Found in Broker Database?' is invoked, and assuming that a disposition code has been searched in the broker database, when the system evaluates if the disposition code was found in the freight forwarder records, the desired outcome is that the system either proceeds with freight forwarder information retrieval or marks it as a standard disposition code.
💻 Technical Criteria
Given A disposition code has been searched in the broker database
When The system evaluates if the disposition code was found in the freight forwarder records
Then The system either proceeds with freight forwarder information retrieval or marks it as a standard disposition code
R-GCX016E-cbl-01164 Mark Code as Valid Freight Forwarder Disposition
Process Rules
📊 Business Logic Narrative
When the process 'Mark Code as Valid Freight Forwarder Disposition' is invoked, and assuming that a disposition code has been validated as a legitimate freight forwarder code, when the system marks the code as a valid freight forwarder disposition, the desired outcome is that the system sets the freight forwarder processing flag and continues with freight forwarder-specific processing.
💻 Technical Criteria
Given A disposition code has been validated as a legitimate freight forwarder code
When The system marks the code as a valid freight forwarder disposition
Then The system sets the freight forwarder processing flag and continues with freight forwarder-specific processing
R-GCX016E-cbl-01165 Mark Code as Standard Disposition Code
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Mark Code as Standard Disposition Code', assuming that a disposition code is either not found in the broker database or fails freight forwarder validation, when the system marks the code as a standard disposition code, the desired outcome is that the system continues with standard disposition code processing without freight forwarder-specific handling.
💻 Technical Criteria
EXCLUDING A disposition code is either not found in the broker database or fails freight forwarder validation
When The system marks the code as a standard disposition code
Then The system continues with standard disposition code processing without freight forwarder-specific handling
R-GCX016E-cbl-01179 Freight Forwarder Code Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Freight Forwarder Code Found?' is invoked, and assuming that the broker table search for freight forwarder disposition codes has been completed, when the system evaluates the search results, the desired outcome is that the system determines if a freight forwarder code was found and proceeds with appropriate processing path.
💻 Technical Criteria
Given The broker table search for freight forwarder disposition codes has been completed
When The system evaluates the search results
Then The system determines if a freight forwarder code was found and proceeds with appropriate processing path
R-GCX016E-cbl-01184 Retrieve Associated Broker Information
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Associated Broker Information' is invoked, and assuming that the freight forwarder name has been successfully looked up in broker tables, when the system requires complete broker information for the freight forwarder, the desired outcome is that the system retrieves associated broker information from the gcstbrt broker table segments.
💻 Technical Criteria
Given The freight forwarder name has been successfully looked up in broker tables
When The system requires complete broker information for the freight forwarder
Then The system retrieves associated broker information from the GCSTBRT broker table segments
R-GCX016E-cbl-01185 Get Freight Forwarder Contact Details
Action Rules
📊 Business Logic Narrative
When the process 'Get Freight Forwarder Contact Details' is invoked, and assuming that associated broker information has been retrieved for the freight forwarder, when the system needs contact information for freight forwarder notifications, the desired outcome is that the system retrieves freight forwarder contact details including email addresses and communication preferences from broker table segments.
💻 Technical Criteria
Given Associated broker information has been retrieved for the freight forwarder
When The system needs contact information for freight forwarder notifications
Then The system retrieves freight forwarder contact details including email addresses and communication preferences from broker table segments
R-GCX016E-cbl-01186 Compile Complete Freight Forwarder Profile
Process Rules
📊 Business Logic Narrative
When the process 'Compile Complete Freight Forwarder Profile' is invoked, and assuming that all freight forwarder information components have been retrieved including name, broker details, and contact information, when the system needs to create a complete freight forwarder profile, the desired outcome is that the system compiles all retrieved information into a comprehensive freight forwarder profile.
💻 Technical Criteria
Given All freight forwarder information components have been retrieved including name, broker details, and contact information
When The system needs to create a complete freight forwarder profile
Then The system compiles all retrieved information into a comprehensive freight forwarder profile
R-GCX016E-cbl-01188 No Freight Forwarder Information Available
Process Rules
📊 Business Logic Narrative
When the process 'No Freight Forwarder Information Available' is invoked, and assuming that no freight forwarder code was found during the broker table search, when the system cannot locate freight forwarder information for the disposition code, the desired outcome is that the system indicates that no freight forwarder information is available and continues processing without freight forwarder-specific actions.
💻 Technical Criteria
Given No freight forwarder code was found during the broker table search
When The system cannot locate freight forwarder information for the disposition code
Then The system indicates that no freight forwarder information is available and continues processing without freight forwarder-specific actions
R-GCX016E-cbl-01191 Look up Freight Forwarder Name in Broker Database
Action Rules
📊 Business Logic Narrative
When the process 'Look up Freight Forwarder Name in Broker Database' is invoked, and assuming that a valid freight forwarder code exists, when the system performs a lookup in the gcst2rt broker name segments, the desired outcome is that the corresponding freight forwarder name is retrieved from the database.
💻 Technical Criteria
Given A valid freight forwarder code exists
When The system performs a lookup in the GCST2RT broker name segments
Then The corresponding freight forwarder name is retrieved from the database
R-GCX016E-cbl-01192 Freight Forwarder Name Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Freight Forwarder Name Found?' is invoked, and assuming that a lookup has been performed in the broker name database, when the system checks the lookup results, the desired outcome is that if freight forwarder name is found, proceed to retrieve broker information; otherwise log name not found and end process.
💻 Technical Criteria
Given A lookup has been performed in the broker name database
When The system checks the lookup results
Then If freight forwarder name is found, proceed to retrieve broker information; otherwise log name not found and end process
R-GCX016E-cbl-01193 Retrieve Associated Broker Information
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Associated Broker Information' is invoked, and assuming that a valid freight forwarder name has been found, when the system retrieves associated broker information, the desired outcome is that the broker details linked to the freight forwarder are obtained for email address lookup.
💻 Technical Criteria
Given A valid freight forwarder name has been found
When The system retrieves associated broker information
Then The broker details linked to the freight forwarder are obtained for email address lookup
R-GCX016E-cbl-01194 Broker Information Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Broker Information Available?' is invoked, and assuming that a freight forwarder name has been found in the database, when the system checks for associated broker information, the desired outcome is that if broker information is available, proceed to fetch email address; otherwise log no broker information and end process.
💻 Technical Criteria
Given A freight forwarder name has been found in the database
When The system checks for associated broker information
Then If broker information is available, proceed to fetch email address; otherwise log no broker information and end process
R-GCX016E-cbl-01195 Fetch Email Address from Broker Table
Action Rules
📊 Business Logic Narrative
When the process 'Fetch Email Address from Broker Table' is invoked, and assuming that valid broker information is available, when the system accesses the gcstbrt broker table segments, the desired outcome is that the email address associated with the broker is retrieved from the table.
💻 Technical Criteria
Given Valid broker information is available
When The system accesses the GCSTBRT broker table segments
Then The email address associated with the broker is retrieved from the table
R-GCX016E-cbl-01196 Email Address Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Email Address Found?' is invoked, and assuming that a lookup has been performed in the broker table, when the system checks if an email address was found, the desired outcome is that if email address exists, proceed to validation; otherwise log no email address found and end process.
💻 Technical Criteria
Given A lookup has been performed in the broker table
When The system checks if an email address was found
Then If email address exists, proceed to validation; otherwise log no email address found and end process
R-GCX016E-cbl-01198 Email Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Email Valid?' is invoked, and assuming that email address format validation has been performed, when the system evaluates the validation results, the desired outcome is that if email format is valid, store for notification; otherwise log invalid format and end process.
💻 Technical Criteria
Given Email address format validation has been performed
When The system evaluates the validation results
Then If email format is valid, store for notification; otherwise log invalid format and end process
R-GCX016E-cbl-01199 Store Email Address for Notification
Process Rules
📊 Business Logic Narrative
When the process 'Store Email Address for Notification' is invoked, and assuming that a valid email address has been confirmed, when the system stores the email address, the desired outcome is that the email address is saved for subsequent notification processing.
💻 Technical Criteria
Given A valid email address has been confirmed
When The system stores the email address
Then The email address is saved for subsequent notification processing
R-GCX016E-cbl-01201 Log: Freight Forwarder Name Not Found
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log: Freight Forwarder Name Not Found', assuming that a freight forwarder code exists but name lookup has been performed, when the freight forwarder name is not found in the broker database, the desired outcome is that a log entry is created indicating the freight forwarder name was not found.
💻 Technical Criteria
EXCLUDING A freight forwarder code exists but name lookup has been performed
When The freight forwarder name is not found in the broker database
Then A log entry is created indicating the freight forwarder name was not found
R-GCX016E-cbl-01202 Log: No Broker Information Available
Process Rules
📊 Business Logic Narrative
When the process 'Log: No Broker Information Available' is invoked, and assuming that a freight forwarder name has been found, when no associated broker information is available, the desired outcome is that a log entry is created indicating no broker information is available.
💻 Technical Criteria
Given A freight forwarder name has been found
When No associated broker information is available
Then A log entry is created indicating no broker information is available
R-GCX016E-cbl-01203 Log: No Email Address Found
Process Rules
📊 Business Logic Narrative
When the process 'Log: No Email Address Found' is invoked, and assuming that broker information is available and email lookup has been performed, when no email address is found in the broker table, the desired outcome is that a log entry is created indicating no email address was found.
💻 Technical Criteria
Given Broker information is available and email lookup has been performed
When No email address is found in the broker table
Then A log entry is created indicating no email address was found
R-GCX016E-cbl-01204 Log: Invalid Email Format
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log: Invalid Email Format', assuming that an email address has been retrieved and format validation performed, when the email address format is determined to be invalid, the desired outcome is that a log entry is created indicating the email format is invalid.
💻 Technical Criteria
EXCLUDING An email address has been retrieved and format validation performed
When The email address format is determined to be invalid
Then A log entry is created indicating the email format is invalid
R-GCX016E-cbl-01211 Valid Freight Forwarder?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid Freight Forwarder?' is invoked, and assuming that freight forwarder name and broker information lookup has been completed, when the system validates the retrieved freight forwarder data, the desired outcome is that if the freight forwarder information is valid and complete, proceed with email address retrieval, otherwise complete notification process without sending email.
💻 Technical Criteria
Given Freight forwarder name and broker information lookup has been completed
When The system validates the retrieved freight forwarder data
Then If the freight forwarder information is valid and complete, proceed with email address retrieval, otherwise complete notification process without sending email
R-GCX016E-cbl-01213 Email Address Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Email Address Found?' is invoked, and assuming that the system has attempted to retrieve an email address from the broker table, when the email address retrieval results are evaluated, the desired outcome is that if a valid email address is found, proceed with email content building, otherwise complete notification process without sending email.
💻 Technical Criteria
Given The system has attempted to retrieve an email address from the broker table
When The email address retrieval results are evaluated
Then If a valid email address is found, proceed with email content building, otherwise complete notification process without sending email
R-GCX016E-cbl-01220 Include Processing Timestamps
Process Rules
📊 Business Logic Narrative
When the process 'Include Processing Timestamps' is invoked, and assuming that cih disposition information has been included in the email content, when the system processes timestamp information, the desired outcome is that the system includes processing date, time, and relevant timestamps in the email notification content.
💻 Technical Criteria
Given CIH disposition information has been included in the email content
When The system processes timestamp information
Then The system includes processing date, time, and relevant timestamps in the email notification content
R-GCX016E-cbl-01221 Send Email Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send Email Notification' is invoked, and assuming that comprehensive email content has been built with all required information, when the system attempts to send the email notification, the desired outcome is that the system transmits the email to the freight forwarder's email address and captures delivery status.
💻 Technical Criteria
Given Comprehensive email content has been built with all required information
When The system attempts to send the email notification
Then The system transmits the email to the freight forwarder's email address and captures delivery status
R-GCX016E-cbl-01222 Email Delivery Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Email Delivery Successful?' is invoked, and assuming that an email notification has been sent to the freight forwarder, when the system evaluates the email delivery status, the desired outcome is that if email delivery is successful, log successful delivery, otherwise initiate retry process.
💻 Technical Criteria
Given An email notification has been sent to the freight forwarder
When The system evaluates the email delivery status
Then If email delivery is successful, log successful delivery, otherwise initiate retry process
R-GCX016E-cbl-01223 Log Successful Email Delivery
Process Rules
📊 Business Logic Narrative
When the process 'Log Successful Email Delivery' is invoked, and assuming that email notification has been successfully delivered, when the system processes the successful delivery status, the desired outcome is that the system logs the successful email delivery with timestamp and recipient information.
💻 Technical Criteria
Given Email notification has been successfully delivered
When The system processes the successful delivery status
Then The system logs the successful email delivery with timestamp and recipient information
R-GCX016E-cbl-01224 Retry Email Delivery
Process Rules
📊 Business Logic Narrative
When the process 'Retry Email Delivery' is invoked, and assuming that email notification delivery has failed, when the system initiates retry processing, the desired outcome is that the system attempts to resend the email notification and tracks retry attempts.
💻 Technical Criteria
Given Email notification delivery has failed
When The system initiates retry processing
Then The system attempts to resend the email notification and tracks retry attempts
R-GCX016E-cbl-01226 Log Email Delivery Failure
Process Rules
📊 Business Logic Narrative
When the process 'Log Email Delivery Failure' is invoked, and assuming that email delivery retry limit has been reached without successful delivery, when the system processes the final delivery failure, the desired outcome is that the system logs the email delivery failure with error details and retry attempt information.
💻 Technical Criteria
Given Email delivery retry limit has been reached without successful delivery
When The system processes the final delivery failure
Then The system logs the email delivery failure with error details and retry attempt information
R-GCX016E-cbl-03057 Freight Forwarder Name Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Freight Forwarder Name Found?' is invoked, and assuming that the broker name table gcst2rt has been searched for the freight forwarder name, when the search results are evaluated, the desired outcome is that if the freight forwarder name is found, proceed to retrieve contact information, otherwise log freight forwarder not found.
💻 Technical Criteria
Given The broker name table GCST2RT has been searched for the freight forwarder name
When The search results are evaluated
Then If the freight forwarder name is found, proceed to retrieve contact information, otherwise log freight forwarder not found
R-GCX016E-cbl-03058 Retrieve Freight Forwarder Contact Information
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Freight Forwarder Contact Information' is invoked, and assuming that the freight forwarder name has been successfully found in the broker name table, when complete contact information is needed for notification processing, the desired outcome is that the system retrieves freight forwarder contact information from the broker database.
💻 Technical Criteria
Given The freight forwarder name has been successfully found in the broker name table
When Complete contact information is needed for notification processing
Then The system retrieves freight forwarder contact information from the broker database
R-GCX016E-cbl-03059 Get Email Address from Broker Table GCSTBRT
Action Rules
📊 Business Logic Narrative
When the process 'Get Email Address from Broker Table GCSTBRT' is invoked, and assuming that freight forwarder contact information has been retrieved, when an email address is needed for electronic notification, the desired outcome is that the system retrieves the email address from the gcstbrt broker table.
💻 Technical Criteria
Given Freight forwarder contact information has been retrieved
When An email address is needed for electronic notification
Then The system retrieves the email address from the GCSTBRT broker table
R-GCX016E-cbl-03060 Email Address Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Email Address Available?' is invoked, and assuming that the broker table has been searched for the freight forwarder's email address, when the system needs to determine the notification method, the desired outcome is that if an email address is available, set the freight forwarder identified flag, otherwise log freight forwarder not found.
💻 Technical Criteria
Given The broker table has been searched for the freight forwarder's email address
When The system needs to determine the notification method
Then If an email address is available, set the freight forwarder identified flag, otherwise log freight forwarder not found
R-GCX016E-cbl-03061 Set Freight Forwarder Identified Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Freight Forwarder Identified Flag' is invoked, and assuming that a freight forwarder has been successfully identified with available contact information, when the freight forwarder validation process is complete, the desired outcome is that the system sets the freight forwarder identified flag to indicate successful identification.
💻 Technical Criteria
Given A freight forwarder has been successfully identified with available contact information
When The freight forwarder validation process is complete
Then The system sets the freight forwarder identified flag to indicate successful identification
R-GCX016E-cbl-03062 Store Freight Forwarder Details for Processing
Process Rules
📊 Business Logic Narrative
When the process 'Store Freight Forwarder Details for Processing' is invoked, and assuming that the freight forwarder identified flag has been set, when freight forwarder details need to be preserved for notification processing, the desired outcome is that the system stores freight forwarder details including contact information and email address for processing.
💻 Technical Criteria
Given The freight forwarder identified flag has been set
When Freight forwarder details need to be preserved for notification processing
Then The system stores freight forwarder details including contact information and email address for processing
R-GCX016E-cbl-03063 Log Freight Forwarder Not Found
Process Rules
📊 Business Logic Narrative
When the process 'Log Freight Forwarder Not Found' is invoked, and assuming that the freight forwarder identification process has failed at any validation step, when no valid freight forwarder can be identified for the disposition code, the desired outcome is that the system logs that the freight forwarder was not found and continues processing without freight forwarder notification.
💻 Technical Criteria
Given The freight forwarder identification process has failed at any validation step
When No valid freight forwarder can be identified for the disposition code
Then The system logs that the freight forwarder was not found and continues processing without freight forwarder notification
R-GCX016E-cbl-03290 Freight Forwarder ID Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Freight Forwarder ID Found?' is invoked, and assuming that freight forwarder identifier extraction has been completed, when the system evaluates the extraction results, the desired outcome is that the system determines if a valid freight forwarder id was found and proceeds accordingly.
💻 Technical Criteria
Given Freight forwarder identifier extraction has been completed
When The system evaluates the extraction results
Then The system determines if a valid freight forwarder ID was found and proceeds accordingly
R-GCX016E-cbl-03292 Validate Broker Relationship
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Broker Relationship' is invoked, and assuming that freight forwarder information has been located in the broker database, when the system evaluates the broker-freight forwarder relationship, the desired outcome is that the system validates whether a legitimate broker relationship exists.
💻 Technical Criteria
Given Freight forwarder information has been located in the broker database
When The system evaluates the broker-freight forwarder relationship
Then The system validates whether a legitimate broker relationship exists
R-GCX016E-cbl-03294 Retrieve Freight Forwarder Name
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Freight Forwarder Name' is invoked, and assuming that a valid broker relationship has been established with the freight forwarder, when the system needs freight forwarder identification details, the desired outcome is that the system retrieves the freight forwarder name from the broker records.
💻 Technical Criteria
Given A valid broker relationship has been established with the freight forwarder
When The system needs freight forwarder identification details
Then The system retrieves the freight forwarder name from the broker records
R-GCX016E-cbl-03295 Retrieve Contact Information
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Contact Information' is invoked, and assuming that freight forwarder name has been retrieved from broker records, when the system needs to obtain contact details for notifications, the desired outcome is that the system retrieves contact information from gcstbrt table segments.
💻 Technical Criteria
Given Freight forwarder name has been retrieved from broker records
When The system needs to obtain contact details for notifications
Then The system retrieves contact information from GCSTBRT table segments
R-GCX016E-cbl-03299 Set No Notification Required Flag
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set No Notification Required Flag', assuming that either no freight forwarder id was found, no valid broker relationship exists, or the scenario is not a cih hold, when the system determines notification requirements, the desired outcome is that the system sets the no notification required flag to bypass email delivery.
💻 Technical Criteria
EXCLUDING Either no freight forwarder ID was found, no valid broker relationship exists, or the scenario is not a CIH hold
When The system determines notification requirements
Then The system sets the no notification required flag to bypass email delivery
R-GCX016E-cbl-03423 Search GCST2RT Broker Database
Action Rules
📊 Business Logic Narrative
When the process 'Search GCST2RT Broker Database' is invoked, and assuming that a disposition code needs to be processed for freight forwarder validation, when the system searches the gcst2rt broker database for matching freight forwarder records, the desired outcome is that the system retrieves broker segments that match the disposition code criteria.
💻 Technical Criteria
Given A disposition code needs to be processed for freight forwarder validation
When The system searches the GCST2RT broker database for matching freight forwarder records
Then The system retrieves broker segments that match the disposition code criteria
R-GCX016E-cbl-03424 Broker Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Broker Record Found?' is invoked, and assuming that a search has been performed against the gcst2rt broker database, when the system evaluates the search results for broker record existence, the desired outcome is that the system returns true if a broker record is found, false if no matching record exists.
💻 Technical Criteria
Given A search has been performed against the GCST2RT broker database
When The system evaluates the search results for broker record existence
Then The system returns true if a broker record is found, false if no matching record exists
R-GCX016E-cbl-03425 Valid Freight Forwarder?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid Freight Forwarder?' is invoked, and assuming that a broker record has been found in the database, when the system validates the freight forwarder relationship status, the desired outcome is that the system confirms the broker is authorized to act as a freight forwarder for the given context.
💻 Technical Criteria
Given A broker record has been found in the database
When The system validates the freight forwarder relationship status
Then The system confirms the broker is authorized to act as a freight forwarder for the given context
R-GCX016E-cbl-03426 Retrieve Broker Information
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Broker Information' is invoked, and assuming that a valid freight forwarder relationship has been confirmed, when the system retrieves detailed broker information from the record, the desired outcome is that the system extracts broker identification, contact details, and operational parameters.
💻 Technical Criteria
Given A valid freight forwarder relationship has been confirmed
When The system retrieves detailed broker information from the record
Then The system extracts broker identification, contact details, and operational parameters
R-GCX016E-cbl-03427 Authorized for Disposition Code?
Authorization Rules
📊 Business Logic Narrative
When the process 'Authorized for Disposition Code?' is invoked, and assuming that broker information has been retrieved for a freight forwarder, when the system validates the broker's authority for the specific disposition code, the desired outcome is that the system confirms the freight forwarder is authorized to process this disposition code type.
💻 Technical Criteria
Given Broker information has been retrieved for a freight forwarder
When The system validates the broker's authority for the specific disposition code
Then The system confirms the freight forwarder is authorized to process this disposition code type
R-GCX016E-cbl-03428 Set Freight Forwarder Found Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Freight Forwarder Found Flag' is invoked, and assuming that a freight forwarder has been validated and authorized for disposition code processing, when the system sets the freight forwarder found flag, the desired outcome is that the system marks the freight forwarder as available for subsequent processing operations.
💻 Technical Criteria
Given A freight forwarder has been validated and authorized for disposition code processing
When The system sets the freight forwarder found flag
Then The system marks the freight forwarder as available for subsequent processing operations
R-GCX016E-cbl-03429 Store Broker Details
Process Rules
📊 Business Logic Narrative
When the process 'Store Broker Details' is invoked, and assuming that a freight forwarder has been successfully identified and validated, when the system stores the broker details in working storage, the desired outcome is that the system retains broker identification, contact information, and authorization details for processing.
💻 Technical Criteria
Given A freight forwarder has been successfully identified and validated
When The system stores the broker details in working storage
Then The system retains broker identification, contact information, and authorization details for processing
R-GCX016E-cbl-03430 Log Freight Forwarder Not Found
Process Rules
📊 Business Logic Narrative
When the process 'Log Freight Forwarder Not Found' is invoked, and assuming that no valid freight forwarder record exists or the broker lacks proper authorization or the freight forwarder relationship is invalid, when the system processes the freight forwarder search failure, the desired outcome is that the system logs the freight forwarder not found event for audit and troubleshooting purposes.
💻 Technical Criteria
Given No valid freight forwarder record exists OR the broker lacks proper authorization OR the freight forwarder relationship is invalid
When The system processes the freight forwarder search failure
Then The system logs the freight forwarder not found event for audit and troubleshooting purposes
R-GCX016E-cbl-03431 Continue with Standard Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue with Standard Processing' is invoked, and assuming that freight forwarder search has completed without finding a valid authorized freight forwarder, when the system continues with standard processing procedures, the desired outcome is that the system processes the disposition code using standard business rules without freight forwarder-specific handling.
💻 Technical Criteria
Given Freight forwarder search has completed without finding a valid authorized freight forwarder
When The system continues with standard processing procedures
Then The system processes the disposition code using standard business rules without freight forwarder-specific handling
R-GCX016E-cbl-03541 Search Broker Database for Freight Forwarder Codes
Validation Rules
📊 Business Logic Narrative
When the process 'Search Broker Database for Freight Forwarder Codes' is invoked, and assuming that a disposition code has been retrieved from x4 segment, when the system searches the gcstbrt broker database for freight forwarder disposition codes, the desired outcome is that the system identifies whether the disposition code requires freight forwarder validation.
💻 Technical Criteria
Given A disposition code has been retrieved from X4 segment
When The system searches the GCSTBRT broker database for freight forwarder disposition codes
Then The system identifies whether the disposition code requires freight forwarder validation
R-GCX016E-cbl-03545 Freight Forwarder Authorized for This Disposition?
Authorization Rules
📊 Business Logic Narrative
When the process 'Freight Forwarder Authorized for This Disposition?' is invoked, and assuming that a valid broker-freight forwarder relationship has been established, when the system validates authorization for the specific disposition code, the desired outcome is that the system determines whether the freight forwarder is authorized to use this disposition code.
💻 Technical Criteria
Given A valid broker-freight forwarder relationship has been established
When The system validates authorization for the specific disposition code
Then The system determines whether the freight forwarder is authorized to use this disposition code
R-GCX016E-cbl-03546 Set Freight Forwarder as Validated
Process Rules
📊 Business Logic Narrative
When the process 'Set Freight Forwarder as Validated' is invoked, and assuming that the freight forwarder has been authorized for the disposition code, when the system sets the freight forwarder validation status, the desired outcome is that the freight forwarder is marked as validated and approved for email notification processing.
💻 Technical Criteria
Given The freight forwarder has been authorized for the disposition code
When The system sets the freight forwarder validation status
Then The freight forwarder is marked as validated and approved for email notification processing
R-GCX016E-cbl-03547 Retrieve Freight Forwarder Contact Information
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Freight Forwarder Contact Information' is invoked, and assuming that the freight forwarder has been validated and approved, when the system retrieves freight forwarder contact information, the desired outcome is that the system obtains email addresses and notification preferences for the freight forwarder.
💻 Technical Criteria
Given The freight forwarder has been validated and approved
When The system retrieves freight forwarder contact information
Then The system obtains email addresses and notification preferences for the freight forwarder
R-GCX016E-cbl-03548 Mark Validation as Failed - Unauthorized
Authorization Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Mark Validation as Failed - Unauthorized', assuming that a valid broker-freight forwarder relationship exists but authorization check fails, when the freight forwarder is not authorized for the disposition code, the desired outcome is that the system marks validation as failed due to unauthorized access and skips email notification.
💻 Technical Criteria
EXCLUDING A valid broker-freight forwarder relationship exists but authorization check fails
When The freight forwarder is not authorized for the disposition code
Then The system marks validation as failed due to unauthorized access and skips email notification
R-GCX016E-cbl-03549 Mark Validation as Failed - Invalid Relationship
Validation Rules
📊 Business Logic Narrative
When the process 'Mark Validation as Failed - Invalid Relationship' is invoked, and assuming that freight forwarder lookup has been performed in the broker name table, when no valid broker-freight forwarder relationship is found, the desired outcome is that the system marks validation as failed due to invalid relationship and skips email notification.
💻 Technical Criteria
Given Freight forwarder lookup has been performed in the broker name table
When No valid broker-freight forwarder relationship is found
Then The system marks validation as failed due to invalid relationship and skips email notification
R-GCX016E-cbl-03550 Skip Email Notification - Validation Failed
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Skip Email Notification - Validation Failed', assuming that freight forwarder validation has failed due to unauthorized access, invalid relationship, or disposition code not found, when the system processes the validation failure, the desired outcome is that the system bypasses email notification processing and continues with standard disposition code processing.
💻 Technical Criteria
EXCLUDING Freight forwarder validation has failed due to unauthorized access, invalid relationship, or disposition code not found
When The system processes the validation failure
Then The system bypasses email notification processing and continues with standard disposition code processing
R-GCX016E-cbl-03073 Format Disposition Description
Process Rules
📊 Business Logic Narrative
When the process 'Format Disposition Description' is invoked, and assuming that disposition code details have been retrieved, when the system formats disposition information for display, the desired outcome is that disposition description is formatted according to business display standards.
💻 Technical Criteria
Given Disposition code details have been retrieved
When The system formats disposition information for display
Then Disposition description is formatted according to business display standards
R-GCX016E-cbl-03074 Get Processing Date and Time
Action Rules
📊 Business Logic Narrative
When the process 'Get Processing Date and Time' is invoked, and assuming that email content is being created, when the system processes timestamp information, the desired outcome is that current processing date and time are retrieved for email content.
💻 Technical Criteria
Given Email content is being created
When The system processes timestamp information
Then Current processing date and time are retrieved for email content
R-GCX016E-cbl-03076 Create Email Header Section
Process Rules
📊 Business Logic Narrative
When the process 'Create Email Header Section' is invoked, and assuming that email subject line has been constructed, when the system creates the email header section, the desired outcome is that email header section is created with identification and routing information.
💻 Technical Criteria
Given Email subject line has been constructed
When The system creates the email header section
Then Email header section is created with identification and routing information
R-GCX016E-cbl-03080 Add Disposition Information Section
Process Rules
📊 Business Logic Narrative
When the process 'Add Disposition Information Section' is invoked, and assuming that station information section has been added and disposition information is formatted, when the system adds disposition information to email content, the desired outcome is that disposition information section is added with disposition code and description.
💻 Technical Criteria
Given Station information section has been added and disposition information is formatted
When The system adds disposition information to email content
Then Disposition information section is added with disposition code and description
R-GCX016E-cbl-03081 Add Processing Timestamp
Process Rules
📊 Business Logic Narrative
When the process 'Add Processing Timestamp' is invoked, and assuming that disposition information section has been added and processing date/time is available, when the system adds timestamp to email content, the desired outcome is that processing timestamp is added to email content for tracking purposes.
💻 Technical Criteria
Given Disposition information section has been added and processing date/time is available
When The system adds timestamp to email content
Then Processing timestamp is added to email content for tracking purposes
R-GCX016E-cbl-03082 Finalize Email Content
Process Rules
📊 Business Logic Narrative
When the process 'Finalize Email Content' is invoked, and assuming that all email sections have been added including timestamp, when the system finalizes email content, the desired outcome is that email content is finalized with proper formatting and ready for distribution.
💻 Technical Criteria
Given All email sections have been added including timestamp
When The system finalizes email content
Then Email content is finalized with proper formatting and ready for distribution
R-GCX016E-cbl-03083 Email Content Ready for Distribution
Validation Rules
📊 Business Logic Narrative
When the process 'Email Content Ready for Distribution' is invoked, and assuming that email content has been finalized, when the system prepares email for distribution, the desired outcome is that email content is confirmed ready for distribution to appropriate recipients.
💻 Technical Criteria
Given Email content has been finalized
When The system prepares email for distribution
Then Email content is confirmed ready for distribution to appropriate recipients
R-GCX016E-cbl-01230 Attempt Email Delivery
Action Rules
📊 Business Logic Narrative
When the process 'Attempt Email Delivery' is invoked, and assuming that email message is prepared with valid recipients, when the system attempts email delivery, the desired outcome is that the system executes email delivery process and returns delivery status.
💻 Technical Criteria
Given Email message is prepared with valid recipients
When The system attempts email delivery
Then The system executes email delivery process and returns delivery status
R-GCX016E-cbl-01231 Log Successful Delivery
Process Rules
📊 Business Logic Narrative
When the process 'Log Successful Delivery' is invoked, and assuming that email delivery attempt was made, when the delivery is successful, the desired outcome is that the system logs successful delivery and completes the email distribution process.
💻 Technical Criteria
Given Email delivery attempt was made
When The delivery is successful
Then The system logs successful delivery and completes the email distribution process
R-GCX016E-cbl-01233 Retry Limit Reached?
Decision Rules
📊 Business Logic Narrative
When the process 'Retry Limit Reached?' is invoked, and assuming that email delivery has failed and retry counter has been incremented, when the system checks if retry limit is reached, the desired outcome is that the system determines whether to attempt another retry or log delivery failure based on retry limit configuration.
💻 Technical Criteria
Given Email delivery has failed and retry counter has been incremented
When The system checks if retry limit is reached
Then The system determines whether to attempt another retry or log delivery failure based on retry limit configuration
R-GCX016E-cbl-01241 Dump S09A Status Array Contents
Process Rules
📊 Business Logic Narrative
When the process 'Dump S09A Status Array Contents' is invoked, and assuming that s09a status array contains disposition code information, when debug logging is requested for status array processing, the desired outcome is that the system dumps all s09a status array contents including disposition codes, quantities, and sequence information.
💻 Technical Criteria
Given S09A status array contains disposition code information
When Debug logging is requested for status array processing
Then The system dumps all S09A status array contents including disposition codes, quantities, and sequence information
R-GCX016E-cbl-01245 Compare Status Changes
Process Rules
📊 Business Logic Narrative
When the process 'Compare Status Changes' is invoked, and assuming that before and after processing snapshots exist, when debug analysis is performed on status changes, the desired outcome is that the system compares the snapshots and identifies all status changes that occurred.
💻 Technical Criteria
Given Before and after processing snapshots exist
When Debug analysis is performed on status changes
Then The system compares the snapshots and identifies all status changes that occurred
R-GCX016E-cbl-01246 Format Debug Message Content
Process Rules
📊 Business Logic Narrative
When the process 'Format Debug Message Content' is invoked, and assuming that debug information has been captured from status processing, when creating debug output message, the desired outcome is that the system formats all debug information into a structured message format.
💻 Technical Criteria
Given Debug information has been captured from status processing
When Creating debug output message
Then The system formats all debug information into a structured message format
R-GCX016E-cbl-01249 Add Timestamp Information
Process Rules
📊 Business Logic Narrative
When the process 'Add Timestamp Information' is invoked, and assuming that debug logging is being performed, when creating debug log entries, the desired outcome is that the system adds current timestamp information to track when the status processing occurred.
💻 Technical Criteria
Given Debug logging is being performed
When Creating debug log entries
Then The system adds current timestamp information to track when the status processing occurred
R-GCX016E-cbl-01251 Send to Merlin Message Distribution
Action Rules
📊 Business Logic Narrative
When the process 'Send to Merlin Message Distribution' is invoked, and assuming that debug message is ready for distribution, when sending debug message through merlin system, the desired outcome is that the system sends the debug message through merlin message distribution for delivery.
💻 Technical Criteria
Given Debug message is ready for distribution
When Sending debug message through Merlin system
Then The system sends the debug message through Merlin message distribution for delivery
R-GCX016E-cbl-01258 Check AD Segment Configuration
Validation Rules
📊 Business Logic Narrative
When the process 'Check AD Segment Configuration' is invoked, and assuming that a message needs to be distributed, when recipient determination is required, the desired outcome is that the system should check ad segment configuration for valid recipients.
💻 Technical Criteria
Given A message needs to be distributed
When Recipient determination is required
Then The system should check AD segment configuration for valid recipients
R-GCX016E-cbl-01259 Use Configured Recipient
Decision Rules
📊 Business Logic Narrative
When the process 'Use Configured Recipient' is invoked, and assuming that ad segment configuration has been checked, when a valid recipient is found in the configuration, the desired outcome is that the configured recipient should be used for message delivery.
💻 Technical Criteria
Given AD segment configuration has been checked
When A valid recipient is found in the configuration
Then The configured recipient should be used for message delivery
R-GCX016E-cbl-01260 Use Default Recipient OM01247
Decision Rules
📊 Business Logic Narrative
When the process 'Use Default Recipient OM01247' is invoked, and assuming that ad segment configuration has been checked, when no valid recipient is found in the configuration, the desired outcome is that the default recipient om01247 should be used for message delivery.
💻 Technical Criteria
Given AD segment configuration has been checked
When No valid recipient is found in the configuration
Then The default recipient OM01247 should be used for message delivery
R-GCX016E-cbl-01263 Generate Error Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Error Notification' is invoked, and assuming that a message has been sent to a recipient's basket, when the delivery fails, the desired outcome is that an error notification should be generated.
💻 Technical Criteria
Given A message has been sent to a recipient's basket
When The delivery fails
Then An error notification should be generated
R-GCX016E-cbl-03084 AD Segment Available?
Validation Rules
📊 Business Logic Narrative
When the process 'AD Segment Available?' is invoked, and assuming that a message requires recipient determination, when the system evaluates ad segment availability, the desired outcome is that the system identifies whether ad segment configuration exists for recipient lookup.
💻 Technical Criteria
Given A message requires recipient determination
When The system evaluates AD segment availability
Then The system identifies whether AD segment configuration exists for recipient lookup
R-GCX016E-cbl-03085 Read AD Segment Configuration
Action Rules
📊 Business Logic Narrative
When the process 'Read AD Segment Configuration' is invoked, and assuming that ad segment is available for the message, when the system reads the ad segment configuration, the desired outcome is that the system loads the recipient configuration data from the ad segment.
💻 Technical Criteria
Given AD segment is available for the message
When The system reads the AD segment configuration
Then The system loads the recipient configuration data from the AD segment
R-GCX016E-cbl-03086 Extract Recipient Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Recipient Information' is invoked, and assuming that ad segment configuration has been read successfully, when the system processes the configuration data, the desired outcome is that the system extracts recipient identification and routing information.
💻 Technical Criteria
Given AD segment configuration has been read successfully
When The system processes the configuration data
Then The system extracts recipient identification and routing information
R-GCX016E-cbl-03087 Valid Recipient Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid Recipient Found?' is invoked, and assuming that recipient information has been extracted from ad segment, when the system evaluates the extracted recipient data, the desired outcome is that the system determines if a valid recipient identifier exists.
💻 Technical Criteria
Given Recipient information has been extracted from AD segment
When The system evaluates the extracted recipient data
Then The system determines if a valid recipient identifier exists
R-GCX016E-cbl-03089 Validate Recipient Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Recipient Format' is invoked, and assuming that a valid recipient was found in the ad segment configuration, when the system validates the recipient format, the desired outcome is that the system verifies the recipient identifier meets required format standards.
💻 Technical Criteria
Given A valid recipient was found in the AD segment configuration
When The system validates the recipient format
Then The system verifies the recipient identifier meets required format standards
R-GCX016E-cbl-03090 Recipient Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Recipient Valid?' is invoked, and assuming that recipient format validation has been performed, when the system evaluates validation results, the desired outcome is that the system confirms whether the recipient identifier is valid for message routing.
💻 Technical Criteria
Given Recipient format validation has been performed
When The system evaluates validation results
Then The system confirms whether the recipient identifier is valid for message routing
R-GCX016E-cbl-03091 Use Configured Recipient
Action Rules
📊 Business Logic Narrative
When the process 'Use Configured Recipient' is invoked, and assuming that the recipient identifier has passed format validation, when the system finalizes recipient selection, the desired outcome is that the system uses the configured recipient from the ad segment for message delivery.
💻 Technical Criteria
Given The recipient identifier has passed format validation
When The system finalizes recipient selection
Then The system uses the configured recipient from the AD segment for message delivery
R-GCX016E-cbl-03092 Generate Invalid Recipient Error
Action Rules
📊 Business Logic Narrative
When the process 'Generate Invalid Recipient Error' is invoked, and assuming that the recipient identifier failed format validation, when the system processes the validation failure, the desired outcome is that the system generates an invalid recipient error and initiates rerouting logic.
💻 Technical Criteria
Given The recipient identifier failed format validation
When The system processes the validation failure
Then The system generates an invalid recipient error and initiates rerouting logic
R-GCX016E-cbl-03093 Apply Rerouting Logic
Process Rules
📊 Business Logic Narrative
When the process 'Apply Rerouting Logic' is invoked, and assuming that an invalid recipient error has been generated, when the system applies rerouting logic, the desired outcome is that the system redirects the message to alternative routing paths to ensure delivery.
💻 Technical Criteria
Given An invalid recipient error has been generated
When The system applies rerouting logic
Then The system redirects the message to alternative routing paths to ensure delivery
R-GCX016E-cbl-03094 Set Final Message Recipient
Action Rules
📊 Business Logic Narrative
When the process 'Set Final Message Recipient' is invoked, and assuming that either a configured recipient is validated or default recipient is assigned, when the system completes recipient determination process, the desired outcome is that the system sets the final message recipient for delivery routing.
💻 Technical Criteria
Given Either a configured recipient is validated or default recipient is assigned
When The system completes recipient determination process
Then The system sets the final message recipient for delivery routing
R-GCX016E-cbl-01274 Valid Recipient Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid Recipient Found?' is invoked, and assuming that a recipient has been determined for the message, when the system validates the recipient configuration, the desired outcome is that the recipient is confirmed as valid or invalid for delivery.
💻 Technical Criteria
Given A recipient has been determined for the message
When The system validates the recipient configuration
Then The recipient is confirmed as valid or invalid for delivery
R-GCX016E-cbl-01277 Generate Error Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Error Notification' is invoked, and assuming that an invalid recipient was encountered during routing, when the error handling process executes, the desired outcome is that an error notification is generated indicating the recipient validation failure.
💻 Technical Criteria
Given An invalid recipient was encountered during routing
When The error handling process executes
Then An error notification is generated indicating the recipient validation failure
R-GCX016E-cbl-01278 Delivery Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Delivery Successful?' is invoked, and assuming that a message delivery attempt has been made, when the system checks delivery status, the desired outcome is that the delivery is confirmed as successful or failed.
💻 Technical Criteria
Given A message delivery attempt has been made
When The system checks delivery status
Then The delivery is confirmed as successful or failed
R-GCX016E-cbl-01279 Log Successful Delivery
Action Rules
📊 Business Logic Narrative
When the process 'Log Successful Delivery' is invoked, and assuming that a message delivery was successful, when the logging process executes, the desired outcome is that the successful delivery is recorded with timestamp and recipient information.
💻 Technical Criteria
Given A message delivery was successful
When The logging process executes
Then The successful delivery is recorded with timestamp and recipient information
R-GCX016E-cbl-01282 Rerouting Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Rerouting Successful?' is invoked, and assuming that a rerouting delivery attempt has been made, when the system checks rerouting delivery status, the desired outcome is that the rerouting is confirmed as successful or failed.
💻 Technical Criteria
Given A rerouting delivery attempt has been made
When The system checks rerouting delivery status
Then The rerouting is confirmed as successful or failed
R-GCX016E-cbl-01283 Log Rerouting Success
Action Rules
📊 Business Logic Narrative
When the process 'Log Rerouting Success' is invoked, and assuming that a rerouting delivery was successful, when the logging process executes, the desired outcome is that the successful rerouting is recorded with timestamp and alternative recipient information.
💻 Technical Criteria
Given A rerouting delivery was successful
When The logging process executes
Then The successful rerouting is recorded with timestamp and alternative recipient information
R-GCX016E-cbl-01284 Generate Delivery Failure Alert
Action Rules
📊 Business Logic Narrative
When the process 'Generate Delivery Failure Alert' is invoked, and assuming that both primary delivery and rerouting have failed, when the alert generation process executes, the desired outcome is that a delivery failure alert is generated for system administrators.
💻 Technical Criteria
Given Both primary delivery and rerouting have failed
When The alert generation process executes
Then A delivery failure alert is generated for system administrators
R-GCX016E-cbl-01285 Complete Message Distribution
Process Rules
📊 Business Logic Narrative
When the process 'Complete Message Distribution' is invoked, and assuming that all delivery attempts have been completed, when the completion process executes, the desired outcome is that the message distribution process is marked as complete with final status.
💻 Technical Criteria
Given All delivery attempts have been completed
When The completion process executes
Then The message distribution process is marked as complete with final status
R-GCX016E-cbl-01287 Establish MQ Manager Connection
Action Rules
📊 Business Logic Narrative
When the process 'Establish MQ Manager Connection' is invoked, and assuming that mq connection parameters are initialized, when system attempts to connect to mq manager, the desired outcome is that connection to mq manager is established.
💻 Technical Criteria
Given MQ connection parameters are initialized
When System attempts to connect to MQ Manager
Then Connection to MQ Manager is established
R-GCX016E-cbl-01288 Connection Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Connection Successful?' is invoked, and assuming that system has attempted to connect to mq manager, when connection attempt completes, the desired outcome is that system determines if connection was successful or failed.
💻 Technical Criteria
Given System has attempted to connect to MQ Manager
When Connection attempt completes
Then System determines if connection was successful or failed
R-GCX016E-cbl-01291 Set Queue Ready Status
Process Rules
📊 Business Logic Narrative
When the process 'Set Queue Ready Status' is invoked, and assuming that mq manager connection is established and gc350.exp.input queue is successfully opened, when both connection and queue opening are validated as successful, the desired outcome is that queue status is set to ready for message processing.
💻 Technical Criteria
Given MQ Manager connection is established AND GC350.EXP.INPUT queue is successfully opened
When Both connection and queue opening are validated as successful
Then Queue status is set to ready for message processing
R-GCX016E-cbl-01292 Log Connection Success
Process Rules
📊 Business Logic Narrative
When the process 'Log Connection Success' is invoked, and assuming that queue status has been set to ready, when mq connection setup is complete, the desired outcome is that connection success is logged to system audit trail.
💻 Technical Criteria
Given Queue status has been set to ready
When MQ connection setup is complete
Then Connection success is logged to system audit trail
R-GCX016E-cbl-01293 Handle Connection Error
Action Rules
📊 Business Logic Narrative
When the process 'Handle Connection Error' is invoked, and assuming that system attempted to connect to mq manager, when mq manager connection fails, the desired outcome is that connection error is handled and appropriate error processing is initiated.
💻 Technical Criteria
Given System attempted to connect to MQ Manager
When MQ Manager connection fails
Then Connection error is handled and appropriate error processing is initiated
R-GCX016E-cbl-01294 Log Connection Failure
Process Rules
📊 Business Logic Narrative
When the process 'Log Connection Failure' is invoked, and assuming that mq manager connection has failed, when connection error handling is processed, the desired outcome is that connection failure details are logged to system audit trail.
💻 Technical Criteria
Given MQ Manager connection has failed
When Connection error handling is processed
Then Connection failure details are logged to system audit trail
R-GCX016E-cbl-01295 Handle Queue Open Error
Action Rules
📊 Business Logic Narrative
When the process 'Handle Queue Open Error' is invoked, and assuming that mq manager connection is successful and system attempted to open gc350.exp.input queue, when queue opening fails, the desired outcome is that queue opening error is handled and appropriate error processing is initiated.
💻 Technical Criteria
Given MQ Manager connection is successful AND system attempted to open GC350.EXP.INPUT queue
When Queue opening fails
Then Queue opening error is handled and appropriate error processing is initiated
R-GCX016E-cbl-01298 Connection Failed - Exit
Process Rules
📊 Business Logic Narrative
When the process 'Connection Failed - Exit' is invoked, and assuming that either connection failure or queue opening failure has been logged, when error handling is complete, the desired outcome is that mq connection management process exits without establishing ready status.
💻 Technical Criteria
Given Either connection failure OR queue opening failure has been logged
When Error handling is complete
Then MQ connection management process exits without establishing ready status
R-GCX016E-cbl-01304 Set Date/Time Information
Process Rules
📊 Business Logic Narrative
When the process 'Set Date/Time Information' is invoked, and assuming that disposition code data has been set in the x4 segment, when the system sets date/time information, the desired outcome is that the system assigns current date, time, and timezone information to the x4 segment.
💻 Technical Criteria
Given Disposition code data has been set in the X4 segment
When The system sets date/time information
Then The system assigns current date, time, and timezone information to the X4 segment
R-GCX016E-cbl-01311 Set Vessel/Train Information
Process Rules
📊 Business Logic Narrative
When the process 'Set Vessel/Train Information' is invoked, and assuming that m10 segment structure has been created, when the system sets vessel/train information, the desired outcome is that the system assigns vessel name, train number, and train identification data to the m10 segment.
💻 Technical Criteria
Given M10 segment structure has been created
When The system sets vessel/train information
Then The system assigns vessel name, train number, and train identification data to the M10 segment
R-GCX016E-cbl-01315 Set Event Information
Process Rules
📊 Business Logic Narrative
When the process 'Set Event Information' is invoked, and assuming that v9 segment structure has been created, when the system sets event information, the desired outcome is that the system assigns event code, event date, event time, and event description to the v9 segment.
💻 Technical Criteria
Given V9 segment structure has been created
When The system sets event information
Then The system assigns event code, event date, event time, and event description to the V9 segment
R-GCX016E-cbl-01316 Set Disposition Code
Process Rules
📊 Business Logic Narrative
When the process 'Set Disposition Code' is invoked, and assuming that event information has been set in the v9 segment, when the system sets disposition code, the desired outcome is that the system populates disposition code and related processing flags in the v9 segment.
💻 Technical Criteria
Given Event information has been set in the V9 segment
When The system sets disposition code
Then The system populates disposition code and related processing flags in the V9 segment
R-GCX016E-cbl-01319 All Required Fields Set?
Validation Rules
📊 Business Logic Narrative
When the process 'All Required Fields Set?' is invoked, and assuming that segment completeness validation has been performed, when the system checks if all required fields are set, the desired outcome is that the system returns true if all mandatory fields contain valid data, otherwise returns false.
💻 Technical Criteria
Given Segment completeness validation has been performed
When The system checks if all required fields are set
Then The system returns true if all mandatory fields contain valid data, otherwise returns false
R-GCX016E-cbl-01320 Mark Arrays Ready for Processing
Process Rules
📊 Business Logic Narrative
When the process 'Mark Arrays Ready for Processing' is invoked, and assuming that all required fields validation check returns true, when the system marks arrays ready for processing, the desired outcome is that the system sets the ready status flag and makes the arrays available for message processing.
💻 Technical Criteria
Given All required fields validation check returns true
When The system marks arrays ready for processing
Then The system sets the ready status flag and makes the arrays available for message processing
R-GCX016E-cbl-01321 Log Initialization Error
Process Rules
📊 Business Logic Narrative
When the process 'Log Initialization Error' is invoked, and assuming that all required fields validation check returns false, when the system logs initialization error, the desired outcome is that the system records error details including missing fields and sets error status for the initialization process.
💻 Technical Criteria
Given All required fields validation check returns false
When The system logs initialization error
Then The system records error details including missing fields and sets error status for the initialization process
R-GCX016E-cbl-01325 Capture Timestamp Information
Validation Rules
📊 Business Logic Narrative
When the process 'Capture Timestamp Information' is invoked, and assuming that an audit log entry is being created, when the system captures audit information, the desired outcome is that the current timestamp should be recorded in the log entry.
💻 Technical Criteria
Given An audit log entry is being created
When The system captures audit information
Then The current timestamp should be recorded in the log entry
R-GCX016E-cbl-01326 Capture User Information
Validation Rules
📊 Business Logic Narrative
When the process 'Capture User Information' is invoked, and assuming that an audit log entry is being created, when the system captures audit information, the desired outcome is that the user identification information should be recorded in the log entry.
💻 Technical Criteria
Given An audit log entry is being created
When The system captures audit information
Then The user identification information should be recorded in the log entry
R-GCX016E-cbl-01328 Spawn GCT1051E Transaction
Action Rules
📊 Business Logic Narrative
When the process 'Spawn GCT1051E Transaction' is invoked, and assuming that all audit log information has been prepared, when the system is ready to create the log entry, the desired outcome is that the gct1051e transaction should be spawned to create the audit log.
💻 Technical Criteria
Given All audit log information has been prepared
When The system is ready to create the log entry
Then The GCT1051E transaction should be spawned to create the audit log
R-GCX016E-cbl-01329 Transaction Spawn Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'Transaction Spawn Successful?' is invoked, and assuming that the gct1051e transaction has been spawned for audit logging, when the system checks the transaction spawn result, the desired outcome is that the system should determine if the spawn was successful or failed.
💻 Technical Criteria
Given The GCT1051E transaction has been spawned for audit logging
When The system checks the transaction spawn result
Then The system should determine if the spawn was successful or failed
R-GCX016E-cbl-01330 Log Entry Created Successfully
Process Rules
📊 Business Logic Narrative
When the process 'Log Entry Created Successfully' is invoked, and assuming that the gct1051e transaction spawn was successful, when the system processes the successful spawn result, the desired outcome is that the system should confirm the log entry was created successfully.
💻 Technical Criteria
Given The GCT1051E transaction spawn was successful
When The system processes the successful spawn result
Then The system should confirm the log entry was created successfully
R-GCX016E-cbl-01338 Retrieve Disposition Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Retrieve Disposition Code' is invoked, and assuming that a disposition code is being processed, when disposition code retrieval is performed, the desired outcome is that the current disposition code is retrieved for formatting.
💻 Technical Criteria
Given A disposition code is being processed
When Disposition code retrieval is performed
Then The current disposition code is retrieved for formatting
R-GCX016E-cbl-01339 Retrieve Disposition Description
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Disposition Description' is invoked, and assuming that a disposition code exists and disposition code table is available, when disposition description lookup is performed, the desired outcome is that the corresponding description is retrieved from the disposition code table.
💻 Technical Criteria
Given A disposition code exists and disposition code table is available
When Disposition description lookup is performed
Then The corresponding description is retrieved from the disposition code table
R-GCX016E-cbl-01343 Apply Release Quantity Impact Logic
Decision Rules
📊 Business Logic Narrative
When the process 'Apply Release Quantity Impact Logic' is invoked, and assuming that a disposition code is being processed, when release quantity impact logic is applied, the desired outcome is that the system determines whether the disposition code affects release quantities.
💻 Technical Criteria
Given A disposition code is being processed
When Release quantity impact logic is applied
Then The system determines whether the disposition code affects release quantities
R-GCX016E-cbl-01344 Should Disposition Code Affect Release Quantities?
Decision Rules
📊 Business Logic Narrative
When the process 'Should Disposition Code Affect Release Quantities?' is invoked, and assuming that a disposition code is being evaluated for quantity impact, when the system checks if the disposition code affects release quantities, the desired outcome is that the system returns yes if the code affects quantities, no if it does not.
💻 Technical Criteria
Given A disposition code is being evaluated for quantity impact
When The system checks if the disposition code affects release quantities
Then The system returns yes if the code affects quantities, no if it does not
R-GCX016E-cbl-01351 Lookup Disposition Code in DC Table
Validation Rules
📊 Business Logic Narrative
When the process 'Lookup Disposition Code in DC Table' is invoked, and assuming that a disposition code needs to be processed, when the system looks up the disposition code in the dc table, the desired outcome is that the disposition code details and action type are retrieved if found.
💻 Technical Criteria
Given A disposition code needs to be processed
When The system looks up the disposition code in the DC table
Then The disposition code details and action type are retrieved if found
R-GCX016E-cbl-01352 Disposition Code Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Disposition Code Found?' is invoked, and assuming that a disposition code is being processed for quantity impact, when the system checks if the disposition code exists in the dc table, the desired outcome is that processing continues if found, otherwise an error is generated.
💻 Technical Criteria
Given A disposition code is being processed for quantity impact
When The system checks if the disposition code exists in the DC table
Then Processing continues if found, otherwise an error is generated
R-GCX016E-cbl-01353 Retrieve Disposition Code Action Type
Definitional Rules
📊 Business Logic Narrative
When the process 'Retrieve Disposition Code Action Type' is invoked, and assuming that a valid disposition code exists in the dc table, when the system retrieves the disposition code configuration, the desired outcome is that the action type (add, subtract, or status info) is determined for quantity processing.
💻 Technical Criteria
Given A valid disposition code exists in the DC table
When The system retrieves the disposition code configuration
Then The action type (Add, Subtract, or Status Info) is determined for quantity processing
R-GCX016E-cbl-01355 Add to Release Quantity
Computation Rules
📊 Business Logic Narrative
When the process 'Add to Release Quantity' is invoked, and assuming that a disposition code has an 'add' action type, when the system processes the quantity impact, the desired outcome is that the disposition code quantity is added to the current release quantity.
💻 Technical Criteria
Given A disposition code has an 'Add' action type
When The system processes the quantity impact
Then The disposition code quantity is added to the current release quantity
R-GCX016E-cbl-01356 Subtract from Release Quantity
Computation Rules
📊 Business Logic Narrative
When the process 'Subtract from Release Quantity' is invoked, and assuming that a disposition code has a 'subtract' action type, when the system processes the quantity impact, the desired outcome is that the disposition code quantity is subtracted from the current release quantity.
💻 Technical Criteria
Given A disposition code has a 'Subtract' action type
When The system processes the quantity impact
Then The disposition code quantity is subtracted from the current release quantity
R-GCX016E-cbl-01357 No Quantity Impact
Decision Rules
📊 Business Logic Narrative
When the process 'No Quantity Impact' is invoked, and assuming that a disposition code has 'status info' action type, when the system processes the disposition code, the desired outcome is that no quantity calculations are performed and processing continues to set impact flag.
💻 Technical Criteria
Given A disposition code has 'Status Info' action type
When The system processes the disposition code
Then No quantity calculations are performed and processing continues to set impact flag
R-GCX016E-cbl-01359 Quantity Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Quantity Valid?' is invoked, and assuming that a release quantity has been calculated and validated, when the system checks if the quantity is valid, the desired outcome is that processing continues to update if valid, otherwise an error is generated.
💻 Technical Criteria
Given A release quantity has been calculated and validated
When The system checks if the quantity is valid
Then Processing continues to update if valid, otherwise an error is generated
R-GCX016E-cbl-01362 Log Before/After Comparison
Action Rules
📊 Business Logic Narrative
When the process 'Log Before/After Comparison' is invoked, and assuming that a quantity impact has been processed and messaged, when the system logs the quantity change, the desired outcome is that the original quantity, new quantity, and disposition code are recorded in the system log.
💻 Technical Criteria
Given A quantity impact has been processed and messaged
When The system logs the quantity change
Then The original quantity, new quantity, and disposition code are recorded in the system log
R-GCX016E-cbl-01363 Set Quantity Impact Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Quantity Impact Flag' is invoked, and assuming that disposition code processing has been completed, when the system finalizes quantity impact processing, the desired outcome is that a quantity impact flag is set to indicate whether quantities were affected by the disposition code.
💻 Technical Criteria
Given Disposition code processing has been completed
When The system finalizes quantity impact processing
Then A quantity impact flag is set to indicate whether quantities were affected by the disposition code
R-GCX016E-cbl-01364 Generate Error Message
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error Message', assuming that a disposition code is not found in dc table or calculated quantity is invalid, when the system encounters a validation error, the desired outcome is that an error message is generated indicating the specific validation failure.
💻 Technical Criteria
EXCLUDING A disposition code is not found in DC table OR calculated quantity is invalid
When The system encounters a validation error
Then An error message is generated indicating the specific validation failure
R-GCX016E-cbl-01366 Set Error Flag for Invalid Date
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Error Flag for Invalid Date', assuming that a date input has been provided for age calculation, when the date format validation fails or date is invalid, the desired outcome is that the system sets an error flag to indicate date processing failure.
💻 Technical Criteria
EXCLUDING A date input has been provided for age calculation
When The date format validation fails or date is invalid
Then The system sets an error flag to indicate date processing failure
R-GCX016E-cbl-01368 Convert Date to Julian Format
Computation Rules
📊 Business Logic Narrative
When the process 'Convert Date to Julian Format' is invoked, and assuming that a valid date has been confirmed through validation, when the system needs to perform age calculations, the desired outcome is that the system converts the date to julian format using standard conversion algorithms.
💻 Technical Criteria
Given A valid date has been confirmed through validation
When The system needs to perform age calculations
Then The system converts the date to Julian format using standard conversion algorithms
R-GCX016E-cbl-01374 Query SHIPROOT Database
Validation Rules
📊 Business Logic Narrative
When the process 'Query SHIPROOT Database' is invoked, and assuming that a shipment identifier has been extracted from an edi message, when the system queries the shiproot database for the shipment identifier, the desired outcome is that the system should retrieve the shipment root record if it exists.
💻 Technical Criteria
Given A shipment identifier has been extracted from an EDI message
When The system queries the SHIPROOT database for the shipment identifier
Then The system should retrieve the shipment root record if it exists
R-GCX016E-cbl-01375 Shipment Root Record Exists?
Decision Rules
📊 Business Logic Narrative
When the process 'Shipment Root Record Exists?' is invoked, and assuming that the system has queried the shiproot database for a shipment identifier, when the query result indicates whether a shipment root record exists or not, the desired outcome is that the system should set validation successful flag if record exists, otherwise set error flag.
💻 Technical Criteria
Given The system has queried the SHIPROOT database for a shipment identifier
When The query result indicates whether a shipment root record exists or not
Then The system should set validation successful flag if record exists, otherwise set error flag
R-GCX016E-cbl-01376 Log Validation Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Validation Error', assuming that a shipment root record does not exist in the shiproot database, when the validation check fails, the desired outcome is that the system should log a validation error indicating the missing shipment root record.
💻 Technical Criteria
EXCLUDING A shipment root record does not exist in the SHIPROOT database
When The validation check fails
Then The system should log a validation error indicating the missing shipment root record
R-GCX016E-cbl-01377 Set Error Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Error Flag' is invoked, and assuming that a validation error has been logged for a missing shipment root record, when the shipment root validation process completes with failure, the desired outcome is that the system should set an error flag to indicate validation failure.
💻 Technical Criteria
Given A validation error has been logged for a missing shipment root record
When The shipment root validation process completes with failure
Then The system should set an error flag to indicate validation failure
R-GCX016E-cbl-01378 Continue EDI Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue EDI Processing' is invoked, and assuming that a shipment root record exists in the shiproot database, when the validation is successful, the desired outcome is that the system should continue with normal edi processing workflow.
💻 Technical Criteria
Given A shipment root record exists in the SHIPROOT database
When The validation is successful
Then The system should continue with normal EDI processing workflow
R-GCX016E-cbl-01379 Skip EDI Processing
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Skip EDI Processing', assuming that a shipment root record does not exist and error flag has been set, when the validation process completes with failure, the desired outcome is that the system should skip the edi processing for this shipment.
💻 Technical Criteria
EXCLUDING A shipment root record does not exist and error flag has been set
When The validation process completes with failure
Then The system should skip the EDI processing for this shipment
R-GCX016E-cbl-01380 Validate Shiproot Record Exists
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Shiproot Record Exists' is invoked, and assuming that a shipment requires minimum information processing, when the system attempts to validate the shiproot record existence, the desired outcome is that the system should verify the shiproot record exists in the database.
💻 Technical Criteria
Given A shipment requires minimum information processing
When The system attempts to validate the shiproot record existence
Then The system should verify the shiproot record exists in the database
R-GCX016E-cbl-01381 Generate Error - Shiproot Not Found
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error - Shiproot Not Found', assuming that a shipment requires minimum information processing, when the shiproot record is not found in the database, the desired outcome is that the system should generate an error indicating shiproot not found and terminate processing.
💻 Technical Criteria
EXCLUDING A shipment requires minimum information processing
When The shiproot record is not found in the database
Then The system should generate an error indicating shiproot not found and terminate processing
R-GCX016E-cbl-01387 Create U1 Shipment Minimum Segment
Action Rules
📊 Business Logic Narrative
When the process 'Create U1 Shipment Minimum Segment' is invoked, and assuming that all required shipment data including station information has been processed, when the system creates the u1 segment, the desired outcome is that the system should initialize a new u1 shipment minimum segment with proper structure.
💻 Technical Criteria
Given All required shipment data including station information has been processed
When The system creates the U1 segment
Then The system should initialize a new U1 shipment minimum segment with proper structure
R-GCX016E-cbl-01392 Store U1 Segment for EDI Processing
Action Rules
📊 Business Logic Narrative
When the process 'Store U1 Segment for EDI Processing' is invoked, and assuming that the u1 segment has been validated and all data is correct, when the system stores the u1 segment, the desired outcome is that the system should save the u1 segment to the shipminu database for edi processing.
💻 Technical Criteria
Given The U1 segment has been validated and all data is correct
When The system stores the U1 segment
Then The system should save the U1 segment to the SHIPMINU database for EDI processing
R-GCX016E-cbl-01393 Log Shipment Processing Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Shipment Processing Action' is invoked, and assuming that the u1 segment has been successfully stored for edi processing, when the system completes shipment processing, the desired outcome is that the system should create a log entry documenting the successful completion of shipment minimum information processing.
💻 Technical Criteria
Given The U1 segment has been successfully stored for EDI processing
When The system completes shipment processing
Then The system should create a log entry documenting the successful completion of shipment minimum information processing
R-GCX016E-cbl-01413 Key Station Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Key Station Found?' is invoked, and assuming that gcctbio has completed the key station table lookup, when the system evaluates the lookup results, the desired outcome is that the system proceeds with data loading if station found or generates error if not found.
💻 Technical Criteria
Given GCCTBIO has completed the key station table lookup
When The system evaluates the lookup results
Then The system proceeds with data loading if station found or generates error if not found
R-GCX016E-cbl-01414 Load Key Station Data
Process Rules
📊 Business Logic Narrative
When the process 'Load Key Station Data' is invoked, and assuming that key station information has been successfully retrieved from the ks table, when the system loads the station data, the desired outcome is that key station data is available in working storage for validation and field setting.
💻 Technical Criteria
Given Key station information has been successfully retrieved from the KS table
When The system loads the station data
Then Key station data is available in working storage for validation and field setting
R-GCX016E-cbl-01415 Validate Station Information
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Station Information' is invoked, and assuming that key station data has been loaded into working storage, when the system validates the station information, the desired outcome is that the station data is confirmed as valid or invalid based on business rules.
💻 Technical Criteria
Given Key station data has been loaded into working storage
When The system validates the station information
Then The station data is confirmed as valid or invalid based on business rules
R-GCX016E-cbl-01416 Station Data Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Station Data Valid?' is invoked, and assuming that station information has undergone validation checks, when the system evaluates the validation results, the desired outcome is that the system proceeds with field setting if valid or generates error message if invalid.
💻 Technical Criteria
Given Station information has undergone validation checks
When The system evaluates the validation results
Then The system proceeds with field setting if valid or generates error message if invalid
R-GCX016E-cbl-01417 Set Key Station Fields
Process Rules
📊 Business Logic Narrative
When the process 'Set Key Station Fields' is invoked, and assuming that valid key station data is available in working storage, when the system sets key station fields, the desired outcome is that key station fields are populated with validated station information.
💻 Technical Criteria
Given Valid key station data is available in working storage
When The system sets key station fields
Then Key station fields are populated with validated station information
R-GCX016E-cbl-01420 Generate Error Message for Station Not Found
Process Rules
📊 Business Logic Narrative
When the process 'Generate Error Message for Station Not Found' is invoked, and assuming that key station lookup has failed to find matching station data, when the system generates an error message, the desired outcome is that an error message is created indicating station not found.
💻 Technical Criteria
Given Key station lookup has failed to find matching station data
When The system generates an error message
Then An error message is created indicating station not found
R-GCX016E-cbl-01431 Store Reference Data in Working Storage
Process Rules
📊 Business Logic Narrative
When the process 'Store Reference Data in Working Storage' is invoked, and assuming that reference information has been formatted, when the system stores the reference data, the desired outcome is that formatted reference information is stored in working storage n9 arrays.
💻 Technical Criteria
Given Reference information has been formatted
When The system stores the reference data
Then Formatted reference information is stored in working storage N9 arrays
R-GCX016E-cbl-01433 End N9 Reference Retrieval
Process Rules
📊 Business Logic Narrative
When the process 'End N9 Reference Retrieval' is invoked, and assuming that all n9 reference processing has been completed or no n9 segments were available, when the system reaches the end of the n9 reference retrieval process, the desired outcome is that the n9 reference information retrieval process is completed.
💻 Technical Criteria
Given All N9 reference processing has been completed OR no N9 segments were available
When The system reaches the end of the N9 reference retrieval process
Then The N9 reference information retrieval process is completed
R-GCX016E-cbl-01450 Include Disposition Codes
Process Rules
📊 Business Logic Narrative
When the process 'Include Disposition Codes' is invoked, and assuming that a special action message is being prepared for follower manifest processing, when the system builds the transaction message content, the desired outcome is that all relevant disposition codes from the original transaction are included in the follower manifest message.
💻 Technical Criteria
Given A special action message is being prepared for follower manifest processing
When The system builds the transaction message content
Then All relevant disposition codes from the original transaction are included in the follower manifest message
R-GCX016E-cbl-01451 Include Quantities
Process Rules
📊 Business Logic Narrative
When the process 'Include Quantities' is invoked, and assuming that disposition codes have been included in the follower manifest message, when the system continues building the transaction message, the desired outcome is that all relevant quantity information from the original transaction is included in the follower manifest message.
💻 Technical Criteria
Given Disposition codes have been included in the follower manifest message
When The system continues building the transaction message
Then All relevant quantity information from the original transaction is included in the follower manifest message
R-GCX016E-cbl-01452 Include Entry Numbers
Process Rules
📊 Business Logic Narrative
When the process 'Include Entry Numbers' is invoked, and assuming that quantities have been included in the follower manifest message, when the system completes building the transaction message, the desired outcome is that all relevant entry numbers from the original transaction are included in the follower manifest message.
💻 Technical Criteria
Given Quantities have been included in the follower manifest message
When The system completes building the transaction message
Then All relevant entry numbers from the original transaction are included in the follower manifest message
R-GCX016E-cbl-01453 Spawn GCT0162E Transaction
Action Rules
📊 Business Logic Narrative
When the process 'Spawn GCT0162E Transaction' is invoked, and assuming that a complete follower manifest message has been prepared with all required information, when the system is ready to process the follower manifest, the desired outcome is that a gct0162e transaction is spawned with the prepared message for follower manifest processing.
💻 Technical Criteria
Given A complete follower manifest message has been prepared with all required information
When The system is ready to process the follower manifest
Then A GCT0162E transaction is spawned with the prepared message for follower manifest processing
R-GCX016E-cbl-01454 Set Follower Manifest Processing Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Follower Manifest Processing Flag' is invoked, and assuming that a gct0162e transaction has been successfully spawned for follower manifest processing, when the system updates processing status, the desired outcome is that follower manifest processing flags are set to indicate the current processing state.
💻 Technical Criteria
Given A GCT0162E transaction has been successfully spawned for follower manifest processing
When The system updates processing status
Then Follower manifest processing flags are set to indicate the current processing state
R-GCX016E-cbl-01455 Continue with Next Manifest
Process Rules
📊 Business Logic Narrative
When the process 'Continue with Next Manifest' is invoked, and assuming that follower manifest processing flags have been set for the current manifest, when the system is ready to process additional manifests, the desired outcome is that processing continues with the next manifest in the sequence.
💻 Technical Criteria
Given Follower manifest processing flags have been set for the current manifest
When The system is ready to process additional manifests
Then Processing continues with the next manifest in the sequence
R-GCX016E-cbl-01456 More Follower Manifests?
Decision Rules
📊 Business Logic Narrative
When the process 'More Follower Manifests?' is invoked, and assuming that the current follower manifest has been processed, when the system checks for additional manifests in the sequence, the desired outcome is that if more follower manifests exist, processing continues; otherwise, transaction spawning is completed.
💻 Technical Criteria
Given The current follower manifest has been processed
When The system checks for additional manifests in the sequence
Then If more follower manifests exist, processing continues; otherwise, transaction spawning is completed
R-GCX016E-cbl-01457 Complete Transaction Spawning
Process Rules
📊 Business Logic Narrative
When the process 'Complete Transaction Spawning' is invoked, and assuming that all follower manifests have been processed or no follower manifests were required, when the transaction spawning process reaches completion, the desired outcome is that the transaction spawning process is marked as complete and control returns to the main processing flow.
💻 Technical Criteria
Given All follower manifests have been processed or no follower manifests were required
When The transaction spawning process reaches completion
Then The transaction spawning process is marked as complete and control returns to the main processing flow
R-GCX016E-cbl-01459 MQ Message Error
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'MQ Message Error', assuming that a message is being processed from the message queue, when mq completion code is not ok or reason code indicates message unavailable (2033) or backout count is not zero, the desired outcome is that set appropriate message status flags (message not available or skip message) and generate error notification to merlin system.
💻 Technical Criteria
EXCLUDING A message is being processed from the message queue
When MQ completion code is not OK or reason code indicates message unavailable (2033) or backout count is not zero
Then Set appropriate message status flags (message not available or skip message) and generate error notification to Merlin system
R-GCX016E-cbl-01460 Database I/O Error
Action Rules
📊 Business Logic Narrative
When the process 'Database I/O Error' is invoked, and assuming that a database read, write, or update operation is being performed, when database operation returns an error status code, the desired outcome is that log error information, generate merlin error message, and either continue processing or abend based on error severity.
💻 Technical Criteria
Given A database read, write, or update operation is being performed
When Database operation returns an error status code
Then Log error information, generate Merlin error message, and either continue processing or abend based on error severity
R-GCX016E-cbl-01462 Train Not Found Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Train Not Found Error', assuming that m10 segment contains vessel name that does not start with 'train' or 'day', when train lookup in train list fails to find matching train record, the desired outcome is that generate train not found error message to merlin system and continue processing remaining segments.
💻 Technical Criteria
EXCLUDING M10 segment contains vessel name that does not start with 'TRAIN' or 'DAY'
When Train lookup in train list fails to find matching train record
Then Generate train not found error message to Merlin system and continue processing remaining segments
R-GCX016E-cbl-01464 Invalid Disposition Code Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Invalid Disposition Code Error', assuming that x4 segment contains disposition code information, when disposition code lookup in dc table fails or returns invalid status, the desired outcome is that generate invalid disposition code error message, log the invalid code, and skip processing for that specific disposition code.
💻 Technical Criteria
EXCLUDING X4 segment contains disposition code information
When Disposition code lookup in DC table fails or returns invalid status
Then Generate invalid disposition code error message, log the invalid code, and skip processing for that specific disposition code
R-GCX016E-cbl-01466 Log Error Information
Process Rules
📊 Business Logic Narrative
When the process 'Log Error Information' is invoked, and assuming that an error has occurred during message processing, when error logging is required for audit trail, the desired outcome is that log error details including message id, segment information, error type, and relevant business data for debugging purposes.
💻 Technical Criteria
Given An error has occurred during message processing
When Error logging is required for audit trail
Then Log error details including message ID, segment information, error type, and relevant business data for debugging purposes
R-GCX016E-cbl-01467 Set Error Flags
Process Rules
📊 Business Logic Narrative
When the process 'Set Error Flags' is invoked, and assuming that an error condition has been identified and logged, when processing flow needs to be controlled based on error status, the desired outcome is that set appropriate error flags to indicate error type and severity for downstream processing decisions.
💻 Technical Criteria
Given An error condition has been identified and logged
When Processing flow needs to be controlled based on error status
Then Set appropriate error flags to indicate error type and severity for downstream processing decisions
R-GCX016E-cbl-01472 Update Processing Status
Process Rules
📊 Business Logic Narrative
When the process 'Update Processing Status' is invoked, and assuming that error handling has been completed for a specific error condition, when processing status needs to reflect the current state after error handling, the desired outcome is that update processing status flags and counters to indicate error resolution and readiness for continued processing.
💻 Technical Criteria
Given Error handling has been completed for a specific error condition
When Processing status needs to reflect the current state after error handling
Then Update processing status flags and counters to indicate error resolution and readiness for continued processing
R-GCX016E-cbl-01473 Extract Train ID from Vessel Name
Process Rules
📊 Business Logic Narrative
When the process 'Extract Train ID from Vessel Name' is invoked, and assuming that an m10 vessel name segment is received, when the system processes the vessel name field, the desired outcome is that the train id is extracted from the vessel name for validation.
💻 Technical Criteria
Given An M10 vessel name segment is received
When The system processes the vessel name field
Then The train ID is extracted from the vessel name for validation
R-GCX016E-cbl-01474 Train ID Present?
Validation Rules
📊 Business Logic Narrative
When the process 'Train ID Present?' is invoked, and assuming that a vessel name has been processed for train id extraction, when the system checks if a valid train id was extracted, the desired outcome is that if train id is present, proceed to train lookup; if not present, generate train not found error.
💻 Technical Criteria
Given A vessel name has been processed for train ID extraction
When The system checks if a valid train ID was extracted
Then If train ID is present, proceed to train lookup; if not present, generate train not found error
R-GCX016E-cbl-01475 Call GCCUTRIO to Lookup Train in System
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCUTRIO to Lookup Train in System' is invoked, and assuming that a valid train id has been extracted from the vessel name, when the system needs to validate the train exists in the system, the desired outcome is that call gccutrio program to lookup train data from gcwtl train list segments.
💻 Technical Criteria
Given A valid train ID has been extracted from the vessel name
When The system needs to validate the train exists in the system
Then Call GCCUTRIO program to lookup train data from GCWTL train list segments
R-GCX016E-cbl-01476 Train Found in System?
Validation Rules
📊 Business Logic Narrative
When the process 'Train Found in System?' is invoked, and assuming that gccutrio has been called to lookup train information, when the system evaluates the lookup results, the desired outcome is that if train is found, proceed to validate train record status; if not found, generate train not found error.
💻 Technical Criteria
Given GCCUTRIO has been called to lookup train information
When The system evaluates the lookup results
Then If train is found, proceed to validate train record status; if not found, generate train not found error
R-GCX016E-cbl-01477 Validate Train Record Status
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Train Record Status' is invoked, and assuming that a train record has been found in the system, when the system validates the train record status, the desired outcome is that check if the train is a cprs train for special processing requirements.
💻 Technical Criteria
Given A train record has been found in the system
When The system validates the train record status
Then Check if the train is a CPRS train for special processing requirements
R-GCX016E-cbl-01478 CPRS Train?
Decision Rules
📊 Business Logic Narrative
When the process 'CPRS Train?' is invoked, and assuming that a train record has been validated and found in the system, when the system checks the train type, the desired outcome is that if train is cprs type, apply cprs special processing rules; otherwise set train found flag.
💻 Technical Criteria
Given A train record has been validated and found in the system
When The system checks the train type
Then If train is CPRS type, apply CPRS special processing rules; otherwise set train found flag
R-GCX016E-cbl-01480 Set Train Found Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Train Found Flag' is invoked, and assuming that a train has been successfully validated (either regular or cprs), when the system completes train validation processing, the desired outcome is that set train found flag to true and continue with train processing.
💻 Technical Criteria
Given A train has been successfully validated (either regular or CPRS)
When The system completes train validation processing
Then Set train found flag to true and continue with train processing
R-GCX016E-cbl-01481 Generate Train Not Found Error Message
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Train Not Found Error Message', assuming that train id is not present in vessel name or train is not found in system lookup, when the system encounters train validation failure, the desired outcome is that generate a train not found error message for merlin system notification.
💻 Technical Criteria
EXCLUDING Train ID is not present in vessel name OR train is not found in system lookup
When The system encounters train validation failure
Then Generate a train not found error message for Merlin system notification
R-GCX016E-cbl-01482 Send Error to Merlin System
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Send Error to Merlin System', assuming that a train not found error message has been generated, when the system needs to notify about the validation failure, the desired outcome is that send the error message to merlin system for appropriate notification handling.
💻 Technical Criteria
EXCLUDING A train not found error message has been generated
When The system needs to notify about the validation failure
Then Send the error message to Merlin system for appropriate notification handling
R-GCX016E-cbl-01483 Set Train Processing Flag to Skip
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Train Processing Flag to Skip', assuming that an error message has been sent to merlin system for train not found, when the system needs to prevent further processing of invalid train, the desired outcome is that set train processing flag to skip to bypass subsequent train-related operations.
💻 Technical Criteria
EXCLUDING An error message has been sent to Merlin system for train not found
When The system needs to prevent further processing of invalid train
Then Set train processing flag to skip to bypass subsequent train-related operations
R-GCX016E-cbl-01484 Continue with Train Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue with Train Processing' is invoked, and assuming that train found flag has been set after successful validation, when the system is ready to proceed with train operations, the desired outcome is that continue with normal train processing workflow and log validation results.
💻 Technical Criteria
Given Train found flag has been set after successful validation
When The system is ready to proceed with train operations
Then Continue with normal train processing workflow and log validation results
R-GCX016E-cbl-01485 Log Train Validation Results
Process Rules
📊 Business Logic Narrative
When the process 'Log Train Validation Results' is invoked, and assuming that train validation processing has completed (either successful or failed), when the system needs to record validation results, the desired outcome is that log the train validation results including success/failure status and any relevant details.
💻 Technical Criteria
Given Train validation processing has completed (either successful or failed)
When The system needs to record validation results
Then Log the train validation results including success/failure status and any relevant details
R-GCX016E-cbl-01522 Disposition Code = SEI?
Decision Rules
📊 Business Logic Narrative
When the process 'Disposition Code = SEI?' is invoked, and assuming that a vid segment has been processed and disposition code is available, when the system checks the disposition code, the desired outcome is that if disposition code equals sei, proceed with seizure processing, otherwise complete processing without seizure.
💻 Technical Criteria
Given A VID segment has been processed and disposition code is available
When The system checks the disposition code
Then If disposition code equals SEI, proceed with seizure processing, otherwise complete processing without seizure
R-GCX016E-cbl-01588 Process HMI - Hold Train
Action Rules
📊 Business Logic Narrative
When the process 'Process HMI - Hold Train' is invoked, and assuming that a v9 segment with disposition code hmi is being processed for a train, when the hmi hold event is processed, the desired outcome is that the train held flag is set to 'y' and the hold action is logged.
💻 Technical Criteria
Given A V9 segment with disposition code HMI is being processed for a train
When The HMI hold event is processed
Then The train held flag is set to 'Y' and the hold action is logged
R-GCX016E-cbl-01589 Process HRE - Release Hold
Action Rules
📊 Business Logic Narrative
When the process 'Process HRE - Release Hold' is invoked, and assuming that a v9 segment with disposition code hre is being processed for a train, when the hre hold release event is processed, the desired outcome is that the train held flag is set to 'n' and the release action is logged.
💻 Technical Criteria
Given A V9 segment with disposition code HRE is being processed for a train
When The HRE hold release event is processed
Then The train held flag is set to 'N' and the release action is logged
R-GCX016E-cbl-01590 Process SEI - Seize Train
Action Rules
📊 Business Logic Narrative
When the process 'Process SEI - Seize Train' is invoked, and assuming that a v9 segment with disposition code sei is being processed for a train, when the sei seizure event is processed, the desired outcome is that the train seized flag is set to 'y' and the seizure action is logged.
💻 Technical Criteria
Given A V9 segment with disposition code SEI is being processed for a train
When The SEI seizure event is processed
Then The train seized flag is set to 'Y' and the seizure action is logged
R-GCX016E-cbl-01591 Process SER - Release Seizure
Action Rules
📊 Business Logic Narrative
When the process 'Process SER - Release Seizure' is invoked, and assuming that a v9 segment with disposition code ser is being processed for a train, when the ser seizure release event is processed, the desired outcome is that the train seized flag is set to 'n' and the release action is logged.
💻 Technical Criteria
Given A V9 segment with disposition code SER is being processed for a train
When The SER seizure release event is processed
Then The train seized flag is set to 'N' and the release action is logged
R-GCX016E-cbl-01592 Process LCK - Lock Train
Action Rules
📊 Business Logic Narrative
When the process 'Process LCK - Lock Train' is invoked, and assuming that a v9 segment with disposition code lck is being processed for a train, when the lck lock event is processed, the desired outcome is that the train locked flag is set to 'y'.
💻 Technical Criteria
Given A V9 segment with disposition code LCK is being processed for a train
When The LCK lock event is processed
Then The train locked flag is set to 'Y'
R-GCX016E-cbl-01593 Process ULC - Unlock Train
Decision Rules
📊 Business Logic Narrative
When the process 'Process ULC - Unlock Train' is invoked, and assuming that a v9 segment with disposition code ulc is being processed for a train, when the ulc unlock event is processed and the train is currently locked, the desired outcome is that the train locked flag is set to 'n'.
💻 Technical Criteria
Given A V9 segment with disposition code ULC is being processed for a train
When The ULC unlock event is processed and the train is currently locked
Then The train locked flag is set to 'N'
R-GCX016E-cbl-01594 Process POD/AAD - Train Arrival
Action Rules
📊 Business Logic Narrative
When the process 'Process POD/AAD - Train Arrival' is invoked, and assuming that a v9 segment with disposition code pod or aad is being processed for a train, when the arrival event is processed, the desired outcome is that the train arrival flag is set to 'y' and the train arrival date is recorded.
💻 Technical Criteria
Given A V9 segment with disposition code POD or AAD is being processed for a train
When The arrival event is processed
Then The train arrival flag is set to 'Y' and the train arrival date is recorded
R-GCX016E-cbl-01595 Process COC - Cancel Arrival
Action Rules
📊 Business Logic Narrative
When the process 'Process COC - Cancel Arrival' is invoked, and assuming that a v9 segment with disposition code coc is being processed for a train, when the coc cancellation event is processed, the desired outcome is that the train arrival flag is set to 'n' and the train arrival date is cleared.
💻 Technical Criteria
Given A V9 segment with disposition code COC is being processed for a train
When The COC cancellation event is processed
Then The train arrival flag is set to 'N' and the train arrival date is cleared
R-GCX016E-cbl-01597 Update Train Status in Database
Process Rules
📊 Business Logic Narrative
When the process 'Update Train Status in Database' is invoked, and assuming that a train status flag has been modified due to a v9 disposition code event, when the status processing is complete, the desired outcome is that the train status is updated in the database and the status change is logged.
💻 Technical Criteria
Given A train status flag has been modified due to a V9 disposition code event
When The status processing is complete
Then The train status is updated in the database and the status change is logged
R-GCX016E-cbl-01603 Disposition Code Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Disposition Code Type?' is invoked, and assuming that a vid disposition code has been determined, when the system evaluates the disposition code type, the desired outcome is that the code is classified as hmi hold, hre release, sei seizure, or ser seizure release for appropriate processing.
💻 Technical Criteria
Given A VID disposition code has been determined
When The system evaluates the disposition code type
Then The code is classified as HMI Hold, HRE Release, SEI Seizure, or SER Seizure Release for appropriate processing
R-GCX016E-cbl-01625 Default to System Date
Action Rules
📊 Business Logic Narrative
When the process 'Default to System Date' is invoked, and assuming that the v9 segment date is invalid, missing, or fails validation, when the system requires a train arrival date for processing, the desired outcome is that the system assigns the current system date as the default train arrival date.
💻 Technical Criteria
Given The V9 segment date is invalid, missing, or fails validation
When The system requires a train arrival date for processing
Then The system assigns the current system date as the default train arrival date
R-GCX016E-cbl-01626 Format Date for Processing
Computation Rules
📊 Business Logic Narrative
When the process 'Format Date for Processing' is invoked, and assuming that a train arrival date has been determined (either from v9 segment or system default), when the system prepares the date for train record processing, the desired outcome is that the system formats the date into the standard format required for train arrival processing.
💻 Technical Criteria
Given A train arrival date has been determined (either from V9 segment or system default)
When The system prepares the date for train record processing
Then The system formats the date into the standard format required for train arrival processing
R-GCX016E-cbl-01629 Set Train Arrival Date
Action Rules
📊 Business Logic Narrative
When the process 'Set Train Arrival Date' is invoked, and assuming that a train arrival date has been validated and formatted, and train type processing is complete, when the system updates the train record, the desired outcome is that the system assigns the arrival date to the train record for all subsequent processing.
💻 Technical Criteria
Given A train arrival date has been validated and formatted, and train type processing is complete
When The system updates the train record
Then The system assigns the arrival date to the train record for all subsequent processing
R-GCX016E-cbl-01630 Update Train Status to Arrived
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Status to Arrived' is invoked, and assuming that the train arrival date has been successfully set in the train record, when the system updates the train operational status, the desired outcome is that the system changes the train status to 'arrived' to reflect the current operational state.
💻 Technical Criteria
Given The train arrival date has been successfully set in the train record
When The system updates the train operational status
Then The system changes the train status to 'Arrived' to reflect the current operational state
R-GCX016E-cbl-01631 Log Arrival Date Assignment
Process Rules
📊 Business Logic Narrative
When the process 'Log Arrival Date Assignment' is invoked, and assuming that the train status has been updated to arrived with the assigned arrival date, when the system performs audit logging for the arrival event, the desired outcome is that the system creates a log entry documenting the arrival date assignment, source of date (v9 segment or system default), and timestamp of the assignment.
💻 Technical Criteria
Given The train status has been updated to arrived with the assigned arrival date
When The system performs audit logging for the arrival event
Then The system creates a log entry documenting the arrival date assignment, source of date (V9 segment or system default), and timestamp of the assignment
R-GCX016E-cbl-01633 Send Arrival Confirmation
Action Rules
📊 Business Logic Narrative
When the process 'Send Arrival Confirmation' is invoked, and assuming that the aei notification has been generated for the train arrival, when the system sends confirmation messages to business stakeholders, the desired outcome is that the system transmits arrival confirmation containing train details, arrival date, and status to all configured recipients and external systems.
💻 Technical Criteria
Given The AEI notification has been generated for the train arrival
When The system sends confirmation messages to business stakeholders
Then The system transmits arrival confirmation containing train details, arrival date, and status to all configured recipients and external systems
R-GCX016E-cbl-01636 Set Train Arrival Status
Action Rules
📊 Business Logic Narrative
When the process 'Set Train Arrival Status' is invoked, and assuming that a train has been validated for arrival processing, when the system processes the arrival event, the desired outcome is that set the train arrival status flag to indicate the train has arrived.
💻 Technical Criteria
Given A train has been validated for arrival processing
When The system processes the arrival event
Then Set the train arrival status flag to indicate the train has arrived
R-GCX016E-cbl-01637 Update Train Arrival Date from V9 Segment
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Arrival Date from V9 Segment' is invoked, and assuming that a train arrival status has been set, when the system processes the v9 segment containing arrival date and time, the desired outcome is that update the train arrival date with the date and time from the v9 segment.
💻 Technical Criteria
Given A train arrival status has been set
When The system processes the V9 segment containing arrival date and time
Then Update the train arrival date with the date and time from the V9 segment
R-GCX016E-cbl-01644 Send AEI Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send AEI Notification' is invoked, and assuming that aei message has been generated, when the system sends arrival notifications, the desired outcome is that transmit the aei notification to configured recipients and external systems.
💻 Technical Criteria
Given AEI message has been generated
When The system sends arrival notifications
Then Transmit the AEI notification to configured recipients and external systems
R-GCX016E-cbl-01646 Log Train Arrival Action
Action Rules
📊 Business Logic Narrative
When the process 'Log Train Arrival Action' is invoked, and assuming that arrival notification message has been created, when the system logs the arrival event, the desired outcome is that record the train arrival action in system logs with timestamp and details.
💻 Technical Criteria
Given Arrival notification message has been created
When The system logs the arrival event
Then Record the train arrival action in system logs with timestamp and details
R-GCX016E-cbl-01650 Associate Text with Current Train ID
Process Rules
📊 Business Logic Narrative
When the process 'Associate Text with Current Train ID' is invoked, and assuming that free-form text has been extracted from k1 segment, when the system processes train identification, the desired outcome is that the k1 text should be associated with the current train id.
💻 Technical Criteria
Given Free-form text has been extracted from K1 segment
When The system processes train identification
Then The K1 text should be associated with the current train ID
R-GCX016E-cbl-01651 Link Text to Train Disposition Code
Process Rules
📊 Business Logic Narrative
When the process 'Link Text to Train Disposition Code' is invoked, and assuming that k1 text is associated with current train id, when the system processes disposition code context, the desired outcome is that the k1 text should be linked to the train disposition code.
💻 Technical Criteria
Given K1 text is associated with current train ID
When The system processes disposition code context
Then The K1 text should be linked to the train disposition code
R-GCX016E-cbl-01655 Log K1 Remark for Train
Process Rules
📊 Business Logic Narrative
When the process 'Log K1 Remark for Train' is invoked, and assuming that k1 text is stored in train processing context, when the system performs logging operations, the desired outcome is that the k1 remark should be logged for the train.
💻 Technical Criteria
Given K1 text is stored in train processing context
When The system performs logging operations
Then The K1 remark should be logged for the train
R-GCX016E-cbl-01663 Add to K1 Comment Array
Process Rules
📊 Business Logic Narrative
When the process 'Add to K1 Comment Array' is invoked, and assuming that a k1 comment is linked to a disposition code, when the comment needs to be stored in the array structure, the desired outcome is that the system should add the k1 comment to the appropriate comment array position.
💻 Technical Criteria
Given A K1 comment is linked to a disposition code
When The comment needs to be stored in the array structure
Then The system should add the K1 comment to the appropriate comment array position
R-GCX016E-cbl-01664 More K1 Segments?
Decision Rules
📊 Business Logic Narrative
When the process 'More K1 Segments?' is invoked, and assuming that a k1 segment has been processed and stored, when the system checks for additional k1 segments in the message, the desired outcome is that the system should continue k1 processing if more segments exist or proceed to integration if complete.
💻 Technical Criteria
Given A K1 segment has been processed and stored
When The system checks for additional K1 segments in the message
Then The system should continue K1 processing if more segments exist or proceed to integration if complete
R-GCX016E-cbl-01666 Include K1 Text in Merlin Notifications
Process Rules
📊 Business Logic Narrative
When the process 'Include K1 Text in Merlin Notifications' is invoked, and assuming that k1 comments are integrated into processing and merlin notifications are being generated, when the system creates notification messages, the desired outcome is that the system should include relevant k1 comment text in the merlin notification content.
💻 Technical Criteria
Given K1 comments are integrated into processing and Merlin notifications are being generated
When The system creates notification messages
Then The system should include relevant K1 comment text in the Merlin notification content
R-GCX016E-cbl-01667 Log K1 Message for Audit Trail
Policy Rules
📊 Business Logic Narrative
When the process 'Log K1 Message for Audit Trail' is invoked, and assuming that k1 comments have been included in merlin notifications, when the system needs to maintain audit trail records, the desired outcome is that the system should log k1 message details for audit and compliance purposes.
💻 Technical Criteria
Given K1 comments have been included in Merlin notifications
When The system needs to maintain audit trail records
Then The system should log K1 message details for audit and compliance purposes
R-GCX016E-cbl-01669 Date Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Date Valid?' is invoked, and assuming that an x4 segment is received with a disposition code date field, when the system extracts and validates the disposition code date, the desired outcome is that if the date is valid, use the extracted date; if the date is invalid or missing, default to the current system date.
💻 Technical Criteria
Given An X4 segment is received with a disposition code date field
When The system extracts and validates the disposition code date
Then If the date is valid, use the extracted date; if the date is invalid or missing, default to the current system date
R-GCX016E-cbl-01670 Time Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Time Valid?' is invoked, and assuming that an x4 segment is received with a disposition code time field, when the system extracts and validates the disposition code time, the desired outcome is that if the time is valid, use the extracted time; if the time is invalid or missing, default to the current system time.
💻 Technical Criteria
Given An X4 segment is received with a disposition code time field
When The system extracts and validates the disposition code time
Then If the time is valid, use the extracted time; if the time is invalid or missing, default to the current system time
R-GCX016E-cbl-01671 Extract Disposition Code Date
Process Rules
📊 Business Logic Narrative
When the process 'Extract Disposition Code Date' is invoked, and assuming that an x4 segment containing disposition code information, when the system processes the x4 segment, the desired outcome is that extract the date field from the disposition code data for further validation.
💻 Technical Criteria
Given An X4 segment containing disposition code information
When The system processes the X4 segment
Then Extract the date field from the disposition code data for further validation
R-GCX016E-cbl-01672 Extract Disposition Code Time
Process Rules
📊 Business Logic Narrative
When the process 'Extract Disposition Code Time' is invoked, and assuming that an x4 segment containing disposition code information, when the system processes the x4 segment, the desired outcome is that extract the time field from the disposition code data for further validation.
💻 Technical Criteria
Given An X4 segment containing disposition code information
When The system processes the X4 segment
Then Extract the time field from the disposition code data for further validation
R-GCX016E-cbl-01677 Format Date for Processing
Computation Rules
📊 Business Logic Narrative
When the process 'Format Date for Processing' is invoked, and assuming that a valid date (either extracted or system default) for disposition code processing, when the date needs to be formatted for system processing, the desired outcome is that convert the date into the standard format required for disposition code operations.
💻 Technical Criteria
Given A valid date (either extracted or system default) for disposition code processing
When The date needs to be formatted for system processing
Then Convert the date into the standard format required for disposition code operations
R-GCX016E-cbl-01678 Format Time for Processing
Computation Rules
📊 Business Logic Narrative
When the process 'Format Time for Processing' is invoked, and assuming that a valid time (either extracted or system default) for disposition code processing, when the time needs to be formatted for system processing, the desired outcome is that convert the time into the standard format required for disposition code operations.
💻 Technical Criteria
Given A valid time (either extracted or system default) for disposition code processing
When The time needs to be formatted for system processing
Then Convert the time into the standard format required for disposition code operations
R-GCX016E-cbl-01722 Log Entry Type Code Conversion
Process Rules
📊 Business Logic Narrative
When the process 'Log Entry Type Code Conversion' is invoked, and assuming that the entry type code has been successfully stored, when the system completes entry type code conversion processing, the desired outcome is that log the entry type code conversion details for audit trail and tracking purposes.
💻 Technical Criteria
Given The entry type code has been successfully stored
When The system completes entry type code conversion processing
Then Log the entry type code conversion details for audit trail and tracking purposes
R-GCX016E-cbl-01736 Format FDA Reference Number for A1
Definitional Rules
📊 Business Logic Narrative
When the process 'Format FDA Reference Number for A1' is invoked, and assuming that an a1 disposition code is being processed with an fda reference number, when the system formats the fda reference number, the desired outcome is that the fda reference number is formatted according to a1 disposition code requirements.
💻 Technical Criteria
Given An A1 disposition code is being processed with an FDA reference number
When The system formats the FDA reference number
Then The FDA reference number is formatted according to A1 disposition code requirements
R-GCX016E-cbl-01737 Format FDA Reference Number for A3
Definitional Rules
📊 Business Logic Narrative
When the process 'Format FDA Reference Number for A3' is invoked, and assuming that an a3 disposition code is being processed with an fda reference number, when the system formats the fda reference number, the desired outcome is that the fda reference number is formatted according to a3 disposition code requirements.
💻 Technical Criteria
Given An A3 disposition code is being processed with an FDA reference number
When The system formats the FDA reference number
Then The FDA reference number is formatted according to A3 disposition code requirements
R-GCX016E-cbl-01738 Add 'FDA PN' Prefix for A1
Definitional Rules
📊 Business Logic Narrative
When the process 'Add 'FDA PN' Prefix for A1' is invoked, and assuming that an a1 disposition code is being processed with an fda reference number, when the system adds the required prefix, the desired outcome is that the fda reference number is prefixed with 'fda pn'.
💻 Technical Criteria
Given An A1 disposition code is being processed with an FDA reference number
When The system adds the required prefix
Then The FDA reference number is prefixed with 'FDA PN'
R-GCX016E-cbl-01739 Add 'FDA' Prefix for A3
Definitional Rules
📊 Business Logic Narrative
When the process 'Add 'FDA' Prefix for A3' is invoked, and assuming that an a3 disposition code is being processed with an fda reference number, when the system adds the required prefix, the desired outcome is that the fda reference number is prefixed with 'fda'.
💻 Technical Criteria
Given An A3 disposition code is being processed with an FDA reference number
When The system adds the required prefix
Then The FDA reference number is prefixed with 'FDA'
R-GCX016E-cbl-01743 Validate FDA Reference Number Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate FDA Reference Number Format' is invoked, and assuming that an fda reference number is being processed for a1 or a3 disposition codes, when the system validates the reference number format, the desired outcome is that the fda reference number format is verified to meet business requirements.
💻 Technical Criteria
Given An FDA reference number is being processed for A1 or A3 disposition codes
When The system validates the reference number format
Then The FDA reference number format is verified to meet business requirements
R-GCX016E-cbl-01744 Replace N9 Reference Segment
Action Rules
📊 Business Logic Narrative
When the process 'Replace N9 Reference Segment' is invoked, and assuming that an existing n9 reference segment needs to be updated with fda reference number, when the system processes the segment replacement, the desired outcome is that the n9 reference segment is replaced with the updated fda reference information.
💻 Technical Criteria
Given An existing N9 reference segment needs to be updated with FDA reference number
When The system processes the segment replacement
Then The N9 reference segment is replaced with the updated FDA reference information
R-GCX016E-cbl-01748 Create 350 Special Action Message
Action Rules
📊 Business Logic Narrative
When the process 'Create 350 Special Action Message' is invoked, and assuming that a follower manifest requires processing and the message type is gcw016, when the system creates a special action message, the desired outcome is that a message with special action code 350 is created and general information is copied for the follower manifest.
💻 Technical Criteria
Given A follower manifest requires processing and the message type is GCW016
When The system creates a special action message
Then A message with special action code 350 is created and general information is copied for the follower manifest
R-GCX016E-cbl-01749 Include Disposition Codes in Message
Process Rules
📊 Business Logic Narrative
When the process 'Include Disposition Codes in Message' is invoked, and assuming that a follower manifest message is being prepared and disposition codes exist, when the system includes disposition codes in the message, the desired outcome is that all relevant disposition codes are included in the follower manifest message for downstream processing.
💻 Technical Criteria
Given A follower manifest message is being prepared and disposition codes exist
When The system includes disposition codes in the message
Then All relevant disposition codes are included in the follower manifest message for downstream processing
R-GCX016E-cbl-01752 Spawn GCT0162E Transaction for Follower Processing
Action Rules
📊 Business Logic Narrative
When the process 'Spawn GCT0162E Transaction for Follower Processing' is invoked, and assuming that a follower manifest message has been prepared with all required data, when the system spawns the gct0162e transaction, the desired outcome is that the gct0162e transaction is initiated with the prepared follower manifest message for processing.
💻 Technical Criteria
Given A follower manifest message has been prepared with all required data
When The system spawns the GCT0162E transaction
Then The GCT0162E transaction is initiated with the prepared follower manifest message for processing
R-GCX016E-cbl-01753 Link Follower Manifest to Lead Manifest
Process Rules
📊 Business Logic Narrative
When the process 'Link Follower Manifest to Lead Manifest' is invoked, and assuming that a follower manifest and its corresponding lead manifest are identified, when the system links the follower manifest to the lead manifest, the desired outcome is that the relationship between the follower and lead manifest is established for comprehensive tracking.
💻 Technical Criteria
Given A follower manifest and its corresponding lead manifest are identified
When The system links the follower manifest to the lead manifest
Then The relationship between the follower and lead manifest is established for comprehensive tracking
R-GCX016E-cbl-01755 Log Follower Manifest Processing Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Follower Manifest Processing Action' is invoked, and assuming that a follower manifest processing action has been completed, when the system logs the processing action, the desired outcome is that the follower manifest processing action is recorded in the system log for audit and monitoring purposes.
💻 Technical Criteria
Given A follower manifest processing action has been completed
When The system logs the processing action
Then The follower manifest processing action is recorded in the system log for audit and monitoring purposes
R-GCX016E-cbl-01756 More Follower Manifests?
Decision Rules
📊 Business Logic Narrative
When the process 'More Follower Manifests?' is invoked, and assuming that one follower manifest has been processed and there may be additional follower manifests, when the system checks for more follower manifests to process, the desired outcome is that if more follower manifests exist, continue processing the next one, otherwise complete multi-manifest processing.
💻 Technical Criteria
Given One follower manifest has been processed and there may be additional follower manifests
When The system checks for more follower manifests to process
Then If more follower manifests exist, continue processing the next one, otherwise complete multi-manifest processing
R-GCX016E-cbl-01838 Search Existing Broker Entry Numbers
Validation Rules
📊 Business Logic Narrative
When the process 'Search Existing Broker Entry Numbers' is invoked, and assuming that an entry number with valid format, when the system searches existing broker entry numbers in the database, the desired outcome is that if broker entry number is found, mark entry number as valid, otherwise continue to next validation step.
💻 Technical Criteria
Given An entry number with valid format
When The system searches existing broker entry numbers in the database
Then If broker entry number is found, mark entry number as valid, otherwise continue to next validation step
R-GCX016E-cbl-01843 Entry Number Valid Format?
Decision Rules
📊 Business Logic Narrative
When the process 'Entry Number Valid Format?' is invoked, and assuming that an entry number format validation result, when the system evaluates if entry number has valid format, the desired outcome is that if format is valid, proceed to search existing broker entry numbers, otherwise generate entry number error.
💻 Technical Criteria
Given An entry number format validation result
When The system evaluates if entry number has valid format
Then If format is valid, proceed to search existing broker entry numbers, otherwise generate entry number error
R-GCX016E-cbl-01858 Generate Entry Type Conversion Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Entry Type Conversion Error', assuming that entry type code is present but invalid or conversion fails, when the system encounters an invalid entry type code, the desired outcome is that generate an entry type conversion error and continue processing.
💻 Technical Criteria
EXCLUDING Entry type code is present but invalid or conversion fails
When The system encounters an invalid entry type code
Then Generate an entry type conversion error and continue processing
R-GCX016E-cbl-01859 Skip Entry Type Processing
Process Rules
📊 Business Logic Narrative
When the process 'Skip Entry Type Processing' is invoked, and assuming that no entry type code is present in the x4 segment, when the system evaluates entry type processing requirements, the desired outcome is that skip all entry type conversion processing and continue to next processing step.
💻 Technical Criteria
Given No entry type code is present in the X4 segment
When The system evaluates entry type processing requirements
Then Skip all entry type conversion processing and continue to next processing step
R-GCX016E-cbl-01879 A1 Disposition Code Processing
Process Rules
📊 Business Logic Narrative
When the process 'A1 Disposition Code Processing' is invoked, and assuming that an n9 reference segment is received with a1 disposition code, when the system processes the fda reference number formatting, the desired outcome is that the fda reference number should be prefixed with 'fda pn' and properly formatted.
💻 Technical Criteria
Given An N9 reference segment is received with A1 disposition code
When The system processes the FDA reference number formatting
Then The FDA reference number should be prefixed with 'FDA PN' and properly formatted
R-GCX016E-cbl-01880 A3 Disposition Code Processing
Process Rules
📊 Business Logic Narrative
When the process 'A3 Disposition Code Processing' is invoked, and assuming that an n9 reference segment is received with a3 disposition code, when the system processes the fda reference number formatting, the desired outcome is that the fda reference number should be prefixed with 'fda' and properly formatted.
💻 Technical Criteria
Given An N9 reference segment is received with A3 disposition code
When The system processes the FDA reference number formatting
Then The FDA reference number should be prefixed with 'FDA' and properly formatted
R-GCX016E-cbl-01882 Existing FDA Data Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Existing FDA Data Found?' is invoked, and assuming that an n9 segment is being processed for fda reference formatting, when existing fda data is found in the segment, the desired outcome is that the original fda information should be preserved and not overwritten.
💻 Technical Criteria
Given An N9 segment is being processed for FDA reference formatting
When Existing FDA data is found in the segment
Then The original FDA information should be preserved and not overwritten
R-GCX016E-cbl-01884 Reposition Existing N9 Data
Process Rules
📊 Business Logic Narrative
When the process 'Reposition Existing N9 Data' is invoked, and assuming that an n9 segment contains existing data that needs fda prefix formatting, when the system repositions the existing n9 data, the desired outcome is that the existing data should be moved to appropriate positions to make room for fda prefix.
💻 Technical Criteria
Given An N9 segment contains existing data that needs FDA prefix formatting
When The system repositions the existing N9 data
Then The existing data should be moved to appropriate positions to make room for FDA prefix
R-GCX016E-cbl-01886 Update N9 Segment with Formatted Data
Process Rules
📊 Business Logic Narrative
When the process 'Update N9 Segment with Formatted Data' is invoked, and assuming that fda reference data has been formatted and validated, when the system updates the n9 segment with formatted data, the desired outcome is that the n9 segment should contain the properly formatted fda reference information.
💻 Technical Criteria
Given FDA reference data has been formatted and validated
When The system updates the N9 segment with formatted data
Then The N9 segment should contain the properly formatted FDA reference information
R-GCX016E-cbl-01888 Format FDA PN Prefix for A1
Computation Rules
📊 Business Logic Narrative
When the process 'Format FDA PN Prefix for A1' is invoked, and assuming that an a1 disposition code is being processed, when the system formats the fda reference prefix, the desired outcome is that the system creates a pn prefix format for the fda reference number.
💻 Technical Criteria
Given An A1 disposition code is being processed
When The system formats the FDA reference prefix
Then The system creates a PN prefix format for the FDA reference number
R-GCX016E-cbl-01889 Format FDA Prefix for A3
Computation Rules
📊 Business Logic Narrative
When the process 'Format FDA Prefix for A3' is invoked, and assuming that an a3 disposition code is being processed, when the system formats the fda reference prefix, the desired outcome is that the system creates a standard fda prefix format for the reference number.
💻 Technical Criteria
Given An A3 disposition code is being processed
When The system formats the FDA reference prefix
Then The system creates a standard FDA prefix format for the reference number
R-GCX016E-cbl-01890 N9 Segment Exists?
Validation Rules
📊 Business Logic Narrative
When the process 'N9 Segment Exists?' is invoked, and assuming that the system has retrieved existing n9 reference data from the database, when the system checks for n9 segment existence, the desired outcome is that the system creates a new n9 segment if none exists, or updates the existing n9 segment if one is found.
💻 Technical Criteria
Given The system has retrieved existing N9 reference data from the database
When The system checks for N9 segment existence
Then The system creates a new N9 segment if none exists, or updates the existing N9 segment if one is found
R-GCX016E-cbl-01891 Reference Number Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Reference Number Valid?' is invoked, and assuming that an fda reference number has been formatted with the appropriate prefix, when the system validates the reference number format, the desired outcome is that the system proceeds with fda reference information setting if the format is valid, or completes processing without updates if the format is invalid.
💻 Technical Criteria
Given An FDA reference number has been formatted with the appropriate prefix
When The system validates the reference number format
Then The system proceeds with FDA reference information setting if the format is valid, or completes processing without updates if the format is invalid
R-GCX016E-cbl-01892 Create New N9 Segment
Action Rules
📊 Business Logic Narrative
When the process 'Create New N9 Segment' is invoked, and assuming that no existing n9 segment is found in the database, when the system processes the fda reference information, the desired outcome is that the system creates a new n9 segment with the formatted fda reference data.
💻 Technical Criteria
Given No existing N9 segment is found in the database
When The system processes the FDA reference information
Then The system creates a new N9 segment with the formatted FDA reference data
R-GCX016E-cbl-01893 Update Existing N9 Segment
Action Rules
📊 Business Logic Narrative
When the process 'Update Existing N9 Segment' is invoked, and assuming that an existing n9 segment is found in the database, when the system processes new fda reference information, the desired outcome is that the system updates the existing n9 segment with the new reference data.
💻 Technical Criteria
Given An existing N9 segment is found in the database
When The system processes new FDA reference information
Then The system updates the existing N9 segment with the new reference data
R-GCX016E-cbl-01894 Set FDA Reference Information
Action Rules
📊 Business Logic Narrative
When the process 'Set FDA Reference Information' is invoked, and assuming that the fda reference number format has been validated as correct, when the system processes the reference information, the desired outcome is that the system sets the fda reference information in the n9 segment for database replacement.
💻 Technical Criteria
Given The FDA reference number format has been validated as correct
When The system processes the reference information
Then The system sets the FDA reference information in the N9 segment for database replacement
R-GCX016E-cbl-01895 Replace N9 Segment in Database
Action Rules
📊 Business Logic Narrative
When the process 'Replace N9 Segment in Database' is invoked, and assuming that the fda reference information has been set in the n9 segment, when the system performs database operations, the desired outcome is that the system replaces the n9 segment in the database with the updated reference information.
💻 Technical Criteria
Given The FDA reference information has been set in the N9 segment
When The system performs database operations
Then The system replaces the N9 segment in the database with the updated reference information
R-GCX016E-cbl-01896 Log N9 Reference Update
Process Rules
📊 Business Logic Narrative
When the process 'Log N9 Reference Update' is invoked, and assuming that the n9 segment has been successfully replaced in the database, when the system completes the reference update process, the desired outcome is that the system logs the n9 reference update activity for audit trail maintenance.
💻 Technical Criteria
Given The N9 segment has been successfully replaced in the database
When The system completes the reference update process
Then The system logs the N9 reference update activity for audit trail maintenance
R-GCX016E-cbl-01963 Log SCAC Processing Action
Action Rules
📊 Business Logic Narrative
When the process 'Log SCAC Processing Action' is invoked, and assuming that scac unknown scenario processing has been completed, when the system logs the processing action, the desired outcome is that the system records the scac processing details for audit trail.
💻 Technical Criteria
Given SCAC unknown scenario processing has been completed
When The system logs the processing action
Then The system records the SCAC processing details for audit trail
R-GCX016E-cbl-01972 Process Retrieved S09 Segments
Process Rules
📊 Business Logic Narrative
When the process 'Process Retrieved S09 Segments' is invoked, and assuming that s09 status segments have been successfully retrieved from the database, when the system processes each retrieved segment, the desired outcome is that each s09 segment is processed to extract status data for array population.
💻 Technical Criteria
Given S09 status segments have been successfully retrieved from the database
When The system processes each retrieved segment
Then Each S09 segment is processed to extract status data for array population
R-GCX016E-cbl-01973 Populate S09A Status Arrays
Process Rules
📊 Business Logic Narrative
When the process 'Populate S09A Status Arrays' is invoked, and assuming that s09 segments have been processed and status data extracted, when the system populates status arrays, the desired outcome is that s09a status arrays are populated with the extracted status information from each segment.
💻 Technical Criteria
Given S09 segments have been processed and status data extracted
When The system populates status arrays
Then S09A status arrays are populated with the extracted status information from each segment
R-GCX016E-cbl-01975 More Segments to Process?
Decision Rules
📊 Business Logic Narrative
When the process 'More Segments to Process?' is invoked, and assuming that status segments are being processed sequentially, when the system completes processing of a segment, the desired outcome is that if more segments exist, continue processing; if no more segments, proceed to finalize arrays.
💻 Technical Criteria
Given Status segments are being processed sequentially
When The system completes processing of a segment
Then If more segments exist, continue processing; if no more segments, proceed to finalize arrays
R-GCX016E-cbl-01976 Set Status Arrays Ready Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Status Arrays Ready Flag' is invoked, and assuming that all status segments have been processed and arrays populated, when the status segment retrieval process is complete, the desired outcome is that the status arrays ready flag is set to indicate successful completion.
💻 Technical Criteria
Given All status segments have been processed and arrays populated
When The status segment retrieval process is complete
Then The status arrays ready flag is set to indicate successful completion
R-GCX016E-cbl-01979 Status Segments Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Status Segments Found?' is invoked, and assuming that a database query for s09 status segments has been executed, when the query results are evaluated, the desired outcome is that if status segments are found, continue with array population, otherwise complete the process without population.
💻 Technical Criteria
Given A database query for S09 status segments has been executed
When The query results are evaluated
Then If status segments are found, continue with array population, otherwise complete the process without population
R-GCX016E-cbl-01980 Extract Disposition Code Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Disposition Code Information' is invoked, and assuming that a status segment is being processed, when disposition code information needs to be extracted, the desired outcome is that the disposition code, entry number, and quantity information are extracted from the segment.
💻 Technical Criteria
Given A status segment is being processed
When Disposition code information needs to be extracted
Then The disposition code, entry number, and quantity information are extracted from the segment
R-GCX016E-cbl-01981 Extract Date and Time Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Date and Time Information' is invoked, and assuming that a status segment contains date and time information, when the segment is being processed for array population, the desired outcome is that the date and time information is extracted and formatted for storage in the status array.
💻 Technical Criteria
Given A status segment contains date and time information
When The segment is being processed for array population
Then The date and time information is extracted and formatted for storage in the status array
R-GCX016E-cbl-01982 Extract Status Information Code
Process Rules
📊 Business Logic Narrative
When the process 'Extract Status Information Code' is invoked, and assuming that a status segment is being processed, when status information needs to be extracted, the desired outcome is that the status information code is extracted to identify the type of status change recorded.
💻 Technical Criteria
Given A status segment is being processed
When Status information needs to be extracted
Then The status information code is extracted to identify the type of status change recorded
R-GCX016E-cbl-01983 Store in S09A Status Array
Process Rules
📊 Business Logic Narrative
When the process 'Store in S09A Status Array' is invoked, and assuming that status information has been extracted from a database segment, when the information needs to be stored for processing, the desired outcome is that the disposition code, dates, times, and status information are stored in the corresponding s09a array element.
💻 Technical Criteria
Given Status information has been extracted from a database segment
When The information needs to be stored for processing
Then The disposition code, dates, times, and status information are stored in the corresponding S09A array element
R-GCX016E-cbl-01984 Increment Array Counter
Process Rules
📊 Business Logic Narrative
When the process 'Increment Array Counter' is invoked, and assuming that a status segment has been successfully stored in the status array, when the storage operation is complete, the desired outcome is that the array counter is incremented by one to reflect the additional stored segment.
💻 Technical Criteria
Given A status segment has been successfully stored in the status array
When The storage operation is complete
Then The array counter is incremented by one to reflect the additional stored segment
R-GCX016E-cbl-01993 Replace Status Segment in GCSUSS09
Action Rules
📊 Business Logic Narrative
When the process 'Replace Status Segment in GCSUSS09' is invoked, and assuming that a properly formatted database segment is ready for storage, when the system performs the database replacement operation, the desired outcome is that replace the existing status segment in gcsuss09 table with the updated segment containing current status information.
💻 Technical Criteria
Given A properly formatted database segment is ready for storage
When The system performs the database replacement operation
Then Replace the existing status segment in GCSUSS09 table with the updated segment containing current status information
R-GCX016E-cbl-01994 Database Update Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Database Update Successful?' is invoked, and assuming that a database replacement operation has been attempted on gcsuss09, when the system checks the operation result, the desired outcome is that if the update was successful, proceed to log successful replacement, if there was an error, handle the database error appropriately.
💻 Technical Criteria
Given A database replacement operation has been attempted on GCSUSS09
When The system checks the operation result
Then If the update was successful, proceed to log successful replacement, if there was an error, handle the database error appropriately
R-GCX016E-cbl-01996 Handle Database Error
Process Rules
📊 Business Logic Narrative
When the process 'Handle Database Error' is invoked, and assuming that a database replacement operation has failed, when the system encounters a database error, the desired outcome is that handle the error by logging the failure details and determining appropriate recovery or notification actions.
💻 Technical Criteria
Given A database replacement operation has failed
When The system encounters a database error
Then Handle the error by logging the failure details and determining appropriate recovery or notification actions
R-GCX016E-cbl-01998 Initialize Database Segment Counter
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Database Segment Counter' is invoked, and assuming that a status array conversion process is starting, when the system begins the conversion operation, the desired outcome is that the database segment counter is set to zero and work areas are cleared.
💻 Technical Criteria
Given A status array conversion process is starting
When The system begins the conversion operation
Then The database segment counter is set to zero and work areas are cleared
R-GCX016E-cbl-02000 More Status Array Entries?
Decision Rules
📊 Business Logic Narrative
When the process 'More Status Array Entries?' is invoked, and assuming that a status array with multiple entries exists, when the system checks for remaining entries to process, the desired outcome is that the system returns true if more entries exist or false if all entries have been processed.
💻 Technical Criteria
Given A status array with multiple entries exists
When The system checks for remaining entries to process
Then The system returns true if more entries exist or false if all entries have been processed
R-GCX016E-cbl-02001 Get Next Status Array Entry
Process Rules
📊 Business Logic Narrative
When the process 'Get Next Status Array Entry' is invoked, and assuming that status array entries are available for processing, when the system needs to process the next entry, the desired outcome is that the next status array entry is retrieved and made available for data extraction.
💻 Technical Criteria
Given Status array entries are available for processing
When The system needs to process the next entry
Then The next status array entry is retrieved and made available for data extraction
R-GCX016E-cbl-02002 Extract Disposition Code
Process Rules
📊 Business Logic Narrative
When the process 'Extract Disposition Code' is invoked, and assuming that a status array entry contains disposition code information, when the system processes the entry for database conversion, the desired outcome is that the disposition code is extracted and prepared for database segment formatting.
💻 Technical Criteria
Given A status array entry contains disposition code information
When The system processes the entry for database conversion
Then The disposition code is extracted and prepared for database segment formatting
R-GCX016E-cbl-02003 Extract Date Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Date Information' is invoked, and assuming that a status array entry contains date information, when the system processes the entry for database conversion, the desired outcome is that the date information is extracted and prepared for database segment formatting.
💻 Technical Criteria
Given A status array entry contains date information
When The system processes the entry for database conversion
Then The date information is extracted and prepared for database segment formatting
R-GCX016E-cbl-02004 Extract Time Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Time Information' is invoked, and assuming that a status array entry contains time information, when the system processes the entry for database conversion, the desired outcome is that the time information is extracted and prepared for database segment formatting.
💻 Technical Criteria
Given A status array entry contains time information
When The system processes the entry for database conversion
Then The time information is extracted and prepared for database segment formatting
R-GCX016E-cbl-02005 Extract Quantity Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Quantity Information' is invoked, and assuming that a status array entry contains quantity information, when the system processes the entry for database conversion, the desired outcome is that the quantity information is extracted and prepared for database segment formatting.
💻 Technical Criteria
Given A status array entry contains quantity information
When The system processes the entry for database conversion
Then The quantity information is extracted and prepared for database segment formatting
R-GCX016E-cbl-02006 Format Database Segment Fields
Process Rules
📊 Business Logic Narrative
When the process 'Format Database Segment Fields' is invoked, and assuming that extracted data from status array entry is available, when the system prepares data for database storage, the desired outcome is that all extracted data is formatted according to database segment field specifications.
💻 Technical Criteria
Given Extracted data from status array entry is available
When The system prepares data for database storage
Then All extracted data is formatted according to database segment field specifications
R-GCX016E-cbl-02007 Move Data to Database Segment
Process Rules
📊 Business Logic Narrative
When the process 'Move Data to Database Segment' is invoked, and assuming that formatted data is ready for database storage, when the system populates the database segment, the desired outcome is that all formatted data is moved to the appropriate database segment fields.
💻 Technical Criteria
Given Formatted data is ready for database storage
When The system populates the database segment
Then All formatted data is moved to the appropriate database segment fields
R-GCX016E-cbl-02008 Increment Segment Counter
Process Rules
📊 Business Logic Narrative
When the process 'Increment Segment Counter' is invoked, and assuming that a status array entry has been successfully processed into database format, when the system completes processing of one entry, the desired outcome is that the database segment counter is incremented by one.
💻 Technical Criteria
Given A status array entry has been successfully processed into database format
When The system completes processing of one entry
Then The database segment counter is incremented by one
R-GCX016E-cbl-02009 Check Segment Capacity
Validation Rules
📊 Business Logic Narrative
When the process 'Check Segment Capacity' is invoked, and assuming that a database segment has a defined maximum capacity for entries, when the system adds an entry to the segment, the desired outcome is that the system checks if the segment capacity limit has been reached.
💻 Technical Criteria
Given A database segment has a defined maximum capacity for entries
When The system adds an entry to the segment
Then The system checks if the segment capacity limit has been reached
R-GCX016E-cbl-02010 Segment Full?
Decision Rules
📊 Business Logic Narrative
When the process 'Segment Full?' is invoked, and assuming that a database segment with defined capacity limits, when the system checks segment capacity after adding an entry, the desired outcome is that the system returns true if segment is at capacity or false if more entries can be added.
💻 Technical Criteria
Given A database segment with defined capacity limits
When The system checks segment capacity after adding an entry
Then The system returns true if segment is at capacity or false if more entries can be added
R-GCX016E-cbl-02011 Write Segment to Database
Action Rules
📊 Business Logic Narrative
When the process 'Write Segment to Database' is invoked, and assuming that a database segment that has reached its capacity limit, when the system determines the segment is full, the desired outcome is that the complete segment is written to the gcsuss09 status segments database.
💻 Technical Criteria
Given A database segment that has reached its capacity limit
When The system determines the segment is full
Then The complete segment is written to the GCSUSS09 status segments database
R-GCX016E-cbl-02012 Initialize New Segment
Process Rules
📊 Business Logic Narrative
When the process 'Initialize New Segment' is invoked, and assuming that a database segment has been written to storage, when more status array entries remain to be processed, the desired outcome is that a new database segment is initialized with cleared fields and reset counter.
💻 Technical Criteria
Given A database segment has been written to storage
When More status array entries remain to be processed
Then A new database segment is initialized with cleared fields and reset counter
R-GCX016E-cbl-02013 Continue with Next Entry
Process Rules
📊 Business Logic Narrative
When the process 'Continue with Next Entry' is invoked, and assuming that the current status array entry has been processed, when more entries remain in the status array, the desired outcome is that the system continues processing with the next available entry.
💻 Technical Criteria
Given The current status array entry has been processed
When More entries remain in the status array
Then The system continues processing with the next available entry
R-GCX016E-cbl-02014 All Entries Processed?
Decision Rules
📊 Business Logic Narrative
When the process 'All Entries Processed?' is invoked, and assuming that a status array with a finite number of entries, when the system completes processing entries, the desired outcome is that the system returns true if all entries are processed or false if entries remain.
💻 Technical Criteria
Given A status array with a finite number of entries
When The system completes processing entries
Then The system returns true if all entries are processed or false if entries remain
R-GCX016E-cbl-02015 Write Final Segment to Database
Action Rules
📊 Business Logic Narrative
When the process 'Write Final Segment to Database' is invoked, and assuming that all status array entries have been processed and a final segment contains data, when no more entries remain to be processed, the desired outcome is that the final database segment is written to the gcsuss09 status segments database.
💻 Technical Criteria
Given All status array entries have been processed and a final segment contains data
When No more entries remain to be processed
Then The final database segment is written to the GCSUSS09 status segments database
R-GCX016E-cbl-02018 Extract Disposition Code from X4 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Disposition Code from X4 Segment' is invoked, and assuming that an x4 segment is being processed, when the system needs to validate the disposition code, the desired outcome is that the disposition code is extracted from the x4 segment for table lookup.
💻 Technical Criteria
Given An X4 segment is being processed
When The system needs to validate the disposition code
Then The disposition code is extracted from the X4 segment for table lookup
R-GCX016E-cbl-02019 Call GCCTBIO to Access DC Table
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCTBIO to Access DC Table' is invoked, and assuming that a disposition code needs to be validated, when the system calls the table access function, the desired outcome is that the dc table is accessed through gcctbio to retrieve disposition code information.
💻 Technical Criteria
Given A disposition code needs to be validated
When The system calls the table access function
Then The DC table is accessed through GCCTBIO to retrieve disposition code information
R-GCX016E-cbl-02020 Disposition Code Found in Table?
Validation Rules
📊 Business Logic Narrative
When the process 'Disposition Code Found in Table?' is invoked, and assuming that a disposition code has been extracted from the x4 segment, when the system searches the dc table for the code, the desired outcome is that the system determines if the disposition code is valid and authorized for use.
💻 Technical Criteria
Given A disposition code has been extracted from the X4 segment
When The system searches the DC table for the code
Then The system determines if the disposition code is valid and authorized for use
R-GCX016E-cbl-02021 Retrieve Processing Rules and Attributes
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Processing Rules and Attributes' is invoked, and assuming that a disposition code is found to be valid in the dc table, when the system needs to process the disposition code, the desired outcome is that all associated processing rules, attributes, and configuration parameters are retrieved from the table.
💻 Technical Criteria
Given A disposition code is found to be valid in the DC table
When The system needs to process the disposition code
Then All associated processing rules, attributes, and configuration parameters are retrieved from the table
R-GCX016E-cbl-02022 Set Disposition Code Valid Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Disposition Code Valid Flag' is invoked, and assuming that a disposition code has been successfully validated against the dc table, when the validation process completes successfully, the desired outcome is that the system sets the disposition code valid flag to enable further processing.
💻 Technical Criteria
Given A disposition code has been successfully validated against the DC table
When The validation process completes successfully
Then The system sets the disposition code valid flag to enable further processing
R-GCX016E-cbl-02023 Extract Action Code for Release Quantity
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Action Code for Release Quantity' is invoked, and assuming that a valid disposition code with associated processing rules, when the system needs to determine quantity impact, the desired outcome is that the action code for release quantity processing is extracted from the disposition code attributes.
💻 Technical Criteria
Given A valid disposition code with associated processing rules
When The system needs to determine quantity impact
Then The action code for release quantity processing is extracted from the disposition code attributes
R-GCX016E-cbl-02026 Set Disposition Code Invalid Flag
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Disposition Code Invalid Flag', assuming that a disposition code is not found in the dc table, when the validation process fails, the desired outcome is that the system sets the disposition code invalid flag to prevent further processing.
💻 Technical Criteria
EXCLUDING A disposition code is not found in the DC table
When The validation process fails
Then The system sets the disposition code invalid flag to prevent further processing
R-GCX016E-cbl-02027 Generate Merlin Error Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Merlin Error Message' is invoked, and assuming that an invalid disposition code has been identified, when error handling is required, the desired outcome is that an error message is generated and sent to the merlin messaging system to notify users of the invalid code.
💻 Technical Criteria
Given An invalid disposition code has been identified
When Error handling is required
Then An error message is generated and sent to the Merlin messaging system to notify users of the invalid code
R-GCX016E-cbl-02028 Log Unknown Disposition Code
Process Rules
📊 Business Logic Narrative
When the process 'Log Unknown Disposition Code' is invoked, and assuming that a disposition code is determined to be invalid or unknown, when logging is required for audit purposes, the desired outcome is that the unknown disposition code is logged with relevant context information for system administrators.
💻 Technical Criteria
Given A disposition code is determined to be invalid or unknown
When Logging is required for audit purposes
Then The unknown disposition code is logged with relevant context information for system administrators
R-GCX016E-cbl-02032 Duplicate Code Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Duplicate Code Found?' is invoked, and assuming that the system has searched through existing s09a status arrays, when a matching disposition code is found in the existing status entries, the desired outcome is that the system flags the code as a duplicate and proceeds with duplicate handling logic.
💻 Technical Criteria
Given The system has searched through existing S09A status arrays
When A matching disposition code is found in the existing status entries
Then The system flags the code as a duplicate and proceeds with duplicate handling logic
R-GCX016E-cbl-02033 Code Type Analysis
Decision Rules
📊 Business Logic Narrative
When the process 'Code Type Analysis' is invoked, and assuming that a duplicate disposition code has been detected, when the system analyzes the disposition code characteristics from the dc table, the desired outcome is that the system categorizes the code as hold code, release code, status info code, or removal code based on its processing requirements.
💻 Technical Criteria
Given A duplicate disposition code has been detected
When The system analyzes the disposition code characteristics from the DC table
Then The system categorizes the code as Hold Code, Release Code, Status Info Code, or Removal Code based on its processing requirements
R-GCX016E-cbl-02036 Handle Status Info Code Duplicate
Process Rules
📊 Business Logic Narrative
When the process 'Handle Status Info Code Duplicate' is invoked, and assuming that a duplicate disposition code is identified as a status info code type, when the system processes the duplicate status info code, the desired outcome is that the system keeps the most recent entry and maintains the status information without creating additional duplicates.
💻 Technical Criteria
Given A duplicate disposition code is identified as a Status Info Code type
When The system processes the duplicate status info code
Then The system keeps the most recent entry and maintains the status information without creating additional duplicates
R-GCX016E-cbl-02037 Handle Removal Code Duplicate
Process Rules
📊 Business Logic Narrative
When the process 'Handle Removal Code Duplicate' is invoked, and assuming that a duplicate disposition code is identified as a removal code type, when the system processes the duplicate removal code, the desired outcome is that the system removes the older duplicate entry from the status array.
💻 Technical Criteria
Given A duplicate disposition code is identified as a Removal Code type
When The system processes the duplicate removal code
Then The system removes the older duplicate entry from the status array
R-GCX016E-cbl-02038 Update Existing Entry Date/Time
Process Rules
📊 Business Logic Narrative
When the process 'Update Existing Entry Date/Time' is invoked, and assuming that a duplicate hold or release code requires timestamp updates, when the system processes the duplicate entry, the desired outcome is that the system updates the existing entry's date and time fields with the current processing timestamp.
💻 Technical Criteria
Given A duplicate hold or release code requires timestamp updates
When The system processes the duplicate entry
Then The system updates the existing entry's date and time fields with the current processing timestamp
R-GCX016E-cbl-02039 Keep Most Recent Entry
Process Rules
📊 Business Logic Narrative
When the process 'Keep Most Recent Entry' is invoked, and assuming that a duplicate status info code is being processed, when the system compares entry timestamps, the desired outcome is that the system keeps the entry with the most recent timestamp and discards older duplicate information.
💻 Technical Criteria
Given A duplicate status info code is being processed
When The system compares entry timestamps
Then The system keeps the entry with the most recent timestamp and discards older duplicate information
R-GCX016E-cbl-02040 Remove Older Duplicate
Process Rules
📊 Business Logic Narrative
When the process 'Remove Older Duplicate' is invoked, and assuming that a duplicate removal code is being processed, when the system identifies older duplicate entries in the status array, the desired outcome is that the system removes the older duplicate entries and keeps only the most recent removal code.
💻 Technical Criteria
Given A duplicate removal code is being processed
When The system identifies older duplicate entries in the status array
Then The system removes the older duplicate entries and keeps only the most recent removal code
R-GCX016E-cbl-02041 Add New Code to Array
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Add New Code to Array', assuming that a disposition code is not found as a duplicate in existing status arrays, when the system processes the new disposition code, the desired outcome is that the system adds the new disposition code to the appropriate status array with all required information.
💻 Technical Criteria
EXCLUDING A disposition code is not found as a duplicate in existing status arrays
When The system processes the new disposition code
Then The system adds the new disposition code to the appropriate status array with all required information
R-GCX016E-cbl-02042 Log Duplicate Processing Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Duplicate Processing Action' is invoked, and assuming that any duplicate disposition code processing action has been completed, when the system finishes handling the duplicate or new code, the desired outcome is that the system logs the processing action taken including code type, action performed, and timestamp information.
💻 Technical Criteria
Given Any duplicate disposition code processing action has been completed
When The system finishes handling the duplicate or new code
Then The system logs the processing action taken including code type, action performed, and timestamp information
R-GCX016E-cbl-02044 Identify Counterpart Codes
Decision Rules
📊 Business Logic Narrative
When the process 'Identify Counterpart Codes' is invoked, and assuming that a search for conflicting codes has been initiated and existing disposition codes are found in status arrays, when the system evaluates each existing disposition code against the new disposition code, the desired outcome is that the system identifies which existing codes are counterparts that conflict with the new code based on predefined business relationships.
💻 Technical Criteria
Given A search for conflicting codes has been initiated AND existing disposition codes are found in status arrays
When The system evaluates each existing disposition code against the new disposition code
Then The system identifies which existing codes are counterparts that conflict with the new code based on predefined business relationships
R-GCX016E-cbl-02045 Evaluate Business Rules
Policy Rules
📊 Business Logic Narrative
When the process 'Evaluate Business Rules' is invoked, and assuming that counterpart disposition codes have been identified and business rules exist for code conflict resolution, when the system needs to determine if the conflicting code should be removed, the desired outcome is that the system evaluates the business rules considering factors such as code hierarchy, timing, and business logic to make the removal decision.
💻 Technical Criteria
Given Counterpart disposition codes have been identified AND business rules exist for code conflict resolution
When The system needs to determine if the conflicting code should be removed
Then The system evaluates the business rules considering factors such as code hierarchy, timing, and business logic to make the removal decision
R-GCX016E-cbl-02046 Remove Conflicting Code from Array
Action Rules
📊 Business Logic Narrative
When the process 'Remove Conflicting Code from Array' is invoked, and assuming that a conflicting disposition code has been identified and business rules determine it should be removed, when the system processes the removal of the conflicting code, the desired outcome is that the system removes the conflicting disposition code from the status array.
💻 Technical Criteria
Given A conflicting disposition code has been identified AND business rules determine it should be removed
When The system processes the removal of the conflicting code
Then The system removes the conflicting disposition code from the status array
R-GCX016E-cbl-02048 Log Removal Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Removal Action' is invoked, and assuming that a disposition code has been removed from the status array, when the removal action is completed, the desired outcome is that the system logs the removal action including details of which code was removed and why.
💻 Technical Criteria
Given A disposition code has been removed from the status array
When The removal action is completed
Then The system logs the removal action including details of which code was removed and why
R-GCX016E-cbl-02049 More Codes to Check?
Process Rules
📊 Business Logic Narrative
When the process 'More Codes to Check?' is invoked, and assuming that one disposition code has been processed for conflicts and there are additional codes in the status array, when the system completes processing of one code, the desired outcome is that the system checks if there are more codes remaining to be evaluated and continues the conflict checking process if more codes exist.
💻 Technical Criteria
Given One disposition code has been processed for conflicts AND there are additional codes in the status array
When The system completes processing of one code
Then The system checks if there are more codes remaining to be evaluated and continues the conflict checking process if more codes exist
R-GCX016E-cbl-02050 Continue with Status Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue with Status Processing' is invoked, and assuming that all disposition codes have been checked for conflicts and any necessary removals have been completed, when the counterpart removal process is finished, the desired outcome is that the system continues with the normal disposition code processing workflow.
💻 Technical Criteria
Given All disposition codes have been checked for conflicts AND any necessary removals have been completed
When The counterpart removal process is finished
Then The system continues with the normal disposition code processing workflow
R-GCX016E-cbl-02051 Status Info Code Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Status Info Code Valid?' is invoked, and assuming that a status information code is received for processing, when the system validates the code against the dc table, the desired outcome is that the code is accepted if it exists in the dc table, otherwise it is rejected as invalid.
💻 Technical Criteria
Given A status information code is received for processing
When The system validates the code against the DC table
Then The code is accepted if it exists in the DC table, otherwise it is rejected as invalid
R-GCX016E-cbl-02052 Validate Against DC Table
Action Rules
📊 Business Logic Narrative
When the process 'Validate Against DC Table' is invoked, and assuming that a status information code needs validation, when the system searches the dc table for the code, the desired outcome is that the lookup returns success if code exists or failure if code is not found.
💻 Technical Criteria
Given A status information code needs validation
When The system searches the DC table for the code
Then The lookup returns success if code exists or failure if code is not found
R-GCX016E-cbl-02053 Code Already Exists?
Decision Rules
📊 Business Logic Narrative
When the process 'Code Already Exists?' is invoked, and assuming that a validated status information code and existing status arrays, when the system searches all status arrays for the code, the desired outcome is that the search returns true if code exists in any array, false if code is not found.
💻 Technical Criteria
Given A validated status information code and existing status arrays
When The system searches all status arrays for the code
Then The search returns true if code exists in any array, false if code is not found
R-GCX016E-cbl-02054 Array Full?
Validation Rules
📊 Business Logic Narrative
When the process 'Array Full?' is invoked, and assuming that a status array and a new status information code to be added, when the system checks the current array size against maximum capacity, the desired outcome is that the check returns true if array is at maximum capacity, false if space is available.
💻 Technical Criteria
Given A status array and a new status information code to be added
When The system checks the current array size against maximum capacity
Then The check returns true if array is at maximum capacity, false if space is available
R-GCX016E-cbl-02055 Find Insertion Position
Process Rules
📊 Business Logic Narrative
When the process 'Find Insertion Position' is invoked, and assuming that a status array with available capacity and a new status information code, when the system determines the insertion position based on array sequence rules, the desired outcome is that the position is identified where the code should be inserted to maintain proper array order.
💻 Technical Criteria
Given A status array with available capacity and a new status information code
When The system determines the insertion position based on array sequence rules
Then The position is identified where the code should be inserted to maintain proper array order
R-GCX016E-cbl-02056 Insert Status Info Code
Action Rules
📊 Business Logic Narrative
When the process 'Insert Status Info Code' is invoked, and assuming that a validated status information code and determined insertion position, when the system inserts the code into the status array, the desired outcome is that the code is successfully added to the array at the specified position.
💻 Technical Criteria
Given A validated status information code and determined insertion position
When The system inserts the code into the status array
Then The code is successfully added to the array at the specified position
R-GCX016E-cbl-02058 Set Status Info Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Status Info Flag' is invoked, and assuming that a successfully inserted status information code, when the system sets the status information flag, the desired outcome is that the flag is set to indicate status information processing has occurred.
💻 Technical Criteria
Given A successfully inserted status information code
When The system sets the status information flag
Then The flag is set to indicate status information processing has occurred
R-GCX016E-cbl-02059 Log Status Addition
Action Rules
📊 Business Logic Narrative
When the process 'Log Status Addition' is invoked, and assuming that a successfully processed status information code, when the system logs the status addition activity, the desired outcome is that the activity is recorded with relevant details for audit trail.
💻 Technical Criteria
Given A successfully processed status information code
When The system logs the status addition activity
Then The activity is recorded with relevant details for audit trail
R-GCX016E-cbl-02060 Skip Duplicate Code
Decision Rules
📊 Business Logic Narrative
When the process 'Skip Duplicate Code' is invoked, and assuming that a status information code that already exists in the status arrays, when the system detects the duplicate code, the desired outcome is that the processing is skipped and no duplicate entry is created.
💻 Technical Criteria
Given A status information code that already exists in the status arrays
When The system detects the duplicate code
Then The processing is skipped and no duplicate entry is created
R-GCX016E-cbl-02061 Generate Error Message
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error Message', assuming that a status information code that fails validation, when the system processes the invalid code, the desired outcome is that an appropriate error message is generated indicating the code is invalid.
💻 Technical Criteria
EXCLUDING A status information code that fails validation
When The system processes the invalid code
Then An appropriate error message is generated indicating the code is invalid
R-GCX016E-cbl-02062 Array Capacity Error
Action Rules
📊 Business Logic Narrative
When the process 'Array Capacity Error' is invoked, and assuming that a status array at maximum capacity and a new status information code to add, when the system attempts to add the code to the full array, the desired outcome is that an array capacity error is generated and processing is terminated.
💻 Technical Criteria
Given A status array at maximum capacity and a new status information code to add
When The system attempts to add the code to the full array
Then An array capacity error is generated and processing is terminated
R-GCX016E-cbl-02063 Validate Disposition Code Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Disposition Code Format' is invoked, and assuming that a disposition code removal request is received, when the system validates the disposition code format, the desired outcome is that the disposition code must meet format requirements to proceed with removal processing.
💻 Technical Criteria
Given A disposition code removal request is received
When The system validates the disposition code format
Then The disposition code must meet format requirements to proceed with removal processing
R-GCX016E-cbl-02064 Search Status Array for Matching Code
Validation Rules
📊 Business Logic Narrative
When the process 'Search Status Array for Matching Code' is invoked, and assuming that a valid disposition code is provided for removal, when the system searches the status array for the matching disposition code, the desired outcome is that the disposition code must exist in the status array to proceed with removal.
💻 Technical Criteria
Given A valid disposition code is provided for removal
When The system searches the status array for the matching disposition code
Then The disposition code must exist in the status array to proceed with removal
R-GCX016E-cbl-02065 Validate Removal Authority
Authorization Rules
📊 Business Logic Narrative
When the process 'Validate Removal Authority' is invoked, and assuming that a disposition code exists in the status array, when the system checks removal authorization for the requesting entity, the desired outcome is that the requesting entity must have proper authorization to remove the disposition code.
💻 Technical Criteria
Given A disposition code exists in the status array
When The system checks removal authorization for the requesting entity
Then The requesting entity must have proper authorization to remove the disposition code
R-GCX016E-cbl-02066 Mark Disposition Code for Removal
Process Rules
📊 Business Logic Narrative
When the process 'Mark Disposition Code for Removal' is invoked, and assuming that authorization is confirmed for disposition code removal, when the system removes the disposition code from the status array, the desired outcome is that the disposition code is marked for removal and remaining array elements are shifted to fill the gap.
💻 Technical Criteria
Given Authorization is confirmed for disposition code removal
When The system removes the disposition code from the status array
Then The disposition code is marked for removal and remaining array elements are shifted to fill the gap
R-GCX016E-cbl-02068 Log Removal Action
Policy Rules
📊 Business Logic Narrative
When the process 'Log Removal Action' is invoked, and assuming that a disposition code has been successfully removed from the status array, when the system logs the removal action, the desired outcome is that an audit log entry must be created with removal details including code, timestamp, and requesting entity.
💻 Technical Criteria
Given A disposition code has been successfully removed from the status array
When The system logs the removal action
Then An audit log entry must be created with removal details including code, timestamp, and requesting entity
R-GCX016E-cbl-02069 Generate Removal Confirmation
Action Rules
📊 Business Logic Narrative
When the process 'Generate Removal Confirmation' is invoked, and assuming that a disposition code removal has been logged, when the system generates removal confirmation, the desired outcome is that a confirmation message must be created and sent to appropriate recipients confirming the successful removal.
💻 Technical Criteria
Given A disposition code removal has been logged
When The system generates removal confirmation
Then A confirmation message must be created and sent to appropriate recipients confirming the successful removal
R-GCX016E-cbl-02072 Generate Error - Invalid Code Format
Validation Rules
📊 Business Logic Narrative
When the process 'Generate Error - Invalid Code Format' is invoked, and assuming that a disposition code removal request is received, when the disposition code format validation fails, the desired outcome is that an error message must be generated indicating invalid code format and processing must terminate.
💻 Technical Criteria
Given A disposition code removal request is received
When The disposition code format validation fails
Then An error message must be generated indicating invalid code format and processing must terminate
R-GCX016E-cbl-02073 Generate Error - Code Not Found
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error - Code Not Found', assuming that a valid format disposition code is provided for removal, when the disposition code is not found in the status array, the desired outcome is that an error message must be generated indicating code not found and processing must terminate.
💻 Technical Criteria
EXCLUDING A valid format disposition code is provided for removal
When The disposition code is not found in the status array
Then An error message must be generated indicating code not found and processing must terminate
R-GCX016E-cbl-02074 Generate Error - Unauthorized Removal
Authorization Rules
📊 Business Logic Narrative
When the process 'Generate Error - Unauthorized Removal' is invoked, and assuming that a disposition code exists in the status array, when the requesting entity lacks proper removal authorization, the desired outcome is that an error message must be generated indicating unauthorized removal attempt and processing must terminate.
💻 Technical Criteria
Given A disposition code exists in the status array
When The requesting entity lacks proper removal authorization
Then An error message must be generated indicating unauthorized removal attempt and processing must terminate
R-GCX016E-cbl-02077 Remove Existing Release Codes
Process Rules
📊 Business Logic Narrative
When the process 'Remove Existing Release Codes' is invoked, and assuming that existing release codes have been found in the status array, when processing a new release request, the desired outcome is that the system must remove all existing release disposition codes from the status array before adding the new release code.
💻 Technical Criteria
Given Existing release codes have been found in the status array
When Processing a new release request
Then The system must remove all existing release disposition codes from the status array before adding the new release code
R-GCX016E-cbl-02078 Search for Conflicting Hold Codes
Decision Rules
📊 Business Logic Narrative
When the process 'Search for Conflicting Hold Codes' is invoked, and assuming that a release request is being processed, when the system has processed existing release codes, the desired outcome is that the system must search the status array for hold disposition codes that conflict with the release action.
💻 Technical Criteria
Given A release request is being processed
When The system has processed existing release codes
Then The system must search the status array for hold disposition codes that conflict with the release action
R-GCX016E-cbl-02079 Remove Conflicting Hold Codes
Process Rules
📊 Business Logic Narrative
When the process 'Remove Conflicting Hold Codes' is invoked, and assuming that conflicting hold codes have been identified in the status array, when processing a release request, the desired outcome is that the system must remove all conflicting hold disposition codes from the status array to allow the release to proceed.
💻 Technical Criteria
Given Conflicting hold codes have been identified in the status array
When Processing a release request
Then The system must remove all conflicting hold disposition codes from the status array to allow the release to proceed
R-GCX016E-cbl-02080 Validate New Release Disposition Code
Validation Rules
📊 Business Logic Narrative
When the process 'Validate New Release Disposition Code' is invoked, and assuming that a new release disposition code needs to be added, when the system has cleared conflicting codes from the status array, the desired outcome is that the system must validate the new release disposition code exists in the disposition code table and is classified as a valid release code.
💻 Technical Criteria
Given A new release disposition code needs to be added
When The system has cleared conflicting codes from the status array
Then The system must validate the new release disposition code exists in the disposition code table and is classified as a valid release code
R-GCX016E-cbl-02085 Generate Release Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Release Notification' is invoked, and assuming that release status flags have been set successfully, when stakeholders need to be notified of the release, the desired outcome is that the system must generate release notifications to appropriate parties including brokers and freight forwarders.
💻 Technical Criteria
Given Release status flags have been set successfully
When Stakeholders need to be notified of the release
Then The system must generate release notifications to appropriate parties including brokers and freight forwarders
R-GCX016E-cbl-02086 Log Release Request Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Release Request Action' is invoked, and assuming that release notifications have been generated, when the release request processing is complete, the desired outcome is that the system must log the release request action with timestamp and details for audit trail purposes.
💻 Technical Criteria
Given Release notifications have been generated
When The release request processing is complete
Then The system must log the release request action with timestamp and details for audit trail purposes
R-GCX016E-cbl-02087 Generate Error Message
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error Message', assuming that a release disposition code has failed validation, when the code is not found in the disposition code table or is not a valid release code, the desired outcome is that the system must generate an error message indicating the invalid release disposition code.
💻 Technical Criteria
EXCLUDING A release disposition code has failed validation
When The code is not found in the disposition code table or is not a valid release code
Then The system must generate an error message indicating the invalid release disposition code
R-GCX016E-cbl-02102 Validate Auto Release Disposition Code
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Auto Release Disposition Code' is invoked, and assuming that an auto release request is received with a disposition code, when the system validates the disposition code against the disposition code table, the desired outcome is that the system confirms the code is valid for auto release processing or rejects invalid codes.
💻 Technical Criteria
Given An auto release request is received with a disposition code
When The system validates the disposition code against the disposition code table
Then The system confirms the code is valid for auto release processing or rejects invalid codes
R-GCX016E-cbl-02103 Duplicate Auto Release Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Duplicate Auto Release Found?' is invoked, and assuming that a valid auto release disposition code is being processed, when the system searches the existing status arrays for the same auto release code, the desired outcome is that the system identifies if a duplicate auto release code exists and flags it for removal.
💻 Technical Criteria
Given A valid auto release disposition code is being processed
When The system searches the existing status arrays for the same auto release code
Then The system identifies if a duplicate auto release code exists and flags it for removal
R-GCX016E-cbl-02104 Remove Existing Auto Release Code
Process Rules
📊 Business Logic Narrative
When the process 'Remove Existing Auto Release Code' is invoked, and assuming that a duplicate auto release code is found in the status array, when the system processes the new auto release request, the desired outcome is that the system removes the existing auto release code from the status array.
💻 Technical Criteria
Given A duplicate auto release code is found in the status array
When The system processes the new auto release request
Then The system removes the existing auto release code from the status array
R-GCX016E-cbl-02111 Generate Auto Release Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Auto Release Notification' is invoked, and assuming that auto release processing has been completed with quantity updates, when the system generates notifications for the auto release action, the desired outcome is that the system creates merlin messages or email notifications to inform relevant parties of the auto release.
💻 Technical Criteria
Given Auto release processing has been completed with quantity updates
When The system generates notifications for the auto release action
Then The system creates Merlin messages or email notifications to inform relevant parties of the auto release
R-GCX016E-cbl-02115 Generate Error Message
Validation Rules
📊 Business Logic Narrative
When the process 'Generate Error Message' is invoked, and assuming that an auto release request is received with an invalid disposition code, when the disposition code validation fails, the desired outcome is that the system generates an error message indicating invalid disposition code and stops auto release processing.
💻 Technical Criteria
Given An auto release request is received with an invalid disposition code
When The disposition code validation fails
Then The system generates an error message indicating invalid disposition code and stops auto release processing
R-GCX016E-cbl-02117 Call GCCTBIO to Access DC Table
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCTBIO to Access DC Table' is invoked, and assuming that a disposition code needs to be validated, when the system calls gcctbio to access the dc table, the desired outcome is that the dc table is accessed and made available for code lookup.
💻 Technical Criteria
Given A disposition code needs to be validated
When The system calls GCCTBIO to access the DC table
Then The DC table is accessed and made available for code lookup
R-GCX016E-cbl-02118 Disposition Code Found in Table?
Validation Rules
📊 Business Logic Narrative
When the process 'Disposition Code Found in Table?' is invoked, and assuming that a disposition code from x4 or v9 segment, when the system searches for the code in the dc table, the desired outcome is that the system determines if the code exists and is valid for processing.
💻 Technical Criteria
Given A disposition code from X4 or V9 segment
When The system searches for the code in the DC table
Then The system determines if the code exists and is valid for processing
R-GCX016E-cbl-02119 Retrieve Disposition Code Information
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Disposition Code Information' is invoked, and assuming that a disposition code exists in the dc table, when the code lookup is successful, the desired outcome is that the system retrieves all associated code information including description and processing rules.
💻 Technical Criteria
Given A disposition code exists in the DC table
When The code lookup is successful
Then The system retrieves all associated code information including description and processing rules
R-GCX016E-cbl-02120 Extract Code Description
Process Rules
📊 Business Logic Narrative
When the process 'Extract Code Description' is invoked, and assuming that disposition code information has been retrieved from the table, when the system processes the code information, the desired outcome is that the code description is extracted and made available for use in messages and processing.
💻 Technical Criteria
Given Disposition code information has been retrieved from the table
When The system processes the code information
Then The code description is extracted and made available for use in messages and processing
R-GCX016E-cbl-02121 Extract Processing Rules
Process Rules
📊 Business Logic Narrative
When the process 'Extract Processing Rules' is invoked, and assuming that disposition code information has been retrieved and description extracted, when the system processes the code details, the desired outcome is that the processing rules and business logic for the code are extracted and prepared for execution.
💻 Technical Criteria
Given Disposition code information has been retrieved and description extracted
When The system processes the code details
Then The processing rules and business logic for the code are extracted and prepared for execution
R-GCX016E-cbl-02122 Set Valid Code Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Valid Code Flag' is invoked, and assuming that disposition code has been successfully validated and information extracted, when all code validation steps are complete, the desired outcome is that the system sets the valid code flag to allow continued processing.
💻 Technical Criteria
Given Disposition code has been successfully validated and information extracted
When All code validation steps are complete
Then The system sets the valid code flag to allow continued processing
R-GCX016E-cbl-02123 Generate Merlin Error Message
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Merlin Error Message', assuming that a disposition code is not found in the dc table, when the code validation fails, the desired outcome is that the system generates a merlin error message indicating the unknown disposition code.
💻 Technical Criteria
EXCLUDING A disposition code is not found in the DC table
When The code validation fails
Then The system generates a Merlin error message indicating the unknown disposition code
R-GCX016E-cbl-02124 Set Invalid Code Flag
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Invalid Code Flag', assuming that a disposition code is not found in the dc table, when the error message has been generated, the desired outcome is that the system sets the invalid code flag to prevent normal processing.
💻 Technical Criteria
EXCLUDING A disposition code is not found in the DC table
When The error message has been generated
Then The system sets the invalid code flag to prevent normal processing
R-GCX016E-cbl-02125 Log Unknown Code Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Unknown Code Error', assuming that an invalid disposition code has been identified and flagged, when the invalid code flag is set, the desired outcome is that the system logs the unknown code error with relevant details for audit trail.
💻 Technical Criteria
EXCLUDING An invalid disposition code has been identified and flagged
When The invalid code flag is set
Then The system logs the unknown code error with relevant details for audit trail
R-GCX016E-cbl-02126 Continue with Code Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue with Code Processing' is invoked, and assuming that a disposition code has been validated and marked as valid, when the valid code flag is set, the desired outcome is that the system continues with normal disposition code processing using the extracted information.
💻 Technical Criteria
Given A disposition code has been validated and marked as valid
When The valid code flag is set
Then The system continues with normal disposition code processing using the extracted information
R-GCX016E-cbl-02127 Skip Code Processing
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Skip Code Processing', assuming that a disposition code has been identified as invalid and logged, when the invalid code flag is set and error is logged, the desired outcome is that the system skips normal disposition code processing to prevent further errors.
💻 Technical Criteria
EXCLUDING A disposition code has been identified as invalid and logged
When The invalid code flag is set and error is logged
Then The system skips normal disposition code processing to prevent further errors
R-GCX016E-cbl-02144 Search for Duplicate Disposition Codes
Validation Rules
📊 Business Logic Narrative
When the process 'Search for Duplicate Disposition Codes' is invoked, and assuming that a new disposition code is received for processing and existing status arrays contain disposition codes, when the system processes the new disposition code, the desired outcome is that the system searches all status arrays to determine if the same disposition code with matching entry number and quantity already exists.
💻 Technical Criteria
Given A new disposition code is received for processing and existing status arrays contain disposition codes
When The system processes the new disposition code
Then The system searches all status arrays to determine if the same disposition code with matching entry number and quantity already exists
R-GCX016E-cbl-02147 Insert New Disposition Code in Array
Process Rules
📊 Business Logic Narrative
When the process 'Insert New Disposition Code in Array' is invoked, and assuming that an insertion point has been determined for a new disposition code, when the system inserts the disposition code, the desired outcome is that the system adds the disposition code with its associated quantity, entry number, and sequence information to the appropriate status array position.
💻 Technical Criteria
Given An insertion point has been determined for a new disposition code
When The system inserts the disposition code
Then The system adds the disposition code with its associated quantity, entry number, and sequence information to the appropriate status array position
R-GCX016E-cbl-02148 Check for Counterpart Codes to Remove
Decision Rules
📊 Business Logic Narrative
When the process 'Check for Counterpart Codes to Remove' is invoked, and assuming that a new disposition code has been inserted into the status array, when the system checks for business rule conflicts, the desired outcome is that the system identifies any existing disposition codes that are counterparts or conflicts with the newly added code and must be removed.
💻 Technical Criteria
Given A new disposition code has been inserted into the status array
When The system checks for business rule conflicts
Then The system identifies any existing disposition codes that are counterparts or conflicts with the newly added code and must be removed
R-GCX016E-cbl-02149 Remove Conflicting Disposition Codes
Process Rules
📊 Business Logic Narrative
When the process 'Remove Conflicting Disposition Codes' is invoked, and assuming that counterpart or conflicting disposition codes are identified in the status arrays, when business rules require their removal, the desired outcome is that the system removes the conflicting disposition codes from the status arrays.
💻 Technical Criteria
Given Counterpart or conflicting disposition codes are identified in the status arrays
When Business rules require their removal
Then The system removes the conflicting disposition codes from the status arrays
R-GCX016E-cbl-02150 Reorganize Array After Removal
Process Rules
📊 Business Logic Narrative
When the process 'Reorganize Array After Removal' is invoked, and assuming that disposition codes have been removed from status arrays creating gaps, when the removal process is complete, the desired outcome is that the system reorganizes the arrays by moving remaining entries to eliminate gaps and maintain proper array structure.
💻 Technical Criteria
Given Disposition codes have been removed from status arrays creating gaps
When The removal process is complete
Then The system reorganizes the arrays by moving remaining entries to eliminate gaps and maintain proper array structure
R-GCX016E-cbl-02153 Convert Status Array Back to Database Format
Process Rules
📊 Business Logic Narrative
When the process 'Convert Status Array Back to Database Format' is invoked, and assuming that status arrays have been processed and are ready for database storage, when the system needs to save the updated status information, the desired outcome is that the system converts the s09a status arrays back to s09 database segment format with proper structure and sequencing.
💻 Technical Criteria
Given Status arrays have been processed and are ready for database storage
When The system needs to save the updated status information
Then The system converts the S09A status arrays back to S09 database segment format with proper structure and sequencing
R-GCX016E-cbl-02158 Add Quantity Action
Computation Rules
📊 Business Logic Narrative
When the process 'Add Quantity Action' is invoked, and assuming that a disposition code with add action type is being processed, when the action type is determined as add, the desired outcome is that the specified quantity is prepared to be added to the current release quantity.
💻 Technical Criteria
Given A disposition code with add action type is being processed
When The action type is determined as Add
Then The specified quantity is prepared to be added to the current release quantity
R-GCX016E-cbl-02159 Subtract Quantity Action
Computation Rules
📊 Business Logic Narrative
When the process 'Subtract Quantity Action' is invoked, and assuming that a disposition code with subtract action type is being processed, when the action type is determined as subtract, the desired outcome is that the specified quantity is prepared to be subtracted from the current release quantity.
💻 Technical Criteria
Given A disposition code with subtract action type is being processed
When The action type is determined as Subtract
Then The specified quantity is prepared to be subtracted from the current release quantity
R-GCX016E-cbl-02160 Calculate New Release Quantity
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate New Release Quantity' is invoked, and assuming that current release quantity and action quantity are available, when add or subtract action needs to be applied, the desired outcome is that new release quantity is calculated by adding or subtracting the action quantity from current release quantity.
💻 Technical Criteria
Given Current release quantity and action quantity are available
When Add or subtract action needs to be applied
Then New release quantity is calculated by adding or subtracting the action quantity from current release quantity
R-GCX016E-cbl-02161 Quantity Cannot Be Negative
Validation Rules
📊 Business Logic Narrative
When the process 'Quantity Cannot Be Negative' is invoked, and assuming that a new release quantity has been calculated, when the calculated quantity is less than zero, the desired outcome is that the quantity calculation is rejected and processing terminates with validation error.
💻 Technical Criteria
Given A new release quantity has been calculated
When The calculated quantity is less than zero
Then The quantity calculation is rejected and processing terminates with validation error
R-GCX016E-cbl-02169 Generate Release Impact Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Release Impact Message' is invoked, and assuming that release quantity calculation has been completed and logged, when stakeholders need to be notified of quantity changes, the desired outcome is that a release impact message is generated showing the quantity change and its business impact.
💻 Technical Criteria
Given Release quantity calculation has been completed and logged
When Stakeholders need to be notified of quantity changes
Then A release impact message is generated showing the quantity change and its business impact
R-GCX016E-cbl-02179 Format Hold Details
Process Rules
📊 Business Logic Narrative
When the process 'Format Hold Details' is invoked, and assuming that a specific hold type notification has been processed, when the system formats the hold details, the desired outcome is that the system structures the hold information into a standardized format including hold type, reason codes, dates, quantities, and regulatory information for consistent business presentation.
💻 Technical Criteria
Given A specific hold type notification has been processed
When The system formats the hold details
Then The system structures the hold information into a standardized format including hold type, reason codes, dates, quantities, and regulatory information for consistent business presentation
R-GCX016E-cbl-02190 Hold Disposition Codes Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Hold Disposition Codes Present?' is invoked, and assuming that individual status entries have been analyzed, when the system evaluates for hold conditions, the desired outcome is that hold disposition codes are identified if present in the status array.
💻 Technical Criteria
Given Individual status entries have been analyzed
When The system evaluates for hold conditions
Then Hold disposition codes are identified if present in the status array
R-GCX016E-cbl-02192 Release Disposition Codes Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Release Disposition Codes Present?' is invoked, and assuming that hold evaluation has been completed, when the system evaluates for release conditions, the desired outcome is that release disposition codes are identified if present in the status array.
💻 Technical Criteria
Given Hold evaluation has been completed
When The system evaluates for release conditions
Then Release disposition codes are identified if present in the status array
R-GCX016E-cbl-02193 Evaluate Release Conditions
Definitional Rules
📊 Business Logic Narrative
When the process 'Evaluate Release Conditions' is invoked, and assuming that release disposition codes are present in the status array, when the system evaluates release conditions, the desired outcome is that release codes are categorized as full release, partial release, or conditional release based on quantity and conditions.
💻 Technical Criteria
Given Release disposition codes are present in the status array
When The system evaluates release conditions
Then Release codes are categorized as full release, partial release, or conditional release based on quantity and conditions
R-GCX016E-cbl-02194 Proceed Disposition Codes Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Proceed Disposition Codes Present?' is invoked, and assuming that release evaluation has been completed, when the system evaluates for proceed conditions, the desired outcome is that proceed disposition codes are identified if present in the status array.
💻 Technical Criteria
Given Release evaluation has been completed
When The system evaluates for proceed conditions
Then Proceed disposition codes are identified if present in the status array
R-GCX016E-cbl-02200 Multiple Conflicting Codes?
Decision Rules
📊 Business Logic Narrative
When the process 'Multiple Conflicting Codes?' is invoked, and assuming that manual release evaluation has been completed, when the system evaluates for conflicting disposition codes, the desired outcome is that multiple conflicting disposition codes are identified if they exist in the status array.
💻 Technical Criteria
Given Manual release evaluation has been completed
When The system evaluates for conflicting disposition codes
Then Multiple conflicting disposition codes are identified if they exist in the status array
R-GCX016E-cbl-02202 Calculate Final Release Quantity
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Final Release Quantity' is invoked, and assuming that business rule priority has been applied to conflicting codes, when the system calculates final release quantity, the desired outcome is that final release quantity is computed by summing all release quantities and subtracting hold quantities from the status array.
💻 Technical Criteria
Given Business rule priority has been applied to conflicting codes
When The system calculates final release quantity
Then Final release quantity is computed by summing all release quantities and subtracting hold quantities from the status array
R-GCX016E-cbl-02225 Generate Merlin Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Merlin Notification' is invoked, and assuming that the proceed action has been logged, when merlin notification is generated, the desired outcome is that a notification is sent to the merlin system to inform stakeholders of the proceed status.
💻 Technical Criteria
Given The proceed action has been logged
When Merlin notification is generated
Then A notification is sent to the Merlin system to inform stakeholders of the proceed status
R-GCX016E-cbl-02226 Generate Error - Invalid Entry Number
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error - Invalid Entry Number', assuming that entry number validation is performed against existing records, when the entry number is found to be invalid or does not exist, the desired outcome is that an error is generated indicating the entry number is invalid and processing cannot continue.
💻 Technical Criteria
EXCLUDING Entry number validation is performed against existing records
When The entry number is found to be invalid or does not exist
Then An error is generated indicating the entry number is invalid and processing cannot continue
R-GCX016E-cbl-02240 Restore Previous Arrival Date
Action Rules
📊 Business Logic Narrative
When the process 'Restore Previous Arrival Date' is invoked, and assuming that arrival status is being cancelled and a previous arrival date exists, when the system processes the arrival cancellation, the desired outcome is that the previous arrival date is restored to maintain historical accuracy.
💻 Technical Criteria
Given Arrival status is being cancelled and a previous arrival date exists
When The system processes the arrival cancellation
Then The previous arrival date is restored to maintain historical accuracy
R-GCX016E-cbl-02264 Validate Disposition Code Against DC Table
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Disposition Code Against DC Table' is invoked, and assuming that a status information disposition code is received for processing, when the system validates the disposition code against the dc table, the desired outcome is that the code validation result determines whether processing continues or an error is generated.
💻 Technical Criteria
Given A status information disposition code is received for processing
When The system validates the disposition code against the DC table
Then The code validation result determines whether processing continues or an error is generated
R-GCX016E-cbl-02265 Generate Error Message for Unknown Code
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error Message for Unknown Code', assuming that a disposition code has been validated against the dc table, when the disposition code is not found in the dc table, the desired outcome is that an error message is generated for the unknown disposition code and processing continues with next code.
💻 Technical Criteria
EXCLUDING A disposition code has been validated against the DC table
When The disposition code is not found in the DC table
Then An error message is generated for the unknown disposition code and processing continues with next code
R-GCX016E-cbl-02266 Check if Code Already Exists in Status Array
Validation Rules
📊 Business Logic Narrative
When the process 'Check if Code Already Exists in Status Array' is invoked, and assuming that a valid disposition code needs to be added to the status array, when the system checks the s09a status array for existing occurrences of the same code, the desired outcome is that the duplicate check result determines whether the code should be added or skipped.
💻 Technical Criteria
Given A valid disposition code needs to be added to the status array
When The system checks the S09A status array for existing occurrences of the same code
Then The duplicate check result determines whether the code should be added or skipped
R-GCX016E-cbl-02267 Skip Processing - Code Already Present
Process Rules
📊 Business Logic Narrative
When the process 'Skip Processing - Code Already Present' is invoked, and assuming that a disposition code has been checked against the existing status array, when the same disposition code is already present in the s09a array, the desired outcome is that processing is skipped for this code and continues with the next disposition code.
💻 Technical Criteria
Given A disposition code has been checked against the existing status array
When The same disposition code is already present in the S09A array
Then Processing is skipped for this code and continues with the next disposition code
R-GCX016E-cbl-02268 Insert Status Information Code into S09A Array
Action Rules
📊 Business Logic Narrative
When the process 'Insert Status Information Code into S09A Array' is invoked, and assuming that a valid disposition code that doesn't already exist in the status array, when the system processes the status information code for insertion, the desired outcome is that the disposition code is inserted into the s09a status array with appropriate sequence positioning.
💻 Technical Criteria
Given A valid disposition code that doesn't already exist in the status array
When The system processes the status information code for insertion
Then The disposition code is inserted into the S09A status array with appropriate sequence positioning
R-GCX016E-cbl-02270 Update Status Array Sequence Counter
Process Rules
📊 Business Logic Narrative
When the process 'Update Status Array Sequence Counter' is invoked, and assuming that a new status information code has been added to the s09a array, when the system updates the status array management counters, the desired outcome is that the sequence counter is incremented to reflect the new entry and maintain proper array indexing.
💻 Technical Criteria
Given A new status information code has been added to the S09A array
When The system updates the status array management counters
Then The sequence counter is incremented to reflect the new entry and maintain proper array indexing
R-GCX016E-cbl-02271 Log Status Information Addition
Process Rules
📊 Business Logic Narrative
When the process 'Log Status Information Addition' is invoked, and assuming that a status information disposition code has been successfully processed and added, when the system performs logging operations for the status change, the desired outcome is that the status information addition is logged with relevant details for audit trail purposes.
💻 Technical Criteria
Given A status information disposition code has been successfully processed and added
When The system performs logging operations for the status change
Then The status information addition is logged with relevant details for audit trail purposes
R-GCX016E-cbl-02273 Generate Merlin Notification with Status Context
Action Rules
📊 Business Logic Narrative
When the process 'Generate Merlin Notification with Status Context' is invoked, and assuming that status information has been successfully processed and preserved in audit trail, when the system generates notifications for the status information change, the desired outcome is that a merlin notification is generated with complete status context information for relevant stakeholders.
💻 Technical Criteria
Given Status information has been successfully processed and preserved in audit trail
When The system generates notifications for the status information change
Then A Merlin notification is generated with complete status context information for relevant stakeholders
R-GCX016E-cbl-02282 Mark Audit Trail Entry
Process Rules
📊 Business Logic Narrative
When the process 'Mark Audit Trail Entry' is invoked, and assuming that status snapshot has been created with all preserved information, when audit trail entry needs to be finalized, the desired outcome is that the audit trail entry is marked with timestamp and processing context for future reference.
💻 Technical Criteria
Given Status snapshot has been created with all preserved information
When Audit trail entry needs to be finalized
Then The audit trail entry is marked with timestamp and processing context for future reference
R-GCX016E-cbl-02291 Generate Release Cancellation Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Release Cancellation Notification' is invoked, and assuming that a release cancellation has been detected, when the system processes the cancellation event, the desired outcome is that the system generates appropriate business notifications for the release cancellation.
💻 Technical Criteria
Given A release cancellation has been detected
When The system processes the cancellation event
Then The system generates appropriate business notifications for the release cancellation
R-GCX016E-cbl-02295 Include Date/Time Information
Process Rules
📊 Business Logic Narrative
When the process 'Include Date/Time Information' is invoked, and assuming that disposition code details are included in the cancellation message, when the system processes date and time information, the desired outcome is that the message includes transaction date, time, and other relevant temporal information.
💻 Technical Criteria
Given Disposition code details are included in the cancellation message
When The system processes date and time information
Then The message includes transaction date, time, and other relevant temporal information
R-GCX016E-cbl-02298 Log Cancellation Event
Process Rules
📊 Business Logic Narrative
When the process 'Log Cancellation Event' is invoked, and assuming that the cancellation notification is sent to business users, when the system processes the logging requirement, the desired outcome is that the release cancellation event is logged with relevant details for audit and tracking purposes.
💻 Technical Criteria
Given The cancellation notification is sent to business users
When The system processes the logging requirement
Then The release cancellation event is logged with relevant details for audit and tracking purposes
R-GCX016E-cbl-02302 More Status Entries?
Decision Rules
📊 Business Logic Narrative
When the process 'More Status Entries?' is invoked, and assuming that s09a status arrays have been retrieved, when processing status entries sequentially, the desired outcome is that continue to next entry if more exist, otherwise proceed to status analysis.
💻 Technical Criteria
Given S09A status arrays have been retrieved
When Processing status entries sequentially
Then Continue to next entry if more exist, otherwise proceed to status analysis
R-GCX016E-cbl-02304 Set Hold Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Hold Status Flag' is invoked, and assuming that a hold disposition code has been identified, when processing the disposition code, the desired outcome is that the hold status flag is set to active.
💻 Technical Criteria
Given A hold disposition code has been identified
When Processing the disposition code
Then The hold status flag is set to active
R-GCX016E-cbl-02305 Release Disposition Code?
Decision Rules
📊 Business Logic Narrative
When the process 'Release Disposition Code?' is invoked, and assuming that a disposition code is being evaluated, when the disposition code indicates a release condition (manual release, auto release), the desired outcome is that set the release status flag to true.
💻 Technical Criteria
Given A disposition code is being evaluated
When The disposition code indicates a release condition (manual release, auto release)
Then Set the release status flag to true
R-GCX016E-cbl-02306 Set Release Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Release Status Flag' is invoked, and assuming that a release disposition code has been identified, when processing the disposition code, the desired outcome is that the release status flag is set to active.
💻 Technical Criteria
Given A release disposition code has been identified
When Processing the disposition code
Then The release status flag is set to active
R-GCX016E-cbl-02307 Proceed Disposition Code?
Decision Rules
📊 Business Logic Narrative
When the process 'Proceed Disposition Code?' is invoked, and assuming that a disposition code is being evaluated, when the disposition code indicates a proceed condition, the desired outcome is that set the proceed status flag to true.
💻 Technical Criteria
Given A disposition code is being evaluated
When The disposition code indicates a proceed condition
Then Set the proceed status flag to true
R-GCX016E-cbl-02308 Set Proceed Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Proceed Status Flag' is invoked, and assuming that a proceed disposition code has been identified, when processing the disposition code, the desired outcome is that the proceed status flag is set to active.
💻 Technical Criteria
Given A proceed disposition code has been identified
When Processing the disposition code
Then The proceed status flag is set to active
R-GCX016E-cbl-02309 Arrival Disposition Code?
Decision Rules
📊 Business Logic Narrative
When the process 'Arrival Disposition Code?' is invoked, and assuming that a disposition code is being evaluated, when the disposition code indicates an arrival condition, the desired outcome is that set the arrival status flag to true.
💻 Technical Criteria
Given A disposition code is being evaluated
When The disposition code indicates an arrival condition
Then Set the arrival status flag to true
R-GCX016E-cbl-02310 Set Arrival Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Arrival Status Flag' is invoked, and assuming that an arrival disposition code has been identified, when processing the disposition code, the desired outcome is that the arrival status flag is set to active.
💻 Technical Criteria
Given An arrival disposition code has been identified
When Processing the disposition code
Then The arrival status flag is set to active
R-GCX016E-cbl-02314 Hold Status Active?
Decision Rules
📊 Business Logic Narrative
When the process 'Hold Status Active?' is invoked, and assuming that status flags have been analyzed, when the hold status flag is active, the desired outcome is that proceed to check if release status overrides the hold.
💻 Technical Criteria
Given Status flags have been analyzed
When The hold status flag is active
Then Proceed to check if release status overrides the hold
R-GCX016E-cbl-02315 Release Status Active?
Decision Rules
📊 Business Logic Narrative
When the process 'Release Status Active?' is invoked, and assuming that hold status is active, when release status is also active, the desired outcome is that check for manual release to determine final status.
💻 Technical Criteria
Given Hold status is active
When Release status is also active
Then Check for manual release to determine final status
R-GCX016E-cbl-02316 Manual Release Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Manual Release Present?' is invoked, and assuming that both hold and release status are active, when a manual release disposition code is present, the desired outcome is that set final status to released regardless of hold conditions.
💻 Technical Criteria
Given Both hold and release status are active
When A manual release disposition code is present
Then Set final status to RELEASED regardless of hold conditions
R-GCX016E-cbl-02321 Arrival Status Active?
Decision Rules
📊 Business Logic Narrative
When the process 'Arrival Status Active?' is invoked, and assuming that no hold or proceed status conditions are active, when arrival status flag is active, the desired outcome is that set final status to arrived.
💻 Technical Criteria
Given No hold or proceed status conditions are active
When Arrival status flag is active
Then Set final status to ARRIVED
R-GCX016E-cbl-03559 Hold Combination Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Hold Combination Valid?' is invoked, and assuming that hold combination rules have been evaluated, when the system checks combination validity, the desired outcome is that the system returns true if the hold combination is valid, false if it violates business rules.
💻 Technical Criteria
Given Hold combination rules have been evaluated
When The system checks combination validity
Then The system returns true if the hold combination is valid, false if it violates business rules
R-GCX016E-cbl-03561 FDA Hold Takes Priority?
Policy Rules
📊 Business Logic Narrative
When the process 'FDA Hold Takes Priority?' is invoked, and assuming that fda hold is present along with other hold types, when the system evaluates hold priority, the desired outcome is that the system returns true if fda hold takes priority over other holds, false otherwise.
💻 Technical Criteria
Given FDA hold is present along with other hold types
When The system evaluates hold priority
Then The system returns true if FDA hold takes priority over other holds, false otherwise
R-GCX016E-cbl-03569 Conflicting Holds Detected?
Validation Rules
📊 Business Logic Narrative
When the process 'Conflicting Holds Detected?' is invoked, and assuming that hold combination validation has been performed, when the system checks for conflicting holds, the desired outcome is that the system returns true if conflicting holds are detected, false otherwise.
💻 Technical Criteria
Given Hold combination validation has been performed
When The system checks for conflicting holds
Then The system returns true if conflicting holds are detected, false otherwise
R-GCX016E-cbl-03570 Generate Hold Conflict Warning
Action Rules
📊 Business Logic Narrative
When the process 'Generate Hold Conflict Warning' is invoked, and assuming that conflicting holds have been detected, when the system processes the conflict, the desired outcome is that the system generates a hold conflict warning message for operational review.
💻 Technical Criteria
Given Conflicting holds have been detected
When The system processes the conflict
Then The system generates a hold conflict warning message for operational review
R-GCX016E-cbl-03571 Apply Default Hold Hierarchy
Policy Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Apply Default Hold Hierarchy', assuming that standard hold priority rules do not determine a clear status or conflicts exist, when the system applies default hierarchy rules, the desired outcome is that the system applies the default hold hierarchy to determine the final hold status.
💻 Technical Criteria
EXCLUDING Standard hold priority rules do not determine a clear status or conflicts exist
When The system applies default hierarchy rules
Then The system applies the default hold hierarchy to determine the final hold status
R-GCX016E-cbl-03572 Validate Final Hold Status
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Final Hold Status' is invoked, and assuming that a final hold status has been determined, when the system validates the final status, the desired outcome is that the system confirms the final hold status meets all business rules and regulatory requirements.
💻 Technical Criteria
Given A final hold status has been determined
When The system validates the final status
Then The system confirms the final hold status meets all business rules and regulatory requirements
R-GCX016E-cbl-02394 Other Hold Types?
Decision Rules
📊 Business Logic Narrative
When the process 'Other Hold Types?' is invoked, and assuming that various hold types check has been completed, when the system evaluates additional hold results, the desired outcome is that regardless of other hold type results, proceed to release eligibility evaluation.
💻 Technical Criteria
Given Various hold types check has been completed
When The system evaluates additional hold results
Then Regardless of other hold type results, proceed to release eligibility evaluation
R-GCX016E-cbl-03317 Extract SCAC Code from M10
Process Rules
📊 Business Logic Narrative
When the process 'Extract SCAC Code from M10' is invoked, and assuming that an m10 segment is received with manifest data, when the system processes the m10 segment, the desired outcome is that the scac code is extracted from positions 3-6 of the m10 segment.
💻 Technical Criteria
Given An M10 segment is received with manifest data
When The system processes the M10 segment
Then The SCAC code is extracted from positions 3-6 of the M10 segment
R-GCX016E-cbl-03323 Extract Vessel Name
Process Rules
📊 Business Logic Narrative
When the process 'Extract Vessel Name' is invoked, and assuming that an m10 segment with valid country code is being processed, when the system extracts vessel name information, the desired outcome is that the vessel name is extracted from positions 7-16 of the m10 segment.
💻 Technical Criteria
Given An M10 segment with valid country code is being processed
When The system extracts vessel name information
Then The vessel name is extracted from positions 7-16 of the M10 segment
R-GCX016E-cbl-03324 Extract Vessel Details
Process Rules
📊 Business Logic Narrative
When the process 'Extract Vessel Details' is invoked, and assuming that a vessel name has been extracted from the m10 segment, when the system extracts additional vessel details, the desired outcome is that voyage number, vessel flag, and other vessel identifiers are extracted from their respective positions in the m10 segment.
💻 Technical Criteria
Given A vessel name has been extracted from the M10 segment
When The system extracts additional vessel details
Then Voyage number, vessel flag, and other vessel identifiers are extracted from their respective positions in the M10 segment
R-GCX016E-cbl-03329 Set Manifest Data Fields
Process Rules
📊 Business Logic Narrative
When the process 'Set Manifest Data Fields' is invoked, and assuming that a foreign manifest structure has been built, when the system sets manifest data fields, the desired outcome is that all extracted data elements are assigned to their corresponding fields in the manifest record.
💻 Technical Criteria
Given A foreign manifest structure has been built
When The system sets manifest data fields
Then All extracted data elements are assigned to their corresponding fields in the manifest record
R-GCX016E-cbl-03332 Generate Error Message
Process Rules
📊 Business Logic Narrative
When the process 'Generate Error Message' is invoked, and assuming that manifest validation has failed for any required field, when the system generates an error message, the desired outcome is that a descriptive error message is created indicating the specific validation failure and the manifest is marked as invalid.
💻 Technical Criteria
Given Manifest validation has failed for any required field
When The system generates an error message
Then A descriptive error message is created indicating the specific validation failure and the manifest is marked as invalid
R-GCX016E-cbl-03455 Extract Vessel Details
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Vessel Details' is invoked, and assuming that country code has been mapped from m10 segment, when the system processes vessel information fields from m10 segment, the desired outcome is that vessel name and identification details are extracted and prepared for manifest structure.
💻 Technical Criteria
Given Country code has been mapped from M10 segment
When The system processes vessel information fields from M10 segment
Then Vessel name and identification details are extracted and prepared for manifest structure
R-GCX016E-cbl-03459 Validate Field Mappings
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Field Mappings' is invoked, and assuming that date information has been mapped from m10 segment, when the system validates all mapped fields for completeness and accuracy, the desired outcome is that all field mappings are verified for data integrity and business rule compliance.
💻 Technical Criteria
Given Date information has been mapped from M10 segment
When The system validates all mapped fields for completeness and accuracy
Then All field mappings are verified for data integrity and business rule compliance
R-GCX016E-cbl-03460 All Fields Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'All Fields Valid?' is invoked, and assuming that field mappings have been validated, when the system evaluates the validation results, the desired outcome is that the system determines if all fields are valid and processing can continue or if error handling is required.
💻 Technical Criteria
Given Field mappings have been validated
When The system evaluates the validation results
Then The system determines if all fields are valid and processing can continue or if error handling is required
R-GCX016E-cbl-03461 Set Error Flag
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Error Flag', assuming that field mapping validation has failed, when the system detects invalid or missing field mappings, the desired outcome is that an error flag is set to indicate foreign manifest processing cannot continue normally.
💻 Technical Criteria
EXCLUDING Field mapping validation has failed
When The system detects invalid or missing field mappings
Then An error flag is set to indicate foreign manifest processing cannot continue normally
R-GCX016E-cbl-03463 Store Foreign Manifest Data
Action Rules
📊 Business Logic Narrative
When the process 'Store Foreign Manifest Data' is invoked, and assuming that complete foreign manifest structure has been built, when the system stores the foreign manifest data, the desired outcome is that the foreign manifest data structure is stored and available for further processing operations.
💻 Technical Criteria
Given Complete foreign manifest structure has been built
When The system stores the foreign manifest data
Then The foreign manifest data structure is stored and available for further processing operations
R-GCX016E-cbl-02435 Extract SCAC Code from M10
Process Rules
📊 Business Logic Narrative
When the process 'Extract SCAC Code from M10' is invoked, and assuming that an m10 segment containing carrier information is received, when the system processes the m10 segment for foreign manifest building, the desired outcome is that the scac code is extracted from the m10 segment and stored for manifest construction.
💻 Technical Criteria
Given An M10 segment containing carrier information is received
When The system processes the M10 segment for foreign manifest building
Then The SCAC code is extracted from the M10 segment and stored for manifest construction
R-GCX016E-cbl-02437 Extract Country Code from M10
Process Rules
📊 Business Logic Narrative
When the process 'Extract Country Code from M10' is invoked, and assuming that an m10 segment containing country information is received, when the system processes the m10 segment for foreign manifest building, the desired outcome is that the country code is extracted from the m10 segment and stored for manifest construction.
💻 Technical Criteria
Given An M10 segment containing country information is received
When The system processes the M10 segment for foreign manifest building
Then The country code is extracted from the M10 segment and stored for manifest construction
R-GCX016E-cbl-02438 Extract Vessel Details from M10
Process Rules
📊 Business Logic Narrative
When the process 'Extract Vessel Details from M10' is invoked, and assuming that an m10 segment containing vessel information is received, when the system processes the m10 segment for foreign manifest building, the desired outcome is that the vessel details including name and identification are extracted from the m10 segment and stored for manifest construction.
💻 Technical Criteria
Given An M10 segment containing vessel information is received
When The system processes the M10 segment for foreign manifest building
Then The vessel details including name and identification are extracted from the M10 segment and stored for manifest construction
R-GCX016E-cbl-02439 Validate SCAC Information
Validation Rules
📊 Business Logic Narrative
When the process 'Validate SCAC Information' is invoked, and assuming that a scac code has been extracted from the m10 segment, when the system validates the scac information for foreign manifest building, the desired outcome is that the scac code is checked for validity and completeness according to business rules.
💻 Technical Criteria
Given A SCAC code has been extracted from the M10 segment
When The system validates the SCAC information for foreign manifest building
Then The SCAC code is checked for validity and completeness according to business rules
R-GCX016E-cbl-02441 Extract Vessel Name/ID
Process Rules
📊 Business Logic Narrative
When the process 'Extract Vessel Name/ID' is invoked, and assuming that vessel details have been extracted from the m10 segment, when the system processes vessel information for foreign manifest building, the desired outcome is that the vessel name and identification are extracted and prepared for manifest structure.
💻 Technical Criteria
Given Vessel details have been extracted from the M10 segment
When The system processes vessel information for foreign manifest building
Then The vessel name and identification are extracted and prepared for manifest structure
R-GCX016E-cbl-02442 Extract Voyage Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Voyage Information' is invoked, and assuming that vessel information has been processed from the m10 segment, when the system extracts voyage details for foreign manifest building, the desired outcome is that voyage information is extracted and prepared for inclusion in the manifest structure.
💻 Technical Criteria
Given Vessel information has been processed from the M10 segment
When The system extracts voyage details for foreign manifest building
Then Voyage information is extracted and prepared for inclusion in the manifest structure
R-GCX016E-cbl-02445 Set Country of Origin
Process Rules
📊 Business Logic Narrative
When the process 'Set Country of Origin' is invoked, and assuming that country code has been extracted from the m10 segment and foreign manifest structure is being built, when the system sets country of origin in the manifest, the desired outcome is that country of origin information is properly configured in the foreign manifest structure.
💻 Technical Criteria
Given Country code has been extracted from the M10 segment and foreign manifest structure is being built
When The system sets country of origin in the manifest
Then Country of origin information is properly configured in the foreign manifest structure
R-GCX016E-cbl-02446 Validate Manifest Completeness
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Manifest Completeness' is invoked, and assuming that a foreign manifest structure has been built with extracted m10 segment information, when the system validates manifest completeness, the desired outcome is that all required manifest fields are checked for presence and validity.
💻 Technical Criteria
Given A foreign manifest structure has been built with extracted M10 segment information
When The system validates manifest completeness
Then All required manifest fields are checked for presence and validity
R-GCX016E-cbl-02447 Log Missing Information Warning
Decision Rules
📊 Business Logic Narrative
When the process 'Log Missing Information Warning' is invoked, and assuming that a foreign manifest has been validated and found to be incomplete, when required information is missing from the manifest, the desired outcome is that a warning is logged indicating the missing information details.
💻 Technical Criteria
Given A foreign manifest has been validated and found to be incomplete
When Required information is missing from the manifest
Then A warning is logged indicating the missing information details
R-GCX016E-cbl-02451 Retrieve Key Station Information
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Key Station Information' is invoked, and assuming that a key station lookup is required, when the system processes the key station request, the desired outcome is that the system accesses the ks table via gcctbio to retrieve key station information.
💻 Technical Criteria
Given A key station lookup is required
When The system processes the key station request
Then The system accesses the KS table via GCCTBIO to retrieve key station information
R-GCX016E-cbl-02453 Access KS Table via GCCTBIO
Action Rules
📊 Business Logic Narrative
When the process 'Access KS Table via GCCTBIO' is invoked, and assuming that key station information is needed, when the system calls gcctbio to access the ks table, the desired outcome is that the system retrieves station data from the ks table using the gcctbio interface.
💻 Technical Criteria
Given Key station information is needed
When The system calls GCCTBIO to access the KS table
Then The system retrieves station data from the KS table using the GCCTBIO interface
R-GCX016E-cbl-02458 Generate Station Not Found Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Station Not Found Error', assuming that a station lookup has been performed, when the requested station is not found in either ds or ks table, the desired outcome is that the system generates a station not found error and completes the station lookup process.
💻 Technical Criteria
EXCLUDING A station lookup has been performed
When The requested station is not found in either DS or KS table
Then The system generates a station not found error and completes the station lookup process
R-GCX016E-cbl-02460 Station Lookup Complete
Process Rules
📊 Business Logic Narrative
When the process 'Station Lookup Complete' is invoked, and assuming that station lookup processing has been performed with either successful station setup or error generation, when the station lookup process reaches completion, the desired outcome is that the system finalizes the station lookup operation and returns control to the calling process.
💻 Technical Criteria
Given Station lookup processing has been performed with either successful station setup or error generation
When The station lookup process reaches completion
Then The system finalizes the station lookup operation and returns control to the calling process
R-GCX016E-cbl-02466 Add Disposition Code Description
Process Rules
📊 Business Logic Narrative
When the process 'Add Disposition Code Description' is invoked, and assuming that disposition code details have been formatted, when a disposition code description is available in the system, the desired outcome is that the system adds the descriptive text explaining the disposition code action to the message.
💻 Technical Criteria
Given Disposition code details have been formatted
When A disposition code description is available in the system
Then The system adds the descriptive text explaining the disposition code action to the message
R-GCX016E-cbl-02472 Add Impact Description
Process Rules
📊 Business Logic Narrative
When the process 'Add Impact Description' is invoked, and assuming that before and after quantities have been shown, when impact description is needed for clarity, the desired outcome is that the system adds explanatory text describing whether quantities increased, decreased, or were modified.
💻 Technical Criteria
Given Before and after quantities have been shown
When Impact description is needed for clarity
Then The system adds explanatory text describing whether quantities increased, decreased, or were modified
R-GCX016E-cbl-02476 Process K1 Comments
Process Rules
📊 Business Logic Narrative
When the process 'Process K1 Comments' is invoked, and assuming that hold/release flags have been included in the message, when k1 comments processing is initiated, the desired outcome is that the system evaluates available k1 comments for potential inclusion.
💻 Technical Criteria
Given Hold/release flags have been included in the message
When K1 comments processing is initiated
Then The system evaluates available K1 comments for potential inclusion
R-GCX016E-cbl-02477 K1 Comments Available?
Decision Rules
📊 Business Logic Narrative
When the process 'K1 Comments Available?' is invoked, and assuming that k1 comments processing has been initiated, when the system evaluates k1 comment availability, the desired outcome is that the system determines if valid k1 comments exist for message inclusion.
💻 Technical Criteria
Given K1 comments processing has been initiated
When The system evaluates K1 comment availability
Then The system determines if valid K1 comments exist for message inclusion
R-GCX016E-cbl-02478 Add Free-Form Text Messages
Process Rules
📊 Business Logic Narrative
When the process 'Add Free-Form Text Messages' is invoked, and assuming that k1 comments are available for inclusion, when free-form text messages need to be added, the desired outcome is that the system formats and includes the k1 comment text in the message.
💻 Technical Criteria
Given K1 comments are available for inclusion
When Free-form text messages need to be added
Then The system formats and includes the K1 comment text in the message
R-GCX016E-cbl-02479 Include Processing Details
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Include Processing Details', assuming that free-form text messages have been added or k1 comments are not available, when processing details need to be included, the desired outcome is that the system adds relevant processing details and context information to the message.
💻 Technical Criteria
EXCLUDING Free-form text messages have been added or K1 comments are not available
When Processing details need to be included
Then The system adds relevant processing details and context information to the message
R-GCX016E-cbl-02484 Add USCS Processing Time
Process Rules
📊 Business Logic Narrative
When the process 'Add USCS Processing Time' is invoked, and assuming that date/time information formatting has been initiated, when uscs processing time is available, the desired outcome is that the system adds the uscs processing timestamp to the message.
💻 Technical Criteria
Given Date/time information formatting has been initiated
When USCS processing time is available
Then The system adds the USCS processing timestamp to the message
R-GCX016E-cbl-02485 Add System Processing Time
Process Rules
📊 Business Logic Narrative
When the process 'Add System Processing Time' is invoked, and assuming that uscs processing time has been added, when system processing time needs to be recorded, the desired outcome is that the system adds the internal processing timestamp to the message.
💻 Technical Criteria
Given USCS processing time has been added
When System processing time needs to be recorded
Then The system adds the internal processing timestamp to the message
R-GCX016E-cbl-02487 Set Message Type and Priority
Process Rules
📊 Business Logic Narrative
When the process 'Set Message Type and Priority' is invoked, and assuming that message content has been finalized, when message attributes need to be set, the desired outcome is that the system assigns the appropriate message type and priority level for proper routing and handling.
💻 Technical Criteria
Given Message content has been finalized
When Message attributes need to be set
Then The system assigns the appropriate message type and priority level for proper routing and handling
R-GCX016E-cbl-02488 Complete Merlin Message
Process Rules
📊 Business Logic Narrative
When the process 'Complete Merlin Message' is invoked, and assuming that message type and priority have been set, when final message assembly is required, the desired outcome is that the system completes the merlin message with all formatted content, ready for transmission.
💻 Technical Criteria
Given Message type and priority have been set
When Final message assembly is required
Then The system completes the Merlin message with all formatted content, ready for transmission
R-GCX016E-cbl-02503 No Quantity Impact
Decision Rules
📊 Business Logic Narrative
When the process 'No Quantity Impact' is invoked, and assuming that a disposition code with status info only type is being processed, when the quantity impact evaluation is performed, the desired outcome is that no quantity calculations are performed and the release quantity remains unchanged.
💻 Technical Criteria
Given A disposition code with Status Info Only type is being processed
When The quantity impact evaluation is performed
Then No quantity calculations are performed and the release quantity remains unchanged
R-GCX016E-cbl-02504 Calculate Before/After Quantities
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Before/After Quantities' is invoked, and assuming that a disposition code with quantity impact has been processed, when before and after quantity calculation is performed, the desired outcome is that the system calculates and stores both the original quantity and the new quantity after disposition code impact.
💻 Technical Criteria
Given A disposition code with quantity impact has been processed
When Before and after quantity calculation is performed
Then The system calculates and stores both the original quantity and the new quantity after disposition code impact
R-GCX016E-cbl-02505 Format Quantity Impact Message
Process Rules
📊 Business Logic Narrative
When the process 'Format Quantity Impact Message' is invoked, and assuming that before and after quantities have been calculated for a disposition code, when quantity impact message formatting is initiated, the desired outcome is that a formatted message is created showing the quantity change details in business-friendly format.
💻 Technical Criteria
Given Before and after quantities have been calculated for a disposition code
When Quantity impact message formatting is initiated
Then A formatted message is created showing the quantity change details in business-friendly format
R-GCX016E-cbl-02507 Create Impact Description
Process Rules
📊 Business Logic Narrative
When the process 'Create Impact Description' is invoked, and assuming that a release quantity change has been detected, when impact description creation is initiated, the desired outcome is that a detailed description is created showing the specific quantity change amount and direction (increase/decrease).
💻 Technical Criteria
Given A release quantity change has been detected
When Impact description creation is initiated
Then A detailed description is created showing the specific quantity change amount and direction (increase/decrease)
R-GCX016E-cbl-02508 Add to Merlin Message
Action Rules
📊 Business Logic Narrative
When the process 'Add to Merlin Message' is invoked, and assuming that a quantity impact description has been created, when merlin message composition is in progress, the desired outcome is that the quantity impact information is added to the merlin message content for business user notification.
💻 Technical Criteria
Given A quantity impact description has been created
When Merlin message composition is in progress
Then The quantity impact information is added to the Merlin message content for business user notification
R-GCX016E-cbl-02527 Station Data Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Station Data Found?' is invoked, and assuming that a search for station information has been performed in the ds table, when the system checks if station data was found, the desired outcome is that if station data is found, format it for transit routing; if not found, generate station not found error.
💻 Technical Criteria
Given A search for station information has been performed in the DS table
When The system checks if station data was found
Then If station data is found, format it for transit routing; if not found, generate station not found error
R-GCX016E-cbl-02528 Format Station Information for Transit Routing
Process Rules
📊 Business Logic Narrative
When the process 'Format Station Information for Transit Routing' is invoked, and assuming that station data has been successfully retrieved from the ds table, when the system formats the station information, the desired outcome is that station information is formatted in the required structure for transit routing operations.
💻 Technical Criteria
Given Station data has been successfully retrieved from the DS table
When The system formats the station information
Then Station information is formatted in the required structure for transit routing operations
R-GCX016E-cbl-02529 Return Station Data to Calling Process
Process Rules
📊 Business Logic Narrative
When the process 'Return Station Data to Calling Process' is invoked, and assuming that station information has been successfully formatted for transit routing, when the processing is complete, the desired outcome is that the formatted station data is returned to the calling process.
💻 Technical Criteria
Given Station information has been successfully formatted for transit routing
When The processing is complete
Then The formatted station data is returned to the calling process
R-GCX016E-cbl-02537 Retrieve Station Information
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Station Information' is invoked, and assuming that a matching station record exists in the ds table, when the system processes the successful lookup result, the desired outcome is that the complete station information is retrieved from the ds table.
💻 Technical Criteria
Given A matching station record exists in the DS table
When The system processes the successful lookup result
Then The complete station information is retrieved from the DS table
R-GCX016E-cbl-02538 Extract Station Name and Details
Process Rules
📊 Business Logic Narrative
When the process 'Extract Station Name and Details' is invoked, and assuming that station information has been successfully retrieved from the ds table, when the system processes the retrieved station record, the desired outcome is that station name and relevant details are extracted from the record.
💻 Technical Criteria
Given Station information has been successfully retrieved from the DS table
When The system processes the retrieved station record
Then Station name and relevant details are extracted from the record
R-GCX016E-cbl-02554 Table Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Table Type?' is invoked, and assuming that a table data request is received, when the system evaluates the table type parameter, the desired outcome is that the request should be classified as either station data, broker information, or other table type.
💻 Technical Criteria
Given A table data request is received
When The system evaluates the table type parameter
Then The request should be classified as either station data, broker information, or other table type
R-GCX016E-cbl-02555 Station Data Lookup Request
Process Rules
📊 Business Logic Narrative
When the process 'Station Data Lookup Request' is invoked, and assuming that a request is classified as station data lookup, when the station data processing is initiated, the desired outcome is that the system should prepare to retrieve station-specific information from the table interface.
💻 Technical Criteria
Given A request is classified as station data lookup
When The station data processing is initiated
Then The system should prepare to retrieve station-specific information from the table interface
R-GCX016E-cbl-02556 Broker Information Request
Process Rules
📊 Business Logic Narrative
When the process 'Broker Information Request' is invoked, and assuming that a request is classified as broker information lookup, when the broker data processing is initiated, the desired outcome is that the system should prepare to retrieve broker-specific information from the table interface.
💻 Technical Criteria
Given A request is classified as broker information lookup
When The broker data processing is initiated
Then The system should prepare to retrieve broker-specific information from the table interface
R-GCX016E-cbl-02557 Other Table Type Request
Process Rules
📊 Business Logic Narrative
When the process 'Other Table Type Request' is invoked, and assuming that a request is classified as other table type, when the other table type processing is initiated, the desired outcome is that the system should prepare to retrieve the specified table information from the generic interface.
💻 Technical Criteria
Given A request is classified as other table type
When The other table type processing is initiated
Then The system should prepare to retrieve the specified table information from the generic interface
R-GCX016E-cbl-02558 Call GCCTBIO Interface
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCTBIO Interface' is invoked, and assuming that a table lookup request has been classified and prepared, when the gcctbio interface is called, the desired outcome is that the system should execute the table lookup operation through the external interface.
💻 Technical Criteria
Given A table lookup request has been classified and prepared
When The GCCTBIO interface is called
Then The system should execute the table lookup operation through the external interface
R-GCX016E-cbl-02560 Retrieve Key Station Data
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Key Station Data' is invoked, and assuming that a key station data request is processed through gcctbio, when the key station lookup is executed, the desired outcome is that the system should retrieve key station details from the gcstbrt table segments.
💻 Technical Criteria
Given A key station data request is processed through GCCTBIO
When The key station lookup is executed
Then The system should retrieve key station details from the GCSTBRT table segments
R-GCX016E-cbl-02561 Retrieve Broker Name Data
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Broker Name Data' is invoked, and assuming that a broker name data request is processed through gcctbio, when the broker name lookup is executed, the desired outcome is that the system should retrieve broker name details from the gcstbrt table segments.
💻 Technical Criteria
Given A broker name data request is processed through GCCTBIO
When The broker name lookup is executed
Then The system should retrieve broker name details from the GCSTBRT table segments
R-GCX016E-cbl-02562 Retrieve Broker Contact Data
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Broker Contact Data' is invoked, and assuming that a broker contact data request is processed through gcctbio, when the broker contact lookup is executed, the desired outcome is that the system should retrieve broker contact details from the gcstbrt table segments.
💻 Technical Criteria
Given A broker contact data request is processed through GCCTBIO
When The broker contact lookup is executed
Then The system should retrieve broker contact details from the GCSTBRT table segments
R-GCX016E-cbl-02563 Retrieve Other Table Data
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Other Table Data' is invoked, and assuming that an other table type request is processed through gcctbio, when the other table lookup is executed, the desired outcome is that the system should retrieve the requested table data from the appropriate table segments.
💻 Technical Criteria
Given An other table type request is processed through GCCTBIO
When The other table lookup is executed
Then The system should retrieve the requested table data from the appropriate table segments
R-GCX016E-cbl-02564 Data Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Data Found?' is invoked, and assuming that a table lookup operation has been completed, when the system checks the retrieval results, the desired outcome is that the system should determine if the requested data was found or not found.
💻 Technical Criteria
Given A table lookup operation has been completed
When The system checks the retrieval results
Then The system should determine if the requested data was found or not found
R-GCX016E-cbl-02566 Return Not Found Status
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Return Not Found Status', assuming that table data was not found during lookup, when the not found response process is executed, the desired outcome is that the system should return a not found status to the caller.
💻 Technical Criteria
EXCLUDING Table data was not found during lookup
When The not found response process is executed
Then The system should return a not found status to the caller
R-GCX016E-cbl-02567 Process Retrieved Information
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Process Retrieved Information', assuming that a table lookup operation has completed with either data found or not found status, when the information processing is initiated, the desired outcome is that the system should process the lookup results appropriately for the requesting operation.
💻 Technical Criteria
EXCLUDING A table lookup operation has completed with either data found or not found status
When The information processing is initiated
Then The system should process the lookup results appropriately for the requesting operation
R-GCX016E-cbl-02573 Add Disposition Description
Computation Rules
📊 Business Logic Narrative
When the process 'Add Disposition Description' is invoked, and assuming that disposition code has an associated description in the system, when building merlin message content, the desired outcome is that disposition description is added to provide clear understanding of the action being taken.
💻 Technical Criteria
Given Disposition code has an associated description in the system
When Building Merlin message content
Then Disposition description is added to provide clear understanding of the action being taken
R-GCX016E-cbl-02576 Add Quantity Impact Analysis
Computation Rules
📊 Business Logic Narrative
When the process 'Add Quantity Impact Analysis' is invoked, and assuming that disposition processing results in quantity changes, when before and after quantities are different, the desired outcome is that detailed quantity impact analysis showing the change is added to the merlin message.
💻 Technical Criteria
Given Disposition processing results in quantity changes
When Before and after quantities are different
Then Detailed quantity impact analysis showing the change is added to the Merlin message
R-GCX016E-cbl-02586 Format Complete Message
Computation Rules
📊 Business Logic Narrative
When the process 'Format Complete Message' is invoked, and assuming that all message components have been prepared and validated, when finalizing message creation process, the desired outcome is that complete merlin message is formatted with all required components in proper structure.
💻 Technical Criteria
Given All message components have been prepared and validated
When Finalizing message creation process
Then Complete Merlin message is formatted with all required components in proper structure
R-GCX016E-cbl-02587 Set Message Type and Priority
Decision Rules
📊 Business Logic Narrative
When the process 'Set Message Type and Priority' is invoked, and assuming that complete message content has been formatted, when preparing message for distribution, the desired outcome is that message type and priority are set based on disposition code and processing context.
💻 Technical Criteria
Given Complete message content has been formatted
When Preparing message for distribution
Then Message type and priority are set based on disposition code and processing context
R-GCX016E-cbl-02588 Prepare for Distribution
Process Rules
📊 Business Logic Narrative
When the process 'Prepare for Distribution' is invoked, and assuming that message type and priority have been set, when finalizing message preparation, the desired outcome is that message is prepared for distribution with proper routing and delivery information.
💻 Technical Criteria
Given Message type and priority have been set
When Finalizing message preparation
Then Message is prepared for distribution with proper routing and delivery information
R-GCX016E-cbl-02608 Format After Quantity Display
Process Rules
📊 Business Logic Narrative
When the process 'Format After Quantity Display' is invoked, and assuming that new release quantity calculated after disposition code processing, when the system prepares quantity impact messaging, the desired outcome is that the new quantity is formatted for display as the 'after' quantity in impact messages.
💻 Technical Criteria
Given New release quantity calculated after disposition code processing
When The system prepares quantity impact messaging
Then The new quantity is formatted for display as the 'after' quantity in impact messages
R-GCX016E-cbl-02609 Create Quantity Impact Message
Process Rules
📊 Business Logic Narrative
When the process 'Create Quantity Impact Message' is invoked, and assuming that formatted before and after quantity displays, when the system generates quantity impact messaging, the desired outcome is that a quantity impact message is created showing the quantity change from disposition code processing.
💻 Technical Criteria
Given Formatted before and after quantity displays
When The system generates quantity impact messaging
Then A quantity impact message is created showing the quantity change from disposition code processing
R-GCX016E-cbl-02610 Include in Merlin Message?
Decision Rules
📊 Business Logic Narrative
When the process 'Include in Merlin Message?' is invoked, and assuming that a quantity impact message and merlin message configuration rules, when the system evaluates whether to include quantity impact details in merlin notifications, the desired outcome is that the system includes impact details in the merlin message if configuration rules require it, otherwise finalizes the message without impact details.
💻 Technical Criteria
Given A quantity impact message and Merlin message configuration rules
When The system evaluates whether to include quantity impact details in Merlin notifications
Then The system includes impact details in the Merlin message if configuration rules require it, otherwise finalizes the message without impact details
R-GCX016E-cbl-02611 Add Impact Details to Message
Process Rules
📊 Business Logic Narrative
When the process 'Add Impact Details to Message' is invoked, and assuming that a merlin message and quantity impact details that should be included, when the system processes merlin message formatting with quantity impact inclusion, the desired outcome is that the quantity impact details are added to the merlin message content.
💻 Technical Criteria
Given A Merlin message and quantity impact details that should be included
When The system processes Merlin message formatting with quantity impact inclusion
Then The quantity impact details are added to the Merlin message content
R-GCX016E-cbl-02612 Format Complete Impact Statement
Process Rules
📊 Business Logic Narrative
When the process 'Format Complete Impact Statement' is invoked, and assuming that quantity impact details and disposition code information, when the system creates comprehensive impact messaging, the desired outcome is that a complete impact statement is formatted showing both the disposition code action and its quantity effects.
💻 Technical Criteria
Given Quantity impact details and disposition code information
When The system creates comprehensive impact messaging
Then A complete impact statement is formatted showing both the disposition code action and its quantity effects
R-GCX016E-cbl-02614 Finalize Release Quantity Impact Message
Process Rules
📊 Business Logic Narrative
When the process 'Finalize Release Quantity Impact Message' is invoked, and assuming that all quantity impact message components including before/after quantities, disposition code details, and optional k1 comments, when the system completes quantity impact message processing, the desired outcome is that the release quantity impact message is finalized with all components properly formatted and ready for delivery.
💻 Technical Criteria
Given All quantity impact message components including before/after quantities, disposition code details, and optional K1 comments
When The system completes quantity impact message processing
Then The release quantity impact message is finalized with all components properly formatted and ready for delivery
R-GCX016E-cbl-02628 Update Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Update Successful?' is invoked, and assuming that a status update has been sent to gcciis, when the system receives response from gcciis regarding the update, the desired outcome is that the system determines if the update was successful or failed based on gcciis response.
💻 Technical Criteria
Given A status update has been sent to GCCIIS
When The system receives response from GCCIIS regarding the update
Then The system determines if the update was successful or failed based on GCCIIS response
R-GCX016E-cbl-02629 Log Successful Integration
Process Rules
📊 Business Logic Narrative
When the process 'Log Successful Integration' is invoked, and assuming that a gcciis status update has been successfully processed, when the system processes the successful integration, the desired outcome is that the system records the successful gcciis integration for audit trail.
💻 Technical Criteria
Given A GCCIIS status update has been successfully processed
When The system processes the successful integration
Then The system records the successful GCCIIS integration for audit trail
R-GCX016E-cbl-02630 Handle Integration Error
Process Rules
📊 Business Logic Narrative
When the process 'Handle Integration Error' is invoked, and assuming that a gcciis status update has failed or encountered an error, when the system processes the integration failure, the desired outcome is that the system handles the error condition and takes appropriate corrective action.
💻 Technical Criteria
Given A GCCIIS status update has failed or encountered an error
When The system processes the integration failure
Then The system handles the error condition and takes appropriate corrective action
R-GCX016E-cbl-02631 Search Broker Database for Freight Forwarder Codes
Decision Rules
📊 Business Logic Narrative
When the process 'Search Broker Database for Freight Forwarder Codes' is invoked, and assuming that a disposition code is received for processing, when the system searches the broker database for freight forwarder-specific disposition codes, the desired outcome is that the system determines if the disposition code requires freight forwarder processing.
💻 Technical Criteria
Given A disposition code is received for processing
When The system searches the broker database for freight forwarder-specific disposition codes
Then The system determines if the disposition code requires freight forwarder processing
R-GCX016E-cbl-02636 Retrieve Freight Forwarder Contact Details
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Freight Forwarder Contact Details' is invoked, and assuming that freight forwarder has been identified in the broker name tables, when the system needs to send notifications to the freight forwarder, the desired outcome is that the system retrieves complete contact details including email addresses and notification preferences.
💻 Technical Criteria
Given Freight forwarder has been identified in the broker name tables
When The system needs to send notifications to the freight forwarder
Then The system retrieves complete contact details including email addresses and notification preferences
R-GCX016E-cbl-02637 Mark as Freight Forwarder Disposition Code
Process Rules
📊 Business Logic Narrative
When the process 'Mark as Freight Forwarder Disposition Code' is invoked, and assuming that freight forwarder information has been successfully retrieved and validated, when the disposition code processing continues, the desired outcome is that the system marks the disposition code as requiring freight forwarder notification processing.
💻 Technical Criteria
Given Freight forwarder information has been successfully retrieved and validated
When The disposition code processing continues
Then The system marks the disposition code as requiring freight forwarder notification processing
R-GCX016E-cbl-02638 Continue with Standard Disposition Processing
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Continue with Standard Disposition Processing', assuming that a disposition code is not identified as freight forwarder-related or freight forwarder processing is complete, when the system continues disposition code processing, the desired outcome is that the system proceeds with standard disposition code processing workflow.
💻 Technical Criteria
EXCLUDING A disposition code is not identified as freight forwarder-related OR freight forwarder processing is complete
When The system continues disposition code processing
Then The system proceeds with standard disposition code processing workflow
R-GCX016E-cbl-02641 GCSUSS03 Found?
Validation Rules
📊 Business Logic Narrative
When the process 'GCSUSS03 Found?' is invoked, and assuming that the system has attempted to retrieve the gcsuss03 segment, when the retrieval operation is completed, the desired outcome is that the system determines if the gcsuss03 segment was found and proceeds accordingly.
💻 Technical Criteria
Given The system has attempted to retrieve the GCSUSS03 segment
When The retrieval operation is completed
Then The system determines if the GCSUSS03 segment was found and proceeds accordingly
R-GCX016E-cbl-02644 GCSUSS07 Found?
Validation Rules
📊 Business Logic Narrative
When the process 'GCSUSS07 Found?' is invoked, and assuming that the system has attempted to retrieve the gcsuss07 segment, when the retrieval operation is completed, the desired outcome is that the system determines if the gcsuss07 segment was found and proceeds accordingly.
💻 Technical Criteria
Given The system has attempted to retrieve the GCSUSS07 segment
When The retrieval operation is completed
Then The system determines if the GCSUSS07 segment was found and proceeds accordingly
R-GCX016E-cbl-02645 Extract Additional Freight Forwarder Data from GCSUSS07
Process Rules
📊 Business Logic Narrative
When the process 'Extract Additional Freight Forwarder Data from GCSUSS07' is invoked, and assuming that the gcsuss07 segment has been successfully retrieved, when the system processes the gcsuss07 segment data, the desired outcome is that additional freight forwarder data is extracted from the gcsuss07 segment.
💻 Technical Criteria
Given The GCSUSS07 segment has been successfully retrieved
When The system processes the GCSUSS07 segment data
Then Additional freight forwarder data is extracted from the GCSUSS07 segment
R-GCX016E-cbl-02646 Compile Freight Forwarder Information
Process Rules
📊 Business Logic Narrative
When the process 'Compile Freight Forwarder Information' is invoked, and assuming that freight forwarder data has been extracted from available segments (gcsuss03 and/or gcsuss07), when the system processes the extracted data, the desired outcome is that all available freight forwarder information is compiled into a consolidated format.
💻 Technical Criteria
Given Freight forwarder data has been extracted from available segments (GCSUSS03 and/or GCSUSS07)
When The system processes the extracted data
Then All available freight forwarder information is compiled into a consolidated format
R-GCX016E-cbl-02648 Valid Freight Forwarder?
Decision Rules
📊 Business Logic Narrative
When the process 'Valid Freight Forwarder?' is invoked, and assuming that freight forwarder data has been validated, when the validation process is completed, the desired outcome is that the system determines if the freight forwarder information is valid and complete.
💻 Technical Criteria
Given Freight forwarder data has been validated
When The validation process is completed
Then The system determines if the freight forwarder information is valid and complete
R-GCX016E-cbl-02649 Set Freight Forwarder Identified Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Freight Forwarder Identified Flag' is invoked, and assuming that the freight forwarder information has been validated as complete and accurate, when the system processes the validation result, the desired outcome is that a freight forwarder identified flag is set to indicate successful identification.
💻 Technical Criteria
Given The freight forwarder information has been validated as complete and accurate
When The system processes the validation result
Then A freight forwarder identified flag is set to indicate successful identification
R-GCX016E-cbl-02650 Log Freight Forwarder Not Found
Process Rules
📊 Business Logic Narrative
When the process 'Log Freight Forwarder Not Found' is invoked, and assuming that the freight forwarder information has been validated as incomplete or invalid, when the system processes the validation result, the desired outcome is that a log entry is created indicating that freight forwarder information was not found or is invalid.
💻 Technical Criteria
Given The freight forwarder information has been validated as incomplete or invalid
When The system processes the validation result
Then A log entry is created indicating that freight forwarder information was not found or is invalid
R-GCX016E-cbl-02651 Return Freight Forwarder Information
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Return Freight Forwarder Information', assuming that freight forwarder processing has been completed with either successful identification or logging of not found status, when the system completes the freight forwarder data retrieval process, the desired outcome is that the freight forwarder information (or indication of not found) is returned to the calling process.
💻 Technical Criteria
EXCLUDING Freight forwarder processing has been completed with either successful identification or logging of not found status
When The system completes the freight forwarder data retrieval process
Then The freight forwarder information (or indication of not found) is returned to the calling process
R-GCX016E-cbl-02654 Search Broker Database by FF Code
Action Rules
📊 Business Logic Narrative
When the process 'Search Broker Database by FF Code' is invoked, and assuming that a valid freight forwarder code exists, when the system searches the broker database using the freight forwarder code, the desired outcome is that the system queries the broker database tables to find matching broker records.
💻 Technical Criteria
Given A valid freight forwarder code exists
When The system searches the broker database using the freight forwarder code
Then The system queries the broker database tables to find matching broker records
R-GCX016E-cbl-02655 Broker Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Broker Record Found?' is invoked, and assuming that broker database search has been performed using freight forwarder code, when the system evaluates search results, the desired outcome is that if broker record is found, proceed to retrieve broker name; otherwise log broker information not found.
💻 Technical Criteria
Given Broker database search has been performed using freight forwarder code
When The system evaluates search results
Then If broker record is found, proceed to retrieve broker name; otherwise log broker information not found
R-GCX016E-cbl-02656 Retrieve Broker Name from GCST2RT
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Broker Name from GCST2RT' is invoked, and assuming that a valid broker record has been found in the database, when the system accesses gcst2rt table, the desired outcome is that the broker name is retrieved from the gcst2rt broker name segments.
💻 Technical Criteria
Given A valid broker record has been found in the database
When The system accesses GCST2RT table
Then The broker name is retrieved from the GCST2RT broker name segments
R-GCX016E-cbl-02657 Retrieve Associated Broker Information
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Associated Broker Information' is invoked, and assuming that broker name has been successfully retrieved from gcst2rt, when the system accesses gcstbrt broker information tables, the desired outcome is that associated broker information including contact details is retrieved.
💻 Technical Criteria
Given Broker name has been successfully retrieved from GCST2RT
When The system accesses GCSTBRT broker information tables
Then Associated broker information including contact details is retrieved
R-GCX016E-cbl-02658 Extract Freight Forwarder Name
Process Rules
📊 Business Logic Narrative
When the process 'Extract Freight Forwarder Name' is invoked, and assuming that associated broker information has been retrieved, when the system processes the broker information data, the desired outcome is that the freight forwarder name is extracted from the broker information.
💻 Technical Criteria
Given Associated broker information has been retrieved
When The system processes the broker information data
Then The freight forwarder name is extracted from the broker information
R-GCX016E-cbl-02659 Extract Broker Contact Details
Process Rules
📊 Business Logic Narrative
When the process 'Extract Broker Contact Details' is invoked, and assuming that freight forwarder name has been extracted, when the system continues processing broker information, the desired outcome is that broker contact details are extracted from the broker information data.
💻 Technical Criteria
Given Freight forwarder name has been extracted
When The system continues processing broker information
Then Broker contact details are extracted from the broker information data
R-GCX016E-cbl-02660 Store FF Name and Broker Info
Process Rules
📊 Business Logic Narrative
When the process 'Store FF Name and Broker Info' is invoked, and assuming that freight forwarder name and broker contact details have been extracted, when the system completes information extraction, the desired outcome is that the freight forwarder name and broker information are stored in system variables.
💻 Technical Criteria
Given Freight forwarder name and broker contact details have been extracted
When The system completes information extraction
Then The freight forwarder name and broker information are stored in system variables
R-GCX016E-cbl-02661 Set Lookup Success Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Lookup Success Flag' is invoked, and assuming that freight forwarder name and broker information have been successfully stored, when the lookup process completes successfully, the desired outcome is that the system sets the lookup success flag to indicate successful completion.
💻 Technical Criteria
Given Freight forwarder name and broker information have been successfully stored
When The lookup process completes successfully
Then The system sets the lookup success flag to indicate successful completion
R-GCX016E-cbl-02662 Set Lookup Failed Flag
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Lookup Failed Flag', assuming that either freight forwarder code is not found or broker information lookup fails, when the lookup process cannot be completed successfully, the desired outcome is that the system sets the lookup failed flag to indicate unsuccessful completion.
💻 Technical Criteria
EXCLUDING Either freight forwarder code is not found or broker information lookup fails
When The lookup process cannot be completed successfully
Then The system sets the lookup failed flag to indicate unsuccessful completion
R-GCX016E-cbl-02663 Log Broker Information Not Found
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Broker Information Not Found', assuming that broker database search has been performed but no matching broker record was found, when the system determines that broker information is not available, the desired outcome is that the system logs that broker information was not found for the freight forwarder code.
💻 Technical Criteria
EXCLUDING Broker database search has been performed but no matching broker record was found
When The system determines that broker information is not available
Then The system logs that broker information was not found for the freight forwarder code
R-GCX016E-cbl-02667 Retrieve Associated Broker Information
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Associated Broker Information' is invoked, and assuming that freight forwarder name has been found in broker database, when the system needs complete broker information, the desired outcome is that the system retrieves associated broker information including broker codes and identifiers.
💻 Technical Criteria
Given Freight forwarder name has been found in broker database
When The system needs complete broker information
Then The system retrieves associated broker information including broker codes and identifiers
R-GCX016E-cbl-02668 Access Broker Contact Table
Action Rules
📊 Business Logic Narrative
When the process 'Access Broker Contact Table' is invoked, and assuming that broker information has been retrieved, when the system needs contact information for notifications, the desired outcome is that the system accesses gcstbrt broker contact table using broker identifier.
💻 Technical Criteria
Given Broker information has been retrieved
When The system needs contact information for notifications
Then The system accesses GCSTBRT broker contact table using broker identifier
R-GCX016E-cbl-02669 Extract Email Addresses
Process Rules
📊 Business Logic Narrative
When the process 'Extract Email Addresses' is invoked, and assuming that broker contact table has been accessed, when the system processes contact information, the desired outcome is that the system extracts email addresses from the contact table records for notification purposes.
💻 Technical Criteria
Given Broker contact table has been accessed
When The system processes contact information
Then The system extracts email addresses from the contact table records for notification purposes
R-GCX016E-cbl-02670 Retrieve Additional Contact Information
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Additional Contact Information' is invoked, and assuming that email addresses have been extracted from contact table, when the system needs complete contact information, the desired outcome is that the system retrieves additional contact information such as phone numbers and addresses from the contact table.
💻 Technical Criteria
Given Email addresses have been extracted from contact table
When The system needs complete contact information
Then The system retrieves additional contact information such as phone numbers and addresses from the contact table
R-GCX016E-cbl-02671 Validate Contact Information
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Contact Information' is invoked, and assuming that contact information has been retrieved from broker contact table, when the system validates contact information, the desired outcome is that the system checks that required contact fields are present and properly formatted.
💻 Technical Criteria
Given Contact information has been retrieved from broker contact table
When The system validates contact information
Then The system checks that required contact fields are present and properly formatted
R-GCX016E-cbl-02673 Store Contact Information for Notifications
Process Rules
📊 Business Logic Narrative
When the process 'Store Contact Information for Notifications' is invoked, and assuming that contact information is complete and validated, when the system needs to store contact information, the desired outcome is that the system stores the contact information including email addresses for use in freight forwarder notifications.
💻 Technical Criteria
Given Contact information is complete and validated
When The system needs to store contact information
Then The system stores the contact information including email addresses for use in freight forwarder notifications
R-GCX016E-cbl-02674 Log Missing Contact Information Warning
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Missing Contact Information Warning', assuming that freight forwarder information is not available or contact information is incomplete, when the system cannot retrieve complete contact information, the desired outcome is that the system logs a warning message indicating missing or incomplete freight forwarder contact information.
💻 Technical Criteria
EXCLUDING Freight forwarder information is not available OR contact information is incomplete
When The system cannot retrieve complete contact information
Then The system logs a warning message indicating missing or incomplete freight forwarder contact information
R-GCX016E-cbl-02676 Freight Forwarder Code Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Freight Forwarder Code Found?' is invoked, and assuming that the broker database search has been completed, when the system evaluates the search results for freight forwarder codes, the desired outcome is that the system determines whether to proceed with email notification or terminate the process.
💻 Technical Criteria
Given The broker database search has been completed
When The system evaluates the search results for freight forwarder codes
Then The system determines whether to proceed with email notification or terminate the process
R-GCX016E-cbl-02681 Retrieve Email Address from GCSTBRT Table
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Email Address from GCSTBRT Table' is invoked, and assuming that a valid freight forwarder name has been found in the broker database, when the system accesses the gcstbrt broker table to retrieve email address information, the desired outcome is that the system obtains the freight forwarder's email address for notification delivery.
💻 Technical Criteria
Given A valid freight forwarder name has been found in the broker database
When The system accesses the GCSTBRT broker table to retrieve email address information
Then The system obtains the freight forwarder's email address for notification delivery
R-GCX016E-cbl-02689 Include Hold Reason Details
Process Rules
📊 Business Logic Narrative
When the process 'Include Hold Reason Details' is invoked, and assuming that cih disposition information has been included in the email content, when the system processes hold reason details for email inclusion, the desired outcome is that the system adds comprehensive hold reason details and explanations to complete the email notification content.
💻 Technical Criteria
Given CIH disposition information has been included in the email content
When The system processes hold reason details for email inclusion
Then The system adds comprehensive hold reason details and explanations to complete the email notification content
R-GCX016E-cbl-02690 Send Email Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send Email Notification' is invoked, and assuming that complete email content has been built with all required information, when the system initiates email delivery to the freight forwarder, the desired outcome is that the system sends the cih hold notification email to the specified recipient.
💻 Technical Criteria
Given Complete email content has been built with all required information
When The system initiates email delivery to the freight forwarder
Then The system sends the CIH hold notification email to the specified recipient
R-GCX016E-cbl-02691 Apply Retry Logic for Delivery Failures
Process Rules
📊 Business Logic Narrative
When the process 'Apply Retry Logic for Delivery Failures' is invoked, and assuming that an email notification has been sent to the freight forwarder, when the system encounters email delivery failures or issues, the desired outcome is that the system applies retry logic to attempt email delivery multiple times before considering it failed.
💻 Technical Criteria
Given An email notification has been sent to the freight forwarder
When The system encounters email delivery failures or issues
Then The system applies retry logic to attempt email delivery multiple times before considering it failed
R-GCX016E-cbl-02692 Email Delivery Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'Email Delivery Successful?' is invoked, and assuming that email delivery has been attempted with retry logic applied, when the system evaluates the final delivery status of the email notification, the desired outcome is that the system determines whether the email was successfully delivered or requires alternative handling.
💻 Technical Criteria
Given Email delivery has been attempted with retry logic applied
When The system evaluates the final delivery status of the email notification
Then The system determines whether the email was successfully delivered or requires alternative handling
R-GCX016E-cbl-02693 Log Successful Email Delivery
Process Rules
📊 Business Logic Narrative
When the process 'Log Successful Email Delivery' is invoked, and assuming that email notification has been successfully delivered to the freight forwarder, when the system processes the successful delivery confirmation, the desired outcome is that the system logs the successful email delivery with timestamp and recipient information for audit purposes.
💻 Technical Criteria
Given Email notification has been successfully delivered to the freight forwarder
When The system processes the successful delivery confirmation
Then The system logs the successful email delivery with timestamp and recipient information for audit purposes
R-GCX016E-cbl-02694 Handle Email Delivery Failure
Process Rules
📊 Business Logic Narrative
When the process 'Handle Email Delivery Failure' is invoked, and assuming that email notification delivery has failed after retry attempts, when the system processes the delivery failure, the desired outcome is that the system initiates alternative notification handling procedures.
💻 Technical Criteria
Given Email notification delivery has failed after retry attempts
When The system processes the delivery failure
Then The system initiates alternative notification handling procedures
R-GCX016E-cbl-02696 Log Email Processing Complete
Process Rules
📊 Business Logic Narrative
When the process 'Log Email Processing Complete' is invoked, and assuming that email processing has been completed either through successful delivery or fallback rerouting, when the system finalizes the email notification process, the desired outcome is that the system logs the completion of email processing with final status and actions taken.
💻 Technical Criteria
Given Email processing has been completed either through successful delivery or fallback rerouting
When The system finalizes the email notification process
Then The system logs the completion of email processing with final status and actions taken
R-GCX016E-cbl-02700 Delivery Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'Delivery Successful?' is invoked, and assuming that an email delivery attempt has been made, when the system checks the delivery status, the desired outcome is that if the delivery response indicates success, the process continues to success logging, otherwise it proceeds to retry logic.
💻 Technical Criteria
Given An email delivery attempt has been made
When The system checks the delivery status
Then If the delivery response indicates success, the process continues to success logging, otherwise it proceeds to retry logic
R-GCX016E-cbl-02701 Log Successful Delivery
Process Rules
📊 Business Logic Narrative
When the process 'Log Successful Delivery' is invoked, and assuming that email delivery has been confirmed as successful, when the system logs the successful delivery, the desired outcome is that a delivery success record is created with timestamp and recipient information for audit purposes.
💻 Technical Criteria
Given Email delivery has been confirmed as successful
When The system logs the successful delivery
Then A delivery success record is created with timestamp and recipient information for audit purposes
R-GCX016E-cbl-02704 Apply Retry Delay
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Apply Retry Delay', assuming that email delivery has failed and maximum retries have not been reached, when the system applies retry delay, the desired outcome is that a predetermined delay period is applied before the next delivery attempt.
💻 Technical Criteria
EXCLUDING Email delivery has failed and maximum retries have not been reached
When The system applies retry delay
Then A predetermined delay period is applied before the next delivery attempt
R-GCX016E-cbl-02705 Update Delivery Status
Process Rules
📊 Business Logic Narrative
When the process 'Update Delivery Status' is invoked, and assuming that retry delay has been applied, when the system updates delivery status, the desired outcome is that the delivery status is updated to indicate retry in progress and the system is ready for the next attempt.
💻 Technical Criteria
Given Retry delay has been applied
When The system updates delivery status
Then The delivery status is updated to indicate retry in progress and the system is ready for the next attempt
R-GCX016E-cbl-02706 Log Delivery Failure
Process Rules
📊 Business Logic Narrative
When the process 'Log Delivery Failure' is invoked, and assuming that maximum retry attempts have been reached without successful email delivery, when the system logs the delivery failure, the desired outcome is that a delivery failure record is created with error details and retry attempt count for troubleshooting purposes.
💻 Technical Criteria
Given Maximum retry attempts have been reached without successful email delivery
When The system logs the delivery failure
Then A delivery failure record is created with error details and retry attempt count for troubleshooting purposes
R-GCX016E-cbl-02709 Send to Default Recipient
Action Rules
📊 Business Logic Narrative
When the process 'Send to Default Recipient' is invoked, and assuming that alternative recipients are available for fallback delivery, when the system sends to default recipient, the desired outcome is that the email is delivered to the default recipient (om01247) with notification that original delivery failed.
💻 Technical Criteria
Given Alternative recipients are available for fallback delivery
When The system sends to default recipient
Then The email is delivered to the default recipient (OM01247) with notification that original delivery failed
R-GCX016E-cbl-02710 Log Final Failure
Process Rules
📊 Business Logic Narrative
When the process 'Log Final Failure' is invoked, and assuming that all email delivery attempts including alternative recipients have failed, when the system logs final failure, the desired outcome is that a final failure record is created indicating complete delivery failure with all attempted recipients and error details.
💻 Technical Criteria
Given All email delivery attempts including alternative recipients have failed
When The system logs final failure
Then A final failure record is created indicating complete delivery failure with all attempted recipients and error details
R-GCX016E-cbl-02719 Create Before/After Comparison
Process Rules
📊 Business Logic Narrative
When the process 'Create Before/After Comparison' is invoked, and assuming that both before and after status information has been captured, when the system completes status processing, the desired outcome is that a comparison is created highlighting status changes, quantity modifications, and disposition code updates.
💻 Technical Criteria
Given Both before and after status information has been captured
When The system completes status processing
Then A comparison is created highlighting status changes, quantity modifications, and disposition code updates
R-GCX016E-cbl-02720 Format Debug Message Content
Process Rules
📊 Business Logic Narrative
When the process 'Format Debug Message Content' is invoked, and assuming that all debug information has been captured, when the system prepares debug output, the desired outcome is that debug information is formatted into a structured message containing header, before/after status, and comparison data.
💻 Technical Criteria
Given All debug information has been captured
When The system prepares debug output
Then Debug information is formatted into a structured message containing header, before/after status, and comparison data
R-GCX016E-cbl-02722 Store Debug Log for Audit Trail
Process Rules
📊 Business Logic Narrative
When the process 'Store Debug Log for Audit Trail' is invoked, and assuming that debug logging has been completed, when the system finalizes debug processing, the desired outcome is that debug log information is stored in audit trail records with timestamps for compliance and historical reference.
💻 Technical Criteria
Given Debug logging has been completed
When The system finalizes debug processing
Then Debug log information is stored in audit trail records with timestamps for compliance and historical reference
R-GCX016E-cbl-02727 UNRLSE Message Type
Decision Rules
📊 Business Logic Narrative
When the process 'UNRLSE Message Type' is invoked, and assuming that a merlin message is ready for distribution and message type is unrlse, when the system processes the message routing, the desired outcome is that the message should be sent to om01247 and all valid sd cancel merlin ids.
💻 Technical Criteria
Given A Merlin message is ready for distribution and message type is UNRLSE
When The system processes the message routing
Then The message should be sent to OM01247 and all valid SD cancel Merlin IDs
R-GCX016E-cbl-02728 Check AD Segment Configuration
Validation Rules
📊 Business Logic Narrative
When the process 'Check AD Segment Configuration' is invoked, and assuming that a message type has been determined for a merlin message, when the system needs to identify message recipients, the desired outcome is that the ad segment configuration should be checked to find valid recipient merlin ids.
💻 Technical Criteria
Given A message type has been determined for a Merlin message
When The system needs to identify message recipients
Then The AD segment configuration should be checked to find valid recipient Merlin IDs
R-GCX016E-cbl-02729 Valid Recipient Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid Recipient Found?' is invoked, and assuming that ad segment configuration has been checked for a message, when the system evaluates recipient validity, the desired outcome is that if valid recipients are found, proceed with configured routing; if no valid recipients exist, use default routing.
💻 Technical Criteria
Given AD segment configuration has been checked for a message
When The system evaluates recipient validity
Then If valid recipients are found, proceed with configured routing; if no valid recipients exist, use default routing
R-GCX016E-cbl-02732 Generate Invalid Recipient Error
Validation Rules
📊 Business Logic Narrative
When the process 'Generate Invalid Recipient Error' is invoked, and assuming that an invalid recipient is detected in the routing configuration, when the system validates recipient information, the desired outcome is that an invalid recipient error should be generated for tracking and correction.
💻 Technical Criteria
Given An invalid recipient is detected in the routing configuration
When The system validates recipient information
Then An invalid recipient error should be generated for tracking and correction
R-GCX016E-cbl-02734 Log Distribution Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Distribution Action' is invoked, and assuming that a message has been successfully distributed to recipients, when the distribution process completes, the desired outcome is that the distribution action should be logged with relevant details for audit purposes.
💻 Technical Criteria
Given A message has been successfully distributed to recipients
When The distribution process completes
Then The distribution action should be logged with relevant details for audit purposes
R-GCX016E-cbl-02735 Handle Delivery Failure
Process Rules
📊 Business Logic Narrative
When the process 'Handle Delivery Failure' is invoked, and assuming that a message distribution has been attempted, when the delivery fails for any reason, the desired outcome is that the system should handle the delivery failure and determine if retry is required.
💻 Technical Criteria
Given A message distribution has been attempted
When The delivery fails for any reason
Then The system should handle the delivery failure and determine if retry is required
R-GCX016E-cbl-02744 Use AD Segment Configuration
Process Rules
📊 Business Logic Narrative
When the process 'Use AD Segment Configuration' is invoked, and assuming that a message recipient has been determined, when the recipient is valid, the desired outcome is that the system should use ad segment configuration for delivery.
💻 Technical Criteria
Given A message recipient has been determined
When The recipient is valid
Then The system should use AD segment configuration for delivery
R-GCX016E-cbl-02746 Generate Error Notification
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error Notification', assuming that a message has been sent to a recipient, when the delivery is not successful, the desired outcome is that the system should generate an error notification.
💻 Technical Criteria
EXCLUDING A message has been sent to a recipient
When The delivery is not successful
Then The system should generate an error notification
R-GCX016E-cbl-02748 Final Delivery Failure
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Final Delivery Failure', assuming that a message rerouting has been attempted, when the rerouting is not successful, the desired outcome is that the system should record a final delivery failure.
💻 Technical Criteria
EXCLUDING A message rerouting has been attempted
When The rerouting is not successful
Then The system should record a final delivery failure
R-GCX016E-cbl-02752 Capture User Information
Policy Rules
📊 Business Logic Narrative
When the process 'Capture User Information' is invoked, and assuming that an audit log entry is being prepared with timestamp information, when the system captures user information, the desired outcome is that the user identification and relevant user context are recorded in the audit log entry for accountability tracking.
💻 Technical Criteria
Given An audit log entry is being prepared with timestamp information
When The system captures user information
Then The user identification and relevant user context are recorded in the audit log entry for accountability tracking
R-GCX016E-cbl-02753 Set Action Code to LOG-USE-INPUT-MESSAGE
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Action Code to LOG-USE-INPUT-MESSAGE' is invoked, and assuming that an audit log entry has been prepared with timestamp and user information, when the system sets the action code for the audit log, the desired outcome is that the action code is set to log-use-input-message to indicate this is an input message logging action.
💻 Technical Criteria
Given An audit log entry has been prepared with timestamp and user information
When The system sets the action code for the audit log
Then The action code is set to LOG-USE-INPUT-MESSAGE to indicate this is an input message logging action
R-GCX016E-cbl-02754 Spawn GCT1051E Transaction
Action Rules
📊 Business Logic Narrative
When the process 'Spawn GCT1051E Transaction' is invoked, and assuming that an audit log entry is prepared with action code log-use-input-message, when the system spawns the gct1051e transaction, the desired outcome is that the gct1051e audit logging transaction is invoked to process the audit log entry.
💻 Technical Criteria
Given An audit log entry is prepared with action code LOG-USE-INPUT-MESSAGE
When The system spawns the GCT1051E transaction
Then The GCT1051E audit logging transaction is invoked to process the audit log entry
R-GCX016E-cbl-02755 Transaction Spawn Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Transaction Spawn Successful?' is invoked, and assuming that the gct1051e transaction has been spawned for audit logging, when the system checks the transaction spawn result, the desired outcome is that if the transaction spawn was successful, proceed to log audit entry creation, otherwise handle the logging error.
💻 Technical Criteria
Given The GCT1051E transaction has been spawned for audit logging
When The system checks the transaction spawn result
Then If the transaction spawn was successful, proceed to log audit entry creation, otherwise handle the logging error
R-GCX016E-cbl-02756 Log Audit Entry Created
Process Rules
📊 Business Logic Narrative
When the process 'Log Audit Entry Created' is invoked, and assuming that the gct1051e transaction spawn was successful, when the audit log entry is processed, the desired outcome is that the audit log entry is successfully created and recorded in the audit system for compliance tracking.
💻 Technical Criteria
Given The GCT1051E transaction spawn was successful
When The audit log entry is processed
Then The audit log entry is successfully created and recorded in the audit system for compliance tracking
R-GCX016E-cbl-02770 Does Disposition Code Affect Release Quantity?
Decision Rules
📊 Business Logic Narrative
When the process 'Does Disposition Code Affect Release Quantity?' is invoked, and assuming that a disposition code is being processed, when the system checks if the disposition code affects release quantities, the desired outcome is that the system returns true if the disposition code affects release quantities, false otherwise.
💻 Technical Criteria
Given A disposition code is being processed
When The system checks if the disposition code affects release quantities
Then The system returns true if the disposition code affects release quantities, false otherwise
R-GCX016E-cbl-02775 Valid Recipient in AD Segment?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid Recipient in AD Segment?' is invoked, and assuming that a merlin message is ready for distribution with a recipient configured in the ad segment, when the system checks the validity of the recipient in the ad segment, the desired outcome is that the system determines if the recipient is valid and proceeds accordingly.
💻 Technical Criteria
Given A Merlin message is ready for distribution with a recipient configured in the AD segment
When The system checks the validity of the recipient in the AD segment
Then The system determines if the recipient is valid and proceeds accordingly
R-GCX016E-cbl-02776 Use Configured Recipient
Decision Rules
📊 Business Logic Narrative
When the process 'Use Configured Recipient' is invoked, and assuming that a merlin message has a valid recipient configured in the ad segment, when the recipient validation passes successfully, the desired outcome is that the system uses the configured recipient for message delivery.
💻 Technical Criteria
Given A Merlin message has a valid recipient configured in the AD segment
When The recipient validation passes successfully
Then The system uses the configured recipient for message delivery
R-GCX016E-cbl-02777 Detect Invalid Recipient
Validation Rules
📊 Business Logic Narrative
When the process 'Detect Invalid Recipient' is invoked, and assuming that a merlin message has an invalid recipient configured in the ad segment, when the recipient validation fails, the desired outcome is that the system detects the invalid recipient and generates an error notification.
💻 Technical Criteria
Given A Merlin message has an invalid recipient configured in the AD segment
When The recipient validation fails
Then The system detects the invalid recipient and generates an error notification
R-GCX016E-cbl-02778 Set Default Recipient OM01247
Decision Rules
📊 Business Logic Narrative
When the process 'Set Default Recipient OM01247' is invoked, and assuming that a merlin message has an invalid recipient and an error notification has been generated, when the system needs to assign a fallback recipient, the desired outcome is that the system sets om01247 as the default recipient for message delivery.
💻 Technical Criteria
Given A Merlin message has an invalid recipient and an error notification has been generated
When The system needs to assign a fallback recipient
Then The system sets OM01247 as the default recipient for message delivery
R-GCX016E-cbl-02797 Validation Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'Validation Successful?' is invoked, and assuming that segment data validation has been completed, when the system evaluates validation results, the desired outcome is that a determination is made whether validation was successful or failed based on business requirements.
💻 Technical Criteria
Given Segment data validation has been completed
When The system evaluates validation results
Then A determination is made whether validation was successful or failed based on business requirements
R-GCX016E-cbl-02799 Log Initialization Complete
Action Rules
📊 Business Logic Narrative
When the process 'Log Initialization Complete' is invoked, and assuming that message segments have been successfully initialized and marked ready, when the system completes the initialization process, the desired outcome is that initialization completion is logged for audit and tracking purposes.
💻 Technical Criteria
Given Message segments have been successfully initialized and marked ready
When The system completes the initialization process
Then Initialization completion is logged for audit and tracking purposes
R-GCX016E-cbl-02800 Generate Error Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Error Message' is invoked, and assuming that segment data validation has failed, when the system processes the validation failure outcome, the desired outcome is that an appropriate error message is generated describing the validation failure.
💻 Technical Criteria
Given Segment data validation has failed
When The system processes the validation failure outcome
Then An appropriate error message is generated describing the validation failure
R-GCX016E-cbl-02801 Set Error Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Error Flag' is invoked, and assuming that an error message has been generated for validation failure, when the system handles the error condition, the desired outcome is that error flag is set to indicate validation failure and prevent further processing.
💻 Technical Criteria
Given An error message has been generated for validation failure
When The system handles the error condition
Then Error flag is set to indicate validation failure and prevent further processing
R-GCX016E-cbl-02803 Initialize Train Message Arrays
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Train Message Arrays' is invoked, and assuming that a train processing request is received, when the system begins message array initialization, the desired outcome is that message arrays are initialized and prepared for m10 and v9 segment storage.
💻 Technical Criteria
Given A train processing request is received
When The system begins message array initialization
Then Message arrays are initialized and prepared for M10 and V9 segment storage
R-GCX016E-cbl-02810 Set Event Code from Disposition
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Event Code from Disposition' is invoked, and assuming that v9 event segment is created and disposition code is available, when the system sets event code from disposition, the desired outcome is that event code field in v9 segment is populated based on the disposition code.
💻 Technical Criteria
Given V9 event segment is created and disposition code is available
When The system sets event code from disposition
Then Event code field in V9 segment is populated based on the disposition code
R-GCX016E-cbl-02815 Validation Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'Validation Successful?' is invoked, and assuming that segment data validation is completed, when validation is successful, the desired outcome is that system proceeds to store segments in message arrays.
💻 Technical Criteria
Given Segment data validation is completed
When Validation is successful
Then System proceeds to store segments in message arrays
R-GCX016E-cbl-02816 Validation Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'Validation Successful?' is invoked, and assuming that segment data validation is completed, when validation fails, the desired outcome is that system proceeds to log validation error and set error flag.
💻 Technical Criteria
Given Segment data validation is completed
When Validation fails
Then System proceeds to log validation error and set error flag
R-GCX016E-cbl-02817 Store M10 Segment in Array
Process Rules
📊 Business Logic Narrative
When the process 'Store M10 Segment in Array' is invoked, and assuming that m10 segment validation is successful, when the system stores m10 segment in array, the desired outcome is that m10 segment is placed in the appropriate position in the message array.
💻 Technical Criteria
Given M10 segment validation is successful
When The system stores M10 segment in array
Then M10 segment is placed in the appropriate position in the message array
R-GCX016E-cbl-02818 Store V9 Segment in Array
Process Rules
📊 Business Logic Narrative
When the process 'Store V9 Segment in Array' is invoked, and assuming that v9 segment validation is successful and m10 segment is stored, when the system stores v9 segment in array, the desired outcome is that v9 segment is placed in the appropriate position in the message array.
💻 Technical Criteria
Given V9 segment validation is successful and M10 segment is stored
When The system stores V9 segment in array
Then V9 segment is placed in the appropriate position in the message array
R-GCX016E-cbl-02819 Set Array Counters
Process Rules
📊 Business Logic Narrative
When the process 'Set Array Counters' is invoked, and assuming that m10 and v9 segments are stored in arrays, when the system sets array counters, the desired outcome is that array counters are updated to reflect the current number of stored segments.
💻 Technical Criteria
Given M10 and V9 segments are stored in arrays
When The system sets array counters
Then Array counters are updated to reflect the current number of stored segments
R-GCX016E-cbl-02820 Mark Arrays Ready for Processing
Process Rules
📊 Business Logic Narrative
When the process 'Mark Arrays Ready for Processing' is invoked, and assuming that array counters are set and segments are properly stored, when the system marks arrays ready for processing, the desired outcome is that arrays are flagged as ready and available for subsequent train processing operations.
💻 Technical Criteria
Given Array counters are set and segments are properly stored
When The system marks arrays ready for processing
Then Arrays are flagged as ready and available for subsequent train processing operations
R-GCX016E-cbl-02821 Log Validation Error
Process Rules
📊 Business Logic Narrative
When the process 'Log Validation Error' is invoked, and assuming that segment data validation fails, when the system logs validation error, the desired outcome is that error details are recorded for troubleshooting and audit purposes.
💻 Technical Criteria
Given Segment data validation fails
When The system logs validation error
Then Error details are recorded for troubleshooting and audit purposes
R-GCX016E-cbl-02822 Set Error Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Error Flag' is invoked, and assuming that validation error is logged, when the system sets error flag, the desired outcome is that error flag is activated to prevent further processing with invalid data.
💻 Technical Criteria
Given Validation error is logged
When The system sets error flag
Then Error flag is activated to prevent further processing with invalid data
R-GCX016E-cbl-02829 Retrieve Disposition Description
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Disposition Description' is invoked, and assuming that a disposition code has been identified, when the disposition description lookup is performed, the desired outcome is that the corresponding description is retrieved from the disposition code table.
💻 Technical Criteria
Given A disposition code has been identified
When The disposition description lookup is performed
Then The corresponding description is retrieved from the disposition code table
R-GCX016E-cbl-02834 Should Disposition Code Affect Release Quantities?
Decision Rules
📊 Business Logic Narrative
When the process 'Should Disposition Code Affect Release Quantities?' is invoked, and assuming that a disposition code is being evaluated for quantity impact, when the system checks if the disposition code affects release quantities, the desired outcome is that the system returns true if the disposition code should affect quantities, false otherwise.
💻 Technical Criteria
Given A disposition code is being evaluated for quantity impact
When The system checks if the disposition code affects release quantities
Then The system returns true if the disposition code should affect quantities, false otherwise
R-GCX016E-cbl-02838 Validate Shiproot Record Exists
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Shiproot Record Exists' is invoked, and assuming that a shipment processing request is initiated, when the system attempts to validate shiproot record existence, the desired outcome is that the system should verify the shiproot record exists in the shipment database and proceed only if found.
💻 Technical Criteria
Given A shipment processing request is initiated
When The system attempts to validate shiproot record existence
Then The system should verify the shiproot record exists in the shipment database and proceed only if found
R-GCX016E-cbl-02845 Create U1 Shipment Minimum Segment
Action Rules
📊 Business Logic Narrative
When the process 'Create U1 Shipment Minimum Segment' is invoked, and assuming that all required station information has been processed, when the system creates a u1 shipment minimum segment, the desired outcome is that a u1 segment structure should be created and ready for data population.
💻 Technical Criteria
Given All required station information has been processed
When The system creates a U1 shipment minimum segment
Then A U1 segment structure should be created and ready for data population
R-GCX016E-cbl-02849 Validate U1 Segment Data
Validation Rules
📊 Business Logic Narrative
When the process 'Validate U1 Segment Data' is invoked, and assuming that all data fields have been populated in the u1 segment, when the system validates u1 segment data completeness and accuracy, the desired outcome is that the u1 segment should pass validation checks for required fields and data integrity before storage.
💻 Technical Criteria
Given All data fields have been populated in the U1 segment
When The system validates U1 segment data completeness and accuracy
Then The U1 segment should pass validation checks for required fields and data integrity before storage
R-GCX016E-cbl-02850 Store U1 Segment for EDI Processing
Action Rules
📊 Business Logic Narrative
When the process 'Store U1 Segment for EDI Processing' is invoked, and assuming that u1 segment data has been validated successfully, when the system stores the u1 segment for edi processing, the desired outcome is that the u1 segment should be stored in the shipment minimum segments database and made available for edi transmission.
💻 Technical Criteria
Given U1 segment data has been validated successfully
When The system stores the U1 segment for EDI processing
Then The U1 segment should be stored in the shipment minimum segments database and made available for EDI transmission
R-GCX016E-cbl-02851 Log Shipment Creation Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Shipment Creation Action' is invoked, and assuming that u1 segment has been successfully stored for edi processing, when the system logs the shipment creation action, the desired outcome is that a log entry should be created documenting the successful creation of shipment minimum information with relevant identifiers and timestamp.
💻 Technical Criteria
Given U1 segment has been successfully stored for EDI processing
When The system logs the shipment creation action
Then A log entry should be created documenting the successful creation of shipment minimum information with relevant identifiers and timestamp
🚂 Equipment & Cargo Specs 1613 logic blocks
R-GCX016E-cbl-00007 Message Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Message Type?' is invoked, and assuming that message array has been initialized, when message contains cargo-related segments (x4, n7), the desired outcome is that route to cargo processing path.
💻 Technical Criteria
Given Message array has been initialized
When Message contains cargo-related segments (X4, N7)
Then Route to cargo processing path
R-GCX016E-cbl-00021 105:Equipment Hold Processing by VID Segment
Action Rules
📊 Business Logic Narrative
When the process '105:Equipment Hold Processing by VID Segment' is invoked, and assuming that event code is hmi or sei, when vid segments are present for equipment-specific processing, the desired outcome is that process associated vid segments for equipment-specific holds.
💻 Technical Criteria
Given Event code is HMI or SEI
When VID segments are present for equipment-specific processing
Then Process associated VID segments for equipment-specific holds
R-GCX016E-cbl-00022 106:Equipment Release Processing by VID Segment
Action Rules
📊 Business Logic Narrative
When the process '106:Equipment Release Processing by VID Segment' is invoked, and assuming that event code is hre or ser, when vid segments are present for equipment-specific processing, the desired outcome is that process associated vid segments for equipment-specific releases.
💻 Technical Criteria
Given Event code is HRE or SER
When VID segments are present for equipment-specific processing
Then Process associated VID segments for equipment-specific releases
R-GCX016E-cbl-00023 Cargo Lookup Method?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Lookup Method?' is invoked, and assuming that x4 segment contains disposition code and processing parameters, when processing type is by bond number, the desired outcome is that route to bond-based cargo processing.
💻 Technical Criteria
Given X4 segment contains disposition code and processing parameters
When Processing type is by bond number
Then Route to bond-based cargo processing
R-GCX016E-cbl-00025 21:Cargo Processing by Bond
Process Rules
📊 Business Logic Narrative
When the process '21:Cargo Processing by Bond' is invoked, and assuming that disposition code requires bond-based processing, when bond number is identified from x4 segment, the desired outcome is that process all cargos with matching bond number.
💻 Technical Criteria
Given Disposition code requires bond-based processing
When Bond number is identified from X4 segment
Then Process all cargos with matching bond number
R-GCX016E-cbl-00027 23:Individual Cargo Processing
Process Rules
📊 Business Logic Narrative
When the process '23:Individual Cargo Processing' is invoked, and assuming that disposition code requires individual cargo processing, when single cargo is identified from segments, the desired outcome is that process individual us cargo with disposition code.
💻 Technical Criteria
Given Disposition code requires individual cargo processing
When Single cargo is identified from segments
Then Process individual US cargo with disposition code
R-GCX016E-cbl-00029 42:S09 Status Segment Processing
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process '42:S09 Status Segment Processing', assuming that cargo is not cprs shipment, when n7 segment data contains car information, the desired outcome is that update car id from n7 segment data.
💻 Technical Criteria
EXCLUDING Cargo is not CPRS shipment
When N7 segment data contains car information
Then Update car ID from N7 segment data
R-GCX016E-cbl-00030 42:S09 Status Segment Processing
Action Rules
📊 Business Logic Narrative
When the process '42:S09 Status Segment Processing' is invoked, and assuming that cargo is cprs shipment, when car id processing is performed, the desired outcome is that clear car id information.
💻 Technical Criteria
Given Cargo is CPRS shipment
When Car ID processing is performed
Then Clear car ID information
R-GCX016E-cbl-00034 24:Disposition Code 95 Processing
Action Rules
📊 Business Logic Narrative
When the process '24:Disposition Code 95 Processing' is invoked, and assuming that disposition code is 95, when entry numbers match existing bond information, the desired outcome is that clear bond information from cargo record.
💻 Technical Criteria
Given Disposition code is 95
When Entry numbers match existing bond information
Then Clear bond information from cargo record
R-GCX016E-cbl-00037 50:CPRS Bond Processing
Action Rules
📊 Business Logic Narrative
When the process '50:CPRS Bond Processing' is invoked, and assuming that cargo is cprs shipment, when bond processing is required, the desired outcome is that apply cprs-specific bond processing rules.
💻 Technical Criteria
Given Cargo is CPRS shipment
When Bond processing is required
Then Apply CPRS-specific bond processing rules
R-GCX016E-cbl-00040 59:Complex Cargo Status Evaluation
Decision Rules
📊 Business Logic Narrative
When the process '59:Complex Cargo Status Evaluation' is invoked, and assuming that all disposition codes have been processed and analyzed, when final status determination is required, the desired outcome is that apply status hierarchy: manual release → released, fda hold → holdfda, ptt with quantity check → ptt, hold combinations → various hold statuses, release with quantity validation → relsd or holdpcs, export/arrival → export/arrival, default → ack or proceed.
💻 Technical Criteria
Given All disposition codes have been processed and analyzed
When Final status determination is required
Then Apply status hierarchy: Manual Release → Released, FDA Hold → HOLDFDA, PTT with quantity check → PTT, Hold combinations → Various hold statuses, Release with quantity validation → RELSD or HOLDPCS, Export/Arrival → EXPORT/ARRIVAL, Default → ACK or PROCEED
R-GCX016E-cbl-00042 68:Export Notification Processing
Action Rules
📊 Business Logic Narrative
When the process '68:Export Notification Processing' is invoked, and assuming that cargo status is set to export, when export processing is performed, the desired outcome is that set export status, clear destination index, and generate appropriate notifications.
💻 Technical Criteria
Given Cargo status is set to export
When Export processing is performed
Then Set export status, clear destination index, and generate appropriate notifications
R-GCX016E-cbl-00043 69:Arrival Notification Processing
Action Rules
📊 Business Logic Narrative
When the process '69:Arrival Notification Processing' is invoked, and assuming that cargo status is set to arrival, when arrival processing is performed, the desired outcome is that update arrival flags and dates based on location.
💻 Technical Criteria
Given Cargo status is set to arrival
When Arrival processing is performed
Then Update arrival flags and dates based on location
R-GCX016E-cbl-00044 70:New Cargo Record Creation
Action Rules
📊 Business Logic Narrative
When the process '70:New Cargo Record Creation' is invoked, and assuming that cargo lookup returns no existing cargo, when new cargo creation is required, the desired outcome is that create new cargo record with cprs vs regular shipment handling and automatically spawn gct0162e for new cargos.
💻 Technical Criteria
Given Cargo lookup returns no existing cargo
When New cargo creation is required
Then Create new cargo record with CPRS vs regular shipment handling and automatically spawn GCT0162E for new cargos
R-GCX016E-cbl-00045 175:New Foreign Cargo Record Creation
Action Rules
📊 Business Logic Narrative
When the process '175:New Foreign Cargo Record Creation' is invoked, and assuming that cargo is identified as foreign shipment, when foreign cargo creation is required, the desired outcome is that create foreign cargo record with appropriate international processing flags.
💻 Technical Criteria
Given Cargo is identified as foreign shipment
When Foreign cargo creation is required
Then Create foreign cargo record with appropriate international processing flags
R-GCX016E-cbl-00050 80:Cargo Status Integration
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process '80:Cargo Status Integration', assuming that cargo status has been determined and requires external integration, when integration is initiated and equipment type is valid (containers, trailers, chassis, etc.) and status is not ptt/ptt-ex for held/partial held cargos, the desired outcome is that map cargo status to integration system status descriptions and process only hold, ptt, ptt-ex, or release statuses.
💻 Technical Criteria
EXCLUDING Cargo status has been determined and requires external integration
When Integration is initiated and equipment type is valid (containers, trailers, chassis, etc.) and status is not PTT/PTT-EX for held/partial held cargos
Then Map cargo status to integration system status descriptions and process only HOLD, PTT, PTT-EX, or RELEASE statuses
R-GCX016E-cbl-00051 80:Cargo Status Integration
Validation Rules
📊 Business Logic Narrative
When the process '80:Cargo Status Integration' is invoked, and assuming that process type is 4e and cargo status is release, when release status verification is performed, the desired outcome is that verify full release before setting 'release' status in integration system.
💻 Technical Criteria
Given Process type is 4E and cargo status is release
When Release status verification is performed
Then Verify full release before setting 'RELEASE' status in integration system
R-GCX016E-cbl-00058 88:Merlin Message Distribution
Action Rules
📊 Business Logic Narrative
When the process '88:Merlin Message Distribution' is invoked, and assuming that merlin message is export type, when export message routing is performed, the desired outcome is that route based on equipment type classification.
💻 Technical Criteria
Given Merlin message is export type
When Export message routing is performed
Then Route based on equipment type classification
R-GCX016E-cbl-02871 Set Message Not Available Flag
Decision Rules
📊 Business Logic Narrative
When the process 'Set Message Not Available Flag' is invoked, and assuming that an mqget operation is executed, when the completion code indicates no message is available (reason code 2033), the desired outcome is that set message not available flag to indicate queue is empty.
💻 Technical Criteria
Given An MQGET operation is executed
When The completion code indicates no message is available (reason code 2033)
Then Set message not available flag to indicate queue is empty
R-GCX016E-cbl-03133 Generate CPRS Train Not Found Error
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate CPRS Train Not Found Error', assuming that a cprs train id has been validated but not found in the train data system, when the system cannot locate the train in gcwtl train data, the desired outcome is that the system generates a train not found error message and continues with cargo lookup processing.
💻 Technical Criteria
EXCLUDING A CPRS train ID has been validated but not found in the train data system
When The system cannot locate the train in GCWTL train data
Then The system generates a train not found error message and continues with cargo lookup processing
R-GCX016E-cbl-03134 CPRS Cargo Lookup by Car ID
Process Rules
📊 Business Logic Narrative
When the process 'CPRS Cargo Lookup by Car ID' is invoked, and assuming that cprs train processing has been initiated (whether train was found or not), when the system searches gcsusrt cargo records using the car id from the n7 segment, the desired outcome is that the system identifies existing cprs cargo records or determines that new cargo records need to be created.
💻 Technical Criteria
Given CPRS train processing has been initiated (whether train was found or not)
When The system searches GCSUSRT cargo records using the car ID from the N7 segment
Then The system identifies existing CPRS cargo records or determines that new cargo records need to be created
R-GCX016E-cbl-03135 Process Existing CPRS Cargo
Process Rules
📊 Business Logic Narrative
When the process 'Process Existing CPRS Cargo' is invoked, and assuming that cprs cargo records have been found in the system for the specified car id, when the system processes the existing cargo records, the desired outcome is that the system updates the existing cprs cargo with new disposition codes, status changes, and associated processing.
💻 Technical Criteria
Given CPRS cargo records have been found in the system for the specified car ID
When The system processes the existing cargo records
Then The system updates the existing CPRS cargo with new disposition codes, status changes, and associated processing
R-GCX016E-cbl-03136 Create New CPRS Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Create New CPRS Cargo Record' is invoked, and assuming that no existing cprs cargo records are found for the specified car id, when the system needs to process new cprs cargo, the desired outcome is that the system creates new cargo records in gcsusrt with appropriate cprs-specific attributes and initial status.
💻 Technical Criteria
Given No existing CPRS cargo records are found for the specified car ID
When The system needs to process new CPRS cargo
Then The system creates new cargo records in GCSUSRT with appropriate CPRS-specific attributes and initial status
R-GCX016E-cbl-03137 Apply CPRS Bond Processing Rules
Policy Rules
📊 Business Logic Narrative
When the process 'Apply CPRS Bond Processing Rules' is invoked, and assuming that cprs cargo records are ready for bond processing (either existing or newly created), when the system applies cprs bond processing rules from gcstbrt bond tables, the desired outcome is that the system processes bonds according to canadian pacific railway requirements and cross-border regulations.
💻 Technical Criteria
Given CPRS cargo records are ready for bond processing (either existing or newly created)
When The system applies CPRS bond processing rules from GCSTBRT bond tables
Then The system processes bonds according to Canadian Pacific Railway requirements and cross-border regulations
R-GCX016E-cbl-03138 Set CPRS Special Flags
Process Rules
📊 Business Logic Narrative
When the process 'Set CPRS Special Flags' is invoked, and assuming that cprs bond processing rules have been applied to the cargo, when the system configures cprs-specific processing flags, the desired outcome is that the system sets appropriate flags for canadian pacific railway processing, cross-border handling, and special routing requirements.
💻 Technical Criteria
Given CPRS bond processing rules have been applied to the cargo
When The system configures CPRS-specific processing flags
Then The system sets appropriate flags for Canadian Pacific Railway processing, cross-border handling, and special routing requirements
R-GCX016E-cbl-03139 Handle CPRS Cross-Border Validation
Validation Rules
📊 Business Logic Narrative
When the process 'Handle CPRS Cross-Border Validation' is invoked, and assuming that cprs special flags have been configured for the cargo, when the system performs cross-border validation for canadian pacific railway operations, the desired outcome is that the system validates compliance with cross-border regulations and determines if canadian border crossing processing is required.
💻 Technical Criteria
Given CPRS special flags have been configured for the cargo
When The system performs cross-border validation for Canadian Pacific Railway operations
Then The system validates compliance with cross-border regulations and determines if Canadian border crossing processing is required
R-GCX016E-cbl-03141 Map US Port to Canadian Location
Process Rules
📊 Business Logic Narrative
When the process 'Map US Port to Canadian Location' is invoked, and assuming that a canadian border crossing has been identified for cprs cargo, when the system maps us port information to canadian location equivalents using border location maps, the desired outcome is that the system establishes proper location mapping for cross-border processing and routing validation.
💻 Technical Criteria
Given A Canadian border crossing has been identified for CPRS cargo
When The system maps US port information to Canadian location equivalents using border location maps
Then The system establishes proper location mapping for cross-border processing and routing validation
R-GCX016E-cbl-03143 Apply CPRS Bond Information
Process Rules
📊 Business Logic Narrative
When the process 'Apply CPRS Bond Information' is invoked, and assuming that cprs routing rules have been validated (either after border crossing mapping or direct validation), when the system applies cprs bond information to the cargo, the desired outcome is that the system updates cargo records with appropriate canadian pacific railway bond details and requirements.
💻 Technical Criteria
Given CPRS routing rules have been validated (either after border crossing mapping or direct validation)
When The system applies CPRS bond information to the cargo
Then The system updates cargo records with appropriate Canadian Pacific Railway bond details and requirements
R-GCX016E-cbl-03144 Set Canadian Pacific Railway Bond
Process Rules
📊 Business Logic Narrative
When the process 'Set Canadian Pacific Railway Bond' is invoked, and assuming that cprs bond information has been applied to the cargo, when the system sets canadian pacific railway bond configuration, the desired outcome is that the system establishes proper bond settings specific to canadian pacific railway requirements and generates bond creation messaging.
💻 Technical Criteria
Given CPRS bond information has been applied to the cargo
When The system sets Canadian Pacific Railway bond configuration
Then The system establishes proper bond settings specific to Canadian Pacific Railway requirements and generates bond creation messaging
R-GCX016E-cbl-03146 Update CPRS Cargo Status
Process Rules
📊 Business Logic Narrative
When the process 'Update CPRS Cargo Status' is invoked, and assuming that k1 bond creation messages have been generated, when the system updates cprs cargo status, the desired outcome is that the system sets appropriate status indicators reflecting completed canadian pacific railway processing and prepares for notification generation.
💻 Technical Criteria
Given K1 bond creation messages have been generated
When The system updates CPRS cargo status
Then The system sets appropriate status indicators reflecting completed Canadian Pacific Railway processing and prepares for notification generation
R-GCX016E-cbl-03147 Send CPRS Notifications
Action Rules
📊 Business Logic Narrative
When the process 'Send CPRS Notifications' is invoked, and assuming that cprs cargo status has been updated, when the system sends cprs processing notifications, the desired outcome is that the system delivers appropriate notifications to stakeholders regarding canadian pacific railway cargo processing completion.
💻 Technical Criteria
Given CPRS cargo status has been updated
When The system sends CPRS processing notifications
Then The system delivers appropriate notifications to stakeholders regarding Canadian Pacific Railway cargo processing completion
R-GCX016E-cbl-00087 Process VID Segment for Individual Equipment
Decision Rules
📊 Business Logic Narrative
When the process 'Process VID Segment for Individual Equipment' is invoked, and assuming that an hre disposition code is received and a vid segment is present in the message, when the system processes the hold release event, the desired outcome is that the system processes vid segment for individual equipment hold release instead of train-level processing.
💻 Technical Criteria
Given An HRE disposition code is received AND a VID segment is present in the message
When The system processes the hold release event
Then The system processes VID segment for individual equipment hold release instead of train-level processing
R-GCX016E-cbl-00088 Decrement Equipment Hold Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Decrement Equipment Hold Counter' is invoked, and assuming that equipment-specific hold release is being processed and the equipment has an active hold counter, when the vid segment is processed for hold release, the desired outcome is that the equipment hold counter is decremented by one.
💻 Technical Criteria
Given Equipment-specific hold release is being processed AND the equipment has an active hold counter
When The VID segment is processed for hold release
Then The equipment hold counter is decremented by one
R-GCX016E-cbl-00089 Hold Counter = 0?
Decision Rules
📊 Business Logic Narrative
When the process 'Hold Counter = 0?' is invoked, and assuming that equipment hold counter has been decremented, when the system checks the equipment hold counter value, the desired outcome is that if the hold counter equals zero then proceed to remove equipment hold flag else proceed to log hold release action.
💻 Technical Criteria
Given Equipment hold counter has been decremented
When The system checks the equipment hold counter value
Then IF the hold counter equals zero THEN proceed to remove equipment hold flag ELSE proceed to log hold release action
R-GCX016E-cbl-00090 Remove Equipment Hold Flag
Action Rules
📊 Business Logic Narrative
When the process 'Remove Equipment Hold Flag' is invoked, and assuming that equipment hold counter equals zero, when all holds on the equipment have been released, the desired outcome is that the equipment hold status flag is removed from the equipment record.
💻 Technical Criteria
Given Equipment hold counter equals zero
When All holds on the equipment have been released
Then The equipment hold status flag is removed from the equipment record
R-GCX016E-cbl-00093 Log Hold Release Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Hold Release Action' is invoked, and assuming that a hold release action has been processed (either equipment-specific or train-level), when the hold release processing is completed, the desired outcome is that the hold release action is logged in the system audit trail.
💻 Technical Criteria
Given A hold release action has been processed (either equipment-specific or train-level)
When The hold release processing is completed
Then The hold release action is logged in the system audit trail
R-GCX016E-cbl-00105 US Cargo Arrival Processing
Process Rules
📊 Business Logic Narrative
When the process 'US Cargo Arrival Processing' is invoked, and assuming that the train arrived status flag has been set, when the system continues with cargo processing, the desired outcome is that initiate arrival processing for all us cargo manifests associated with this train.
💻 Technical Criteria
Given The train arrived status flag has been set
When The system continues with cargo processing
Then Initiate arrival processing for all US cargo manifests associated with this train
R-GCX016E-cbl-00106 Send AEI Arrival Messages
Action Rules
📊 Business Logic Narrative
When the process 'Send AEI Arrival Messages' is invoked, and assuming that us cargo arrival processing has been initiated, when the system processes aei notification requirements, the desired outcome is that generate and send aei arrival messages to notify relevant parties of train arrival.
💻 Technical Criteria
Given US cargo arrival processing has been initiated
When The system processes AEI notification requirements
Then Generate and send AEI arrival messages to notify relevant parties of train arrival
R-GCX016E-cbl-00187 Update Train Equipment List Status
Process Rules
📊 Business Logic Narrative
When the process 'Update Train Equipment List Status' is invoked, and assuming that a train has been seized and notifications sent, when the system processes equipment associated with the train, the desired outcome is that the system updates the equipment list status to reflect the train seizure.
💻 Technical Criteria
Given A train has been seized and notifications sent
When The system processes equipment associated with the train
Then The system updates the equipment list status to reflect the train seizure
R-GCX016E-cbl-00188 Mark All Equipment in Train as Seized
Action Rules
📊 Business Logic Narrative
When the process 'Mark All Equipment in Train as Seized' is invoked, and assuming that the train equipment list has been updated, when the system processes individual equipment items, the desired outcome is that the system marks each equipment item in the train as seized.
💻 Technical Criteria
Given The train equipment list has been updated
When The system processes individual equipment items
Then The system marks each equipment item in the train as seized
R-GCX016E-cbl-00201 Process Individual Equipment in Train
Process Rules
📊 Business Logic Narrative
When the process 'Process Individual Equipment in Train' is invoked, and assuming that a train seizure release has been processed, when the system processes associated equipment, the desired outcome is that each piece of equipment in the train is individually evaluated for seizure release.
💻 Technical Criteria
Given A train seizure release has been processed
When The system processes associated equipment
Then Each piece of equipment in the train is individually evaluated for seizure release
R-GCX016E-cbl-00202 Equipment Seized?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment Seized?' is invoked, and assuming that individual equipment is being processed for seizure release, when the system evaluates each piece of equipment, the desired outcome is that the system determines if the equipment is currently in seized status.
💻 Technical Criteria
Given Individual equipment is being processed for seizure release
When The system evaluates each piece of equipment
Then The system determines if the equipment is currently in seized status
R-GCX016E-cbl-00203 Release Equipment from Seizure
Action Rules
📊 Business Logic Narrative
When the process 'Release Equipment from Seizure' is invoked, and assuming that equipment is currently in seized status, when the train seizure release is processed, the desired outcome is that the individual equipment is released from seizure status.
💻 Technical Criteria
Given Equipment is currently in seized status
When The train seizure release is processed
Then The individual equipment is released from seizure status
R-GCX016E-cbl-00204 Update Equipment Seizure Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Update Equipment Seizure Counter' is invoked, and assuming that equipment has been released from seizure, when the seizure release processing continues, the desired outcome is that the equipment seizure counter is updated to reflect the release.
💻 Technical Criteria
Given Equipment has been released from seizure
When The seizure release processing continues
Then The equipment seizure counter is updated to reflect the release
R-GCX016E-cbl-00205 Continue to Next Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Continue to Next Equipment' is invoked, and assuming that current equipment processing is complete, when more equipment exists in the train, the desired outcome is that the system moves to process the next piece of equipment.
💻 Technical Criteria
Given Current equipment processing is complete
When More equipment exists in the train
Then The system moves to process the next piece of equipment
R-GCX016E-cbl-00206 Generate Train Seizure Release Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Train Seizure Release Notification' is invoked, and assuming that all equipment in the train has been processed for seizure release, when the seizure release processing is complete, the desired outcome is that a train seizure release notification is generated.
💻 Technical Criteria
Given All equipment in the train has been processed for seizure release
When The seizure release processing is complete
Then A train seizure release notification is generated
R-GCX016E-cbl-00223 Validate Equipment ID in VID Segment
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Equipment ID in VID Segment' is invoked, and assuming that a vid segment is received with hre disposition code, when the system processes the vid segment equipment id field, the desired outcome is that the equipment id must contain non-blank, valid alphanumeric data to proceed with hold release processing.
💻 Technical Criteria
Given A VID segment is received with HRE disposition code
When The system processes the VID segment equipment ID field
Then The equipment ID must contain non-blank, valid alphanumeric data to proceed with hold release processing
R-GCX016E-cbl-00224 Look up Equipment in Train Consist
Validation Rules
📊 Business Logic Narrative
When the process 'Look up Equipment in Train Consist' is invoked, and assuming that a valid equipment id from vid segment, when the system searches the train consist list for the equipment, the desired outcome is that the equipment must be found in the train consist to proceed with hold release processing.
💻 Technical Criteria
Given A valid equipment ID from VID segment
When The system searches the train consist list for the equipment
Then The equipment must be found in the train consist to proceed with hold release processing
R-GCX016E-cbl-00225 Check Current Equipment Hold Status
Decision Rules
📊 Business Logic Narrative
When the process 'Check Current Equipment Hold Status' is invoked, and assuming that equipment exists in the train consist, when the system checks the equipment's current hold status, the desired outcome is that the equipment must currently have a hold flag set to proceed with hold release.
💻 Technical Criteria
Given Equipment exists in the train consist
When The system checks the equipment's current hold status
Then The equipment must currently have a hold flag set to proceed with hold release
R-GCX016E-cbl-00226 Remove Equipment Hold Flag
Action Rules
📊 Business Logic Narrative
When the process 'Remove Equipment Hold Flag' is invoked, and assuming that equipment is currently held with hold flag set, when hre disposition code is processed for the equipment, the desired outcome is that the system removes the hold flag from the equipment record.
💻 Technical Criteria
Given Equipment is currently held with hold flag set
When HRE disposition code is processed for the equipment
Then The system removes the hold flag from the equipment record
R-GCX016E-cbl-00227 Update Equipment Status in Train List
Action Rules
📊 Business Logic Narrative
When the process 'Update Equipment Status in Train List' is invoked, and assuming that equipment hold flag has been removed, when the system updates the train list, the desired outcome is that the equipment status in the train list is updated to reflect the released status.
💻 Technical Criteria
Given Equipment hold flag has been removed
When The system updates the train list
Then The equipment status in the train list is updated to reflect the released status
R-GCX016E-cbl-00228 Decrement Train Hold Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Decrement Train Hold Counter' is invoked, and assuming that equipment hold has been successfully released, when the system updates train-level counters, the desired outcome is that the train hold counter is decremented by one to reflect the equipment release.
💻 Technical Criteria
Given Equipment hold has been successfully released
When The system updates train-level counters
Then The train hold counter is decremented by one to reflect the equipment release
R-GCX016E-cbl-00229 All Equipment Released?
Decision Rules
📊 Business Logic Narrative
When the process 'All Equipment Released?' is invoked, and assuming that train hold counter has been decremented, when the system checks if any equipment remains held, the desired outcome is that if train hold counter equals zero, all equipment is considered released; otherwise equipment remains held.
💻 Technical Criteria
Given Train hold counter has been decremented
When The system checks if any equipment remains held
Then If train hold counter equals zero, all equipment is considered released; otherwise equipment remains held
R-GCX016E-cbl-00230 Update Train Hold Status to Released
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Hold Status to Released' is invoked, and assuming that all equipment in the train has been released from hold, when the system updates the train status, the desired outcome is that the train hold status is set to released.
💻 Technical Criteria
Given All equipment in the train has been released from hold
When The system updates the train status
Then The train hold status is set to released
R-GCX016E-cbl-00231 Log Equipment Hold Release Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Equipment Hold Release Action' is invoked, and assuming that equipment hold has been successfully released, when the system performs logging operations, the desired outcome is that an audit record is created documenting the equipment hold release action with timestamp and equipment details.
💻 Technical Criteria
Given Equipment hold has been successfully released
When The system performs logging operations
Then An audit record is created documenting the equipment hold release action with timestamp and equipment details
R-GCX016E-cbl-00232 Generate Equipment Release Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Equipment Release Notification' is invoked, and assuming that equipment hold release has been logged, when the system generates notifications, the desired outcome is that internal notifications are created to inform relevant parties of the equipment release.
💻 Technical Criteria
Given Equipment hold release has been logged
When The system generates notifications
Then Internal notifications are created to inform relevant parties of the equipment release
R-GCX016E-cbl-00233 Send Merlin Message for Equipment Release
Action Rules
📊 Business Logic Narrative
When the process 'Send Merlin Message for Equipment Release' is invoked, and assuming that equipment release notification has been generated, when the system sends external notifications, the desired outcome is that a merlin message is sent containing equipment release details to external systems.
💻 Technical Criteria
Given Equipment release notification has been generated
When The system sends external notifications
Then A Merlin message is sent containing equipment release details to external systems
R-GCX016E-cbl-00234 Generate Error - Invalid Equipment ID
Validation Rules
📊 Business Logic Narrative
When the process 'Generate Error - Invalid Equipment ID' is invoked, and assuming that vid segment contains invalid or blank equipment id, when equipment id validation fails, the desired outcome is that an error is generated indicating invalid equipment id and processing stops.
💻 Technical Criteria
Given VID segment contains invalid or blank equipment ID
When Equipment ID validation fails
Then An error is generated indicating invalid equipment ID and processing stops
R-GCX016E-cbl-00235 Generate Error - Equipment Not Found
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error - Equipment Not Found', assuming that valid equipment id that does not exist in train consist, when equipment lookup in train consist fails, the desired outcome is that an error is generated indicating equipment not found in train and processing stops.
💻 Technical Criteria
EXCLUDING Valid equipment ID that does not exist in train consist
When Equipment lookup in train consist fails
Then An error is generated indicating equipment not found in train and processing stops
R-GCX016E-cbl-00236 Generate Warning - Equipment Not Held
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Warning - Equipment Not Held', assuming that equipment exists in train but is not currently held, when hold release is attempted on non-held equipment, the desired outcome is that a warning is generated indicating equipment is not held and processing continues.
💻 Technical Criteria
EXCLUDING Equipment exists in train but is not currently held
When Hold release is attempted on non-held equipment
Then A warning is generated indicating equipment is not held and processing continues
R-GCX016E-cbl-00237 Disposition Code = SEI?
Validation Rules
📊 Business Logic Narrative
When the process 'Disposition Code = SEI?' is invoked, and assuming that a vid segment is received for equipment processing, when the system checks the disposition code from the previous x4 segment, the desired outcome is that processing continues only if the disposition code equals sei, otherwise the equipment seizure process is skipped.
💻 Technical Criteria
Given A VID segment is received for equipment processing
When The system checks the disposition code from the previous X4 segment
Then Processing continues only if the disposition code equals SEI, otherwise the equipment seizure process is skipped
R-GCX016E-cbl-00238 Equipment ID Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Equipment ID Valid?' is invoked, and assuming that an equipment id has been extracted from the vid segment, when the system validates the equipment id format, the desired outcome is that the equipment id must be in valid format with proper initial and number components, otherwise generate invalid equipment id error.
💻 Technical Criteria
Given An equipment ID has been extracted from the VID segment
When The system validates the equipment ID format
Then The equipment ID must be in valid format with proper initial and number components, otherwise generate invalid equipment ID error
R-GCX016E-cbl-00239 Equipment Found in Train?
Validation Rules
📊 Business Logic Narrative
When the process 'Equipment Found in Train?' is invoked, and assuming that a valid equipment id has been provided for seizure, when the system searches the train consist for the equipment, the desired outcome is that the equipment must exist in the train list, otherwise generate equipment not found error.
💻 Technical Criteria
Given A valid equipment ID has been provided for seizure
When The system searches the train consist for the equipment
Then The equipment must exist in the train list, otherwise generate equipment not found error
R-GCX016E-cbl-00240 Equipment Already Seized?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment Already Seized?' is invoked, and assuming that equipment exists in the train and seizure is requested, when the system checks the current seizure status of the equipment, the desired outcome is that if equipment is already seized, generate equipment already seized error, otherwise proceed with seizure.
💻 Technical Criteria
Given Equipment exists in the train and seizure is requested
When The system checks the current seizure status of the equipment
Then If equipment is already seized, generate equipment already seized error, otherwise proceed with seizure
R-GCX016E-cbl-00241 Set Equipment Seizure Flag
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Equipment Seizure Flag', assuming that equipment is found in train and is not currently seized, when the seizure request is processed, the desired outcome is that set the equipment seizure flag to indicate the equipment is now seized.
💻 Technical Criteria
EXCLUDING Equipment is found in train and is not currently seized
When The seizure request is processed
Then Set the equipment seizure flag to indicate the equipment is now seized
R-GCX016E-cbl-00242 Update Equipment Status in Train List
Action Rules
📊 Business Logic Narrative
When the process 'Update Equipment Status in Train List' is invoked, and assuming that equipment seizure flag has been set, when the system updates the train consist information, the desired outcome is that update the equipment status in the train list to show seized status.
💻 Technical Criteria
Given Equipment seizure flag has been set
When The system updates the train consist information
Then Update the equipment status in the train list to show seized status
R-GCX016E-cbl-00243 Increment Train Seizure Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment Train Seizure Counter' is invoked, and assuming that equipment status has been updated to seized in the train list, when the system updates train-level seizure tracking, the desired outcome is that increment the train seizure counter by one to reflect the additional seized equipment.
💻 Technical Criteria
Given Equipment status has been updated to seized in the train list
When The system updates train-level seizure tracking
Then Increment the train seizure counter by one to reflect the additional seized equipment
R-GCX016E-cbl-00244 Log Equipment Seizure Action
Action Rules
📊 Business Logic Narrative
When the process 'Log Equipment Seizure Action' is invoked, and assuming that equipment has been successfully seized and counters updated, when the system logs the seizure action, the desired outcome is that create a log entry with equipment id, seizure timestamp, and action details for audit purposes.
💻 Technical Criteria
Given Equipment has been successfully seized and counters updated
When The system logs the seizure action
Then Create a log entry with equipment ID, seizure timestamp, and action details for audit purposes
R-GCX016E-cbl-00245 Generate Seizure Confirmation Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Seizure Confirmation Message' is invoked, and assuming that equipment seizure has been logged successfully, when the system generates confirmation messaging, the desired outcome is that create a seizure confirmation message with equipment details and seizure status.
💻 Technical Criteria
Given Equipment seizure has been logged successfully
When The system generates confirmation messaging
Then Create a seizure confirmation message with equipment details and seizure status
R-GCX016E-cbl-00246 Update Train Status if All Equipment Seized
Decision Rules
📊 Business Logic Narrative
When the process 'Update Train Status if All Equipment Seized' is invoked, and assuming that individual equipment has been seized and confirmation message generated, when the system evaluates overall train seizure status, the desired outcome is that if all equipment in the train is now seized, update the train status to fully seized, otherwise maintain partial seizure status.
💻 Technical Criteria
Given Individual equipment has been seized and confirmation message generated
When The system evaluates overall train seizure status
Then If all equipment in the train is now seized, update the train status to fully seized, otherwise maintain partial seizure status
R-GCX016E-cbl-00247 Send Equipment Seizure Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send Equipment Seizure Notification' is invoked, and assuming that train status has been evaluated and updated as needed, when the system dispatches seizure notifications, the desired outcome is that send equipment seizure notification to appropriate recipients including equipment details and seizure confirmation.
💻 Technical Criteria
Given Train status has been evaluated and updated as needed
When The system dispatches seizure notifications
Then Send equipment seizure notification to appropriate recipients including equipment details and seizure confirmation
R-GCX016E-cbl-00248 Receive SER Disposition Code for Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Receive SER Disposition Code for Equipment' is invoked, and assuming that a ser disposition code is received for equipment seizure release, when the system processes the disposition code request, the desired outcome is that the system initiates equipment seizure release processing workflow.
💻 Technical Criteria
Given A SER disposition code is received for equipment seizure release
When The system processes the disposition code request
Then The system initiates equipment seizure release processing workflow
R-GCX016E-cbl-00249 Process VID Segment for Equipment ID
Process Rules
📊 Business Logic Narrative
When the process 'Process VID Segment for Equipment ID' is invoked, and assuming that a vid segment contains equipment identification data, when the system processes the vid segment, the desired outcome is that the equipment id is extracted and prepared for seizure release validation.
💻 Technical Criteria
Given A VID segment contains equipment identification data
When The system processes the VID segment
Then The equipment ID is extracted and prepared for seizure release validation
R-GCX016E-cbl-00250 Equipment Found in Train?
Validation Rules
📊 Business Logic Narrative
When the process 'Equipment Found in Train?' is invoked, and assuming that an equipment id is provided for seizure release, when the system searches for the equipment in the train equipment list, the desired outcome is that the system determines if the equipment exists in the train and proceeds accordingly or generates equipment not found error.
💻 Technical Criteria
Given An equipment ID is provided for seizure release
When The system searches for the equipment in the train equipment list
Then The system determines if the equipment exists in the train and proceeds accordingly or generates equipment not found error
R-GCX016E-cbl-00251 Validate Equipment Seizure Status
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Equipment Seizure Status' is invoked, and assuming that equipment exists in the train consist, when the system validates the equipment's current seizure status, the desired outcome is that the system determines if the equipment is currently seized and eligible for release.
💻 Technical Criteria
Given Equipment exists in the train consist
When The system validates the equipment's current seizure status
Then The system determines if the equipment is currently seized and eligible for release
R-GCX016E-cbl-00252 Equipment Currently Seized?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment Currently Seized?' is invoked, and assuming that equipment seizure status has been validated, when the system checks if the equipment is currently seized, the desired outcome is that the system proceeds with seizure release if equipment is seized or generates warning if equipment is not seized.
💻 Technical Criteria
Given Equipment seizure status has been validated
When The system checks if the equipment is currently seized
Then The system proceeds with seizure release if equipment is seized or generates warning if equipment is not seized
R-GCX016E-cbl-00253 Remove Equipment Seizure Flag
Action Rules
📊 Business Logic Narrative
When the process 'Remove Equipment Seizure Flag' is invoked, and assuming that equipment is currently seized and eligible for release, when the system processes the seizure release request, the desired outcome is that the seizure flag is removed from the equipment record.
💻 Technical Criteria
Given Equipment is currently seized and eligible for release
When The system processes the seizure release request
Then The seizure flag is removed from the equipment record
R-GCX016E-cbl-00254 Update Equipment Status in Train
Action Rules
📊 Business Logic Narrative
When the process 'Update Equipment Status in Train' is invoked, and assuming that equipment seizure flag has been removed, when the system updates the train equipment list, the desired outcome is that the equipment status is updated to reflect the seizure release in the train consist.
💻 Technical Criteria
Given Equipment seizure flag has been removed
When The system updates the train equipment list
Then The equipment status is updated to reflect the seizure release in the train consist
R-GCX016E-cbl-00255 Decrement Train Seizure Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Decrement Train Seizure Counter' is invoked, and assuming that equipment status has been updated in the train, when the system processes the seizure release, the desired outcome is that the train seizure counter is decremented by one.
💻 Technical Criteria
Given Equipment status has been updated in the train
When The system processes the seizure release
Then The train seizure counter is decremented by one
R-GCX016E-cbl-00256 All Equipment Released from Seizure?
Decision Rules
📊 Business Logic Narrative
When the process 'All Equipment Released from Seizure?' is invoked, and assuming that train seizure counter has been decremented, when the system checks if any equipment remains seized in the train, the desired outcome is that the system determines if all equipment is released from seizure and proceeds accordingly.
💻 Technical Criteria
Given Train seizure counter has been decremented
When The system checks if any equipment remains seized in the train
Then The system determines if all equipment is released from seizure and proceeds accordingly
R-GCX016E-cbl-00257 Clear Train Seizure Status
Action Rules
📊 Business Logic Narrative
When the process 'Clear Train Seizure Status' is invoked, and assuming that all equipment in the train has been released from seizure, when the system processes the final seizure release, the desired outcome is that the train seizure status is cleared and the train is no longer considered seized.
💻 Technical Criteria
Given All equipment in the train has been released from seizure
When The system processes the final seizure release
Then The train seizure status is cleared and the train is no longer considered seized
R-GCX016E-cbl-00258 Log Equipment Seizure Release Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Equipment Seizure Release Action' is invoked, and assuming that equipment seizure release has been processed, when the system completes the seizure release action, the desired outcome is that the seizure release action is logged with equipment details and timestamp.
💻 Technical Criteria
Given Equipment seizure release has been processed
When The system completes the seizure release action
Then The seizure release action is logged with equipment details and timestamp
R-GCX016E-cbl-00259 Generate Merlin Notification Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Merlin Notification Message' is invoked, and assuming that equipment seizure release action has been logged, when the system prepares external notifications, the desired outcome is that a merlin notification message is generated with seizure release details.
💻 Technical Criteria
Given Equipment seizure release action has been logged
When The system prepares external notifications
Then A Merlin notification message is generated with seizure release details
R-GCX016E-cbl-00260 Send Equipment Release Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send Equipment Release Notification' is invoked, and assuming that merlin notification message has been generated, when the system sends external notifications, the desired outcome is that the equipment seizure release notification is transmitted to relevant external systems.
💻 Technical Criteria
Given Merlin notification message has been generated
When The system sends external notifications
Then The equipment seizure release notification is transmitted to relevant external systems
R-GCX016E-cbl-00261 Generate Error - Equipment Not Found
Validation Rules
📊 Business Logic Narrative
When the process 'Generate Error - Equipment Not Found' is invoked, and assuming that equipment id is provided for seizure release, when the equipment cannot be found in the train equipment list, the desired outcome is that an equipment not found error is generated and processing terminates.
💻 Technical Criteria
Given Equipment ID is provided for seizure release
When The equipment cannot be found in the train equipment list
Then An equipment not found error is generated and processing terminates
R-GCX016E-cbl-00262 Generate Warning - Equipment Not Seized
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Warning - Equipment Not Seized', assuming that equipment exists in the train but is not currently seized, when a seizure release request is processed for non-seized equipment, the desired outcome is that a warning is generated indicating equipment is not seized and processing continues.
💻 Technical Criteria
EXCLUDING Equipment exists in the train but is not currently seized
When A seizure release request is processed for non-seized equipment
Then A warning is generated indicating equipment is not seized and processing continues
R-GCX016E-cbl-00276 Set Train as Arrived in System
Action Rules
📊 Business Logic Narrative
When the process 'Set Train as Arrived in System' is invoked, and assuming that a train has completed arrival processing steps, when the system needs to record the train's arrived status, the desired outcome is that set the system flag to indicate the train is now arrived and available for cargo operations.
💻 Technical Criteria
Given A train has completed arrival processing steps
When The system needs to record the train's arrived status
Then Set the system flag to indicate the train is now arrived and available for cargo operations
R-GCX016E-cbl-00277 Process US Cargo Arrival Notifications
Process Rules
📊 Business Logic Narrative
When the process 'Process US Cargo Arrival Notifications' is invoked, and assuming that a train has arrived and contains us cargo manifests, when cargo arrival notifications need to be processed, the desired outcome is that process arrival notifications for all us cargos associated with this train.
💻 Technical Criteria
Given A train has arrived and contains US cargo manifests
When Cargo arrival notifications need to be processed
Then Process arrival notifications for all US cargos associated with this train
R-GCX016E-cbl-00291 Identify US Cargo on Train
Process Rules
📊 Business Logic Narrative
When the process 'Identify US Cargo on Train' is invoked, and assuming that a train arrival has been processed (either export or import), when the system scans the train's cargo manifest, the desired outcome is that all us cargo shipments on the train are identified and flagged for aei notification processing.
💻 Technical Criteria
Given A train arrival has been processed (either export or import)
When The system scans the train's cargo manifest
Then All US cargo shipments on the train are identified and flagged for AEI notification processing
R-GCX016E-cbl-00292 Generate AEI Arrival Messages
Action Rules
📊 Business Logic Narrative
When the process 'Generate AEI Arrival Messages' is invoked, and assuming that us cargo has been identified on an arriving train, when the system generates aei arrival messages, the desired outcome is that automatic equipment identification messages are created containing arrival details for each us cargo shipment.
💻 Technical Criteria
Given US cargo has been identified on an arriving train
When The system generates AEI arrival messages
Then Automatic Equipment Identification messages are created containing arrival details for each US cargo shipment
R-GCX016E-cbl-00293 Send Equipment Identification Data
Action Rules
📊 Business Logic Narrative
When the process 'Send Equipment Identification Data' is invoked, and assuming that aei arrival messages have been generated, when the system sends equipment identification data, the desired outcome is that equipment identification information is transmitted to designated recipients and systems.
💻 Technical Criteria
Given AEI arrival messages have been generated
When The system sends equipment identification data
Then Equipment identification information is transmitted to designated recipients and systems
R-GCX016E-cbl-00294 Create Email Notifications
Action Rules
📊 Business Logic Narrative
When the process 'Create Email Notifications' is invoked, and assuming that equipment identification data has been sent, when the system creates email notifications, the desired outcome is that email notifications are generated with aei arrival details for appropriate distribution.
💻 Technical Criteria
Given Equipment identification data has been sent
When The system creates email notifications
Then Email notifications are generated with AEI arrival details for appropriate distribution
R-GCX016E-cbl-00299 Extract Bond Number from X4 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Bond Number from X4 Segment' is invoked, and assuming that an x4 segment contains disposition code information with bond number data, when the system processes the x4 segment for bond-based cargo processing, the desired outcome is that the bond number is extracted and stored for subsequent cargo lookup operations.
💻 Technical Criteria
Given An X4 segment contains disposition code information with bond number data
When The system processes the X4 segment for bond-based cargo processing
Then The bond number is extracted and stored for subsequent cargo lookup operations
R-GCX016E-cbl-00300 126: Cargo Database Lookup by Bond Number
Action Rules
📊 Business Logic Narrative
When the process '126: Cargo Database Lookup by Bond Number' is invoked, and assuming that a valid customs bond number has been extracted from the x4 segment, when the system performs a database lookup using the bond number as search criteria, the desired outcome is that all cargo records matching the bond number are identified and made available for processing.
💻 Technical Criteria
Given A valid customs bond number has been extracted from the X4 segment
When The system performs a database lookup using the bond number as search criteria
Then All cargo records matching the bond number are identified and made available for processing
R-GCX016E-cbl-00301 Cargo Records Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Cargo Records Found?' is invoked, and assuming that a database lookup has been performed using a customs bond number, when the system evaluates the search results, the desired outcome is that if cargo records are found, processing continues with the first record; if no records are found, bond processing is terminated.
💻 Technical Criteria
Given A database lookup has been performed using a customs bond number
When The system evaluates the search results
Then If cargo records are found, processing continues with the first record; if no records are found, bond processing is terminated
R-GCX016E-cbl-00302 Retrieve First Cargo Record by Bond
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve First Cargo Record by Bond' is invoked, and assuming that cargo records exist for the specified bond number, when the system begins processing cargo records for the bond, the desired outcome is that the first cargo record is retrieved and prepared for individual cargo processing.
💻 Technical Criteria
Given Cargo records exist for the specified bond number
When The system begins processing cargo records for the bond
Then The first cargo record is retrieved and prepared for individual cargo processing
R-GCX016E-cbl-00303 Process Individual Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Process Individual Cargo Record' is invoked, and assuming that a cargo record has been retrieved for processing, when the system processes the individual cargo record, the desired outcome is that the cargo record is prepared for disposition code application and status updates.
💻 Technical Criteria
Given A cargo record has been retrieved for processing
When The system processes the individual cargo record
Then The cargo record is prepared for disposition code application and status updates
R-GCX016E-cbl-00304 Apply Disposition Code to Cargo
Decision Rules
📊 Business Logic Narrative
When the process 'Apply Disposition Code to Cargo' is invoked, and assuming that a cargo record is being processed and a disposition code exists from the x4 segment, when the system applies the disposition code to the cargo, the desired outcome is that the disposition code is processed according to its type (hold, release, proceed, etc.) and appropriate cargo actions are determined.
💻 Technical Criteria
Given A cargo record is being processed and a disposition code exists from the X4 segment
When The system applies the disposition code to the cargo
Then The disposition code is processed according to its type (hold, release, proceed, etc.) and appropriate cargo actions are determined
R-GCX016E-cbl-00305 Update Cargo Status
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status' is invoked, and assuming that a disposition code has been applied to a cargo record, when the system updates the cargo status, the desired outcome is that the cargo status is modified according to the disposition code requirements and status change records are created.
💻 Technical Criteria
Given A disposition code has been applied to a cargo record
When The system updates the cargo status
Then The cargo status is modified according to the disposition code requirements and status change records are created
R-GCX016E-cbl-00306 Check for Additional Cargo Records
Process Rules
📊 Business Logic Narrative
When the process 'Check for Additional Cargo Records' is invoked, and assuming that one cargo record has been processed for a bond number, when the system checks for additional cargo records with the same bond, the desired outcome is that the system identifies whether more cargo records exist for continued processing.
💻 Technical Criteria
Given One cargo record has been processed for a bond number
When The system checks for additional cargo records with the same bond
Then The system identifies whether more cargo records exist for continued processing
R-GCX016E-cbl-00307 More Cargo with Same Bond?
Decision Rules
📊 Business Logic Narrative
When the process 'More Cargo with Same Bond?' is invoked, and assuming that the system has checked for additional cargo records with the same bond number, when the evaluation determines if more records exist, the desired outcome is that if more records exist, processing continues with the next record; if no more records exist, bond processing summary is generated.
💻 Technical Criteria
Given The system has checked for additional cargo records with the same bond number
When The evaluation determines if more records exist
Then If more records exist, processing continues with the next record; if no more records exist, bond processing summary is generated
R-GCX016E-cbl-00308 Retrieve Next Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Next Cargo Record' is invoked, and assuming that additional cargo records exist for the same bond number, when the system retrieves the next cargo record, the desired outcome is that the next cargo record is obtained and prepared for individual cargo processing.
💻 Technical Criteria
Given Additional cargo records exist for the same bond number
When The system retrieves the next cargo record
Then The next cargo record is obtained and prepared for individual cargo processing
R-GCX016E-cbl-00309 Generate Bond Processing Summary
Process Rules
📊 Business Logic Narrative
When the process 'Generate Bond Processing Summary' is invoked, and assuming that all cargo records associated with a bond number have been processed, when the system generates a bond processing summary, the desired outcome is that a summary report is created containing details of all cargo records processed and their final status.
💻 Technical Criteria
Given All cargo records associated with a bond number have been processed
When The system generates a bond processing summary
Then A summary report is created containing details of all cargo records processed and their final status
R-GCX016E-cbl-02887 Set Bond Number as Search Key
Process Rules
📊 Business Logic Narrative
When the process 'Set Bond Number as Search Key' is invoked, and assuming that a valid bond number has been extracted and validated, when the system prepares to search for cargo records, the desired outcome is that the bond number is set as the primary search key for database operations.
💻 Technical Criteria
Given A valid bond number has been extracted and validated
When The system prepares to search for cargo records
Then The bond number is set as the primary search key for database operations
R-GCX016E-cbl-02888 Call Database Lookup - GCCUSIO2
Action Rules
📊 Business Logic Narrative
When the process 'Call Database Lookup - GCCUSIO2' is invoked, and assuming that a bond number search key has been established, when the system needs to retrieve cargo records for the bond, the desired outcome is that the gccusio2 database service is called to perform the lookup operation.
💻 Technical Criteria
Given A bond number search key has been established
When The system needs to retrieve cargo records for the bond
Then The GCCUSIO2 database service is called to perform the lookup operation
R-GCX016E-cbl-02889 Retrieve First Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve First Cargo Record' is invoked, and assuming that database lookup has been initiated for a specific bond number, when the system processes the database response, the desired outcome is that the first cargo record associated with the bond number is retrieved for processing.
💻 Technical Criteria
Given Database lookup has been initiated for a specific bond number
When The system processes the database response
Then The first cargo record associated with the bond number is retrieved for processing
R-GCX016E-cbl-02891 Validate Status Code
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Status Code' is invoked, and assuming that a cargo record has been retrieved from the database, when the system examines the cargo record status code, the desired outcome is that the record is validated to ensure it has an acceptable status for bond processing.
💻 Technical Criteria
Given A cargo record has been retrieved from the database
When The system examines the cargo record status code
Then The record is validated to ensure it has an acceptable status for bond processing
R-GCX016E-cbl-02892 Status Code Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Status Code Valid?' is invoked, and assuming that a cargo record status code has been validated, when the system evaluates the status code against business rules, the desired outcome is that the record is accepted for processing if status is valid, otherwise it is skipped.
💻 Technical Criteria
Given A cargo record status code has been validated
When The system evaluates the status code against business rules
Then The record is accepted for processing if status is valid, otherwise it is skipped
R-GCX016E-cbl-02893 Store Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Store Cargo Record' is invoked, and assuming that a cargo record has passed status code validation, when the system processes the valid record, the desired outcome is that the cargo record is stored in the processing collection for bond operations.
💻 Technical Criteria
Given A cargo record has passed status code validation
When The system processes the valid record
Then The cargo record is stored in the processing collection for bond operations
R-GCX016E-cbl-02894 Get Next Cargo Record with Same Bond
Process Rules
📊 Business Logic Narrative
When the process 'Get Next Cargo Record with Same Bond' is invoked, and assuming that at least one cargo record has been found for a bond number, when the system searches for additional records with the same bond, the desired outcome is that all remaining cargo records associated with the bond number are retrieved sequentially.
💻 Technical Criteria
Given At least one cargo record has been found for a bond number
When The system searches for additional records with the same bond
Then All remaining cargo records associated with the bond number are retrieved sequentially
R-GCX016E-cbl-02895 More Records?
Decision Rules
📊 Business Logic Narrative
When the process 'More Records?' is invoked, and assuming that the system is retrieving cargo records for a bond number, when each record retrieval operation completes, the desired outcome is that processing continues if more records exist, otherwise the bond collection is considered complete.
💻 Technical Criteria
Given The system is retrieving cargo records for a bond number
When Each record retrieval operation completes
Then Processing continues if more records exist, otherwise the bond collection is considered complete
R-GCX016E-cbl-02896 Process All Bond Cargo Records
Process Rules
📊 Business Logic Narrative
When the process 'Process All Bond Cargo Records' is invoked, and assuming that all cargo records for a bond number have been collected and validated, when the system completes the bond record collection process, the desired outcome is that all valid cargo records in the bond collection are processed according to business rules.
💻 Technical Criteria
Given All cargo records for a bond number have been collected and validated
When The system completes the bond record collection process
Then All valid cargo records in the bond collection are processed according to business rules
R-GCX016E-cbl-02897 Generate Bond Not Found Error
Action Rules
📊 Business Logic Narrative
When the process 'Generate Bond Not Found Error' is invoked, and assuming that a bond number search has been performed, when no valid cargo records are found for the bond number, the desired outcome is that a bond not found error is generated and appropriate error handling is initiated.
💻 Technical Criteria
Given A bond number search has been performed
When No valid cargo records are found for the bond number
Then A bond not found error is generated and appropriate error handling is initiated
R-GCX016E-cbl-02898 Skip Invalid Status Record
Process Rules
📊 Business Logic Narrative
When the process 'Skip Invalid Status Record' is invoked, and assuming that a cargo record has been retrieved but has an invalid status code, when the system evaluates the record for processing eligibility, the desired outcome is that the record is skipped and the system continues to search for additional valid records.
💻 Technical Criteria
Given A cargo record has been retrieved but has an invalid status code
When The system evaluates the record for processing eligibility
Then The record is skipped and the system continues to search for additional valid records
R-GCX016E-cbl-03148 Retrieve Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Cargo Record' is invoked, and assuming that a cargo identification number is provided for processing, when the system needs to validate cargo status, the desired outcome is that the cargo record is retrieved from the us cargo root database.
💻 Technical Criteria
Given A cargo identification number is provided for processing
When The system needs to validate cargo status
Then The cargo record is retrieved from the US Cargo Root database
R-GCX016E-cbl-03149 Cargo Status Code Check
Validation Rules
📊 Business Logic Narrative
When the process 'Cargo Status Code Check' is invoked, and assuming that a cargo record has been retrieved from the database, when the system examines the cargo status code field, the desired outcome is that the status code is validated against acceptable values for processing eligibility.
💻 Technical Criteria
Given A cargo record has been retrieved from the database
When The system examines the cargo status code field
Then The status code is validated against acceptable values for processing eligibility
R-GCX016E-cbl-03150 Check Deleted Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check Deleted Status' is invoked, and assuming that a cargo record with status code information is available, when the system checks the cargo deletion status indicator, the desired outcome is that the cargo is identified as deleted or active based on the status flag.
💻 Technical Criteria
Given A cargo record with status code information is available
When The system checks the cargo deletion status indicator
Then The cargo is identified as deleted or active based on the status flag
R-GCX016E-cbl-03151 Is Cargo Deleted?
Decision Rules
📊 Business Logic Narrative
When the process 'Is Cargo Deleted?' is invoked, and assuming that a cargo record has been checked for deletion status, when the cargo is marked as deleted, the desired outcome is that the cargo is excluded from processing and marked as invalid for operations.
💻 Technical Criteria
Given A cargo record has been checked for deletion status
When The cargo is marked as deleted
Then The cargo is excluded from processing and marked as invalid for operations
R-GCX016E-cbl-03152 Check New Bond Creation Status
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Check New Bond Creation Status', assuming that a cargo record is not marked as deleted, when the system examines the bond creation status, the desired outcome is that the new bond creation flag is evaluated to determine processing eligibility.
💻 Technical Criteria
EXCLUDING A cargo record is not marked as deleted
When The system examines the bond creation status
Then The new bond creation flag is evaluated to determine processing eligibility
R-GCX016E-cbl-03153 New Bond Created?
Decision Rules
📊 Business Logic Narrative
When the process 'New Bond Created?' is invoked, and assuming that a cargo record has been checked for new bond creation status, when the cargo is associated with a newly created bond, the desired outcome is that the cargo is excluded from processing to prevent conflicts with bond creation procedures.
💻 Technical Criteria
Given A cargo record has been checked for new bond creation status
When The cargo is associated with a newly created bond
Then The cargo is excluded from processing to prevent conflicts with bond creation procedures
R-GCX016E-cbl-03154 Verify Active Status
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Verify Active Status', assuming that a cargo record is not deleted and not associated with a new bond creation, when the system verifies the active status of the cargo, the desired outcome is that the cargo active status is confirmed against business rules for processing eligibility.
💻 Technical Criteria
EXCLUDING A cargo record is not deleted and not associated with a new bond creation
When The system verifies the active status of the cargo
Then The cargo active status is confirmed against business rules for processing eligibility
R-GCX016E-cbl-03155 Is Status Active?
Decision Rules
📊 Business Logic Narrative
When the process 'Is Status Active?' is invoked, and assuming that a cargo record has been verified for active status, when the cargo status is confirmed as active, the desired outcome is that the cargo is marked as valid for processing operations.
💻 Technical Criteria
Given A cargo record has been verified for active status
When The cargo status is confirmed as active
Then The cargo is marked as valid for processing operations
R-GCX016E-cbl-03156 Mark as Valid for Processing
Decision Rules
📊 Business Logic Narrative
When the process 'Mark as Valid for Processing' is invoked, and assuming that a cargo record has passed all validation checks including deletion status, bond creation status, and active status, when all validation criteria are met, the desired outcome is that the cargo is marked as valid and approved for subsequent processing operations.
💻 Technical Criteria
Given A cargo record has passed all validation checks including deletion status, bond creation status, and active status
When All validation criteria are met
Then The cargo is marked as valid and approved for subsequent processing operations
R-GCX016E-cbl-03157 Log Validation Result
Process Rules
📊 Business Logic Narrative
When the process 'Log Validation Result' is invoked, and assuming that cargo status validation has been completed with either valid or invalid result, when the validation process concludes, the desired outcome is that the validation result is logged with cargo identification and validation outcome details.
💻 Technical Criteria
Given Cargo status validation has been completed with either valid or invalid result
When The validation process concludes
Then The validation result is logged with cargo identification and validation outcome details
R-GCX016E-cbl-03158 Continue with Cargo Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue with Cargo Processing' is invoked, and assuming that cargo status validation has been completed and results have been logged, when the cargo is marked as valid for processing, the desired outcome is that the system continues with the next phase of cargo processing operations.
💻 Technical Criteria
Given Cargo status validation has been completed and results have been logged
When The cargo is marked as valid for processing
Then The system continues with the next phase of cargo processing operations
R-GCX016E-cbl-00311 Extract Equipment ID from N7 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment ID from N7 Segment' is invoked, and assuming that an n7 equipment segment is available for processing, when the system processes the n7 segment to extract equipment information, the desired outcome is that the equipment initial and equipment number are extracted and combined to form the equipment id.
💻 Technical Criteria
Given An N7 equipment segment is available for processing
When The system processes the N7 segment to extract equipment information
Then The equipment initial and equipment number are extracted and combined to form the equipment ID
R-GCX016E-cbl-00313 Format Car ID Using Standard Rules
Computation Rules
📊 Business Logic Narrative
When the process 'Format Car ID Using Standard Rules' is invoked, and assuming that equipment initial and equipment number have been extracted from n7 segment, when the system needs to create a standardized car id, the desired outcome is that the car id is formatted by combining equipment initial and equipment number according to standard formatting rules.
💻 Technical Criteria
Given Equipment initial and equipment number have been extracted from N7 segment
When The system needs to create a standardized car ID
Then The car ID is formatted by combining equipment initial and equipment number according to standard formatting rules
R-GCX016E-cbl-00317 Process Individual Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Process Individual Cargo Record' is invoked, and assuming that a cargo record has been retrieved for processing, when the system processes the cargo record, the desired outcome is that the cargo record is processed with applicable disposition codes, status updates, and business rule validations.
💻 Technical Criteria
Given A cargo record has been retrieved for processing
When The system processes the cargo record
Then The cargo record is processed with applicable disposition codes, status updates, and business rule validations
R-GCX016E-cbl-00322 Create New CPRS Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Create New CPRS Cargo Record' is invoked, and assuming that no existing cargo records exist and the traffic is identified as cprs, when the system creates a new cargo record, the desired outcome is that a new cprs cargo record is created with appropriate cprs-specific attributes and processing rules.
💻 Technical Criteria
Given No existing cargo records exist and the traffic is identified as CPRS
When The system creates a new cargo record
Then A new CPRS cargo record is created with appropriate CPRS-specific attributes and processing rules
R-GCX016E-cbl-02900 Format Car ID Using Standard Rules
Definitional Rules
📊 Business Logic Narrative
When the process 'Format Car ID Using Standard Rules' is invoked, and assuming that a raw car id has been extracted from the x4 segment, when the system prepares the car id for database search, the desired outcome is that car id is formatted according to standard business formatting rules for consistent lookup.
💻 Technical Criteria
Given A raw car ID has been extracted from the X4 segment
When The system prepares the car ID for database search
Then Car ID is formatted according to standard business formatting rules for consistent lookup
R-GCX016E-cbl-02906 Handle CPRS Special Processing
Policy Rules
📊 Business Logic Narrative
When the process 'Handle CPRS Special Processing' is invoked, and assuming that traffic has been identified as cprs type, when the system processes cprs cargo, the desired outcome is that special cprs business rules are applied including carrier validation and record creation logic.
💻 Technical Criteria
Given Traffic has been identified as CPRS type
When The system processes CPRS cargo
Then Special CPRS business rules are applied including carrier validation and record creation logic
R-GCX016E-cbl-02909 Create New Record?
Decision Rules
📊 Business Logic Narrative
When the process 'Create New Record?' is invoked, and assuming that no existing cargo records were found and traffic type has been determined, when the system evaluates record creation requirements, the desired outcome is that system determines if a new cargo record should be created based on business rules.
💻 Technical Criteria
Given No existing cargo records were found and traffic type has been determined
When The system evaluates record creation requirements
Then System determines if a new cargo record should be created based on business rules
R-GCX016E-cbl-02910 Create New CPRS Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Create New CPRS Cargo Record' is invoked, and assuming that a new record is required for cprs traffic, when the system creates the cargo record, the desired outcome is that new cprs cargo record is created with cprs-specific business attributes and processing rules.
💻 Technical Criteria
Given A new record is required for CPRS traffic
When The system creates the cargo record
Then New CPRS cargo record is created with CPRS-specific business attributes and processing rules
R-GCX016E-cbl-02911 Create New Foreign Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Create New Foreign Cargo Record' is invoked, and assuming that a new record is required for non-cprs foreign traffic, when the system creates the cargo record, the desired outcome is that new foreign cargo record is created with standard business attributes and processing rules.
💻 Technical Criteria
Given A new record is required for non-CPRS foreign traffic
When The system creates the cargo record
Then New foreign cargo record is created with standard business attributes and processing rules
R-GCX016E-cbl-02912 Initialize New Record with X4/N7 Data
Process Rules
📊 Business Logic Narrative
When the process 'Initialize New Record with X4/N7 Data' is invoked, and assuming that a new cargo record has been created, when the system initializes the record with segment data, the desired outcome is that record is populated with disposition codes from x4 segment and equipment data from n7 segment.
💻 Technical Criteria
Given A new cargo record has been created
When The system initializes the record with segment data
Then Record is populated with disposition codes from X4 segment and equipment data from N7 segment
R-GCX016E-cbl-02913 Insert New Record into Database
Action Rules
📊 Business Logic Narrative
When the process 'Insert New Record into Database' is invoked, and assuming that a new cargo record has been created and initialized with segment data, when the system saves the record, the desired outcome is that new cargo record is inserted into the cargo database and becomes available for processing.
💻 Technical Criteria
Given A new cargo record has been created and initialized with segment data
When The system saves the record
Then New cargo record is inserted into the cargo database and becomes available for processing
R-GCX016E-cbl-02914 Log Cargo Creation Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Cargo Creation Action' is invoked, and assuming that a new cargo record has been successfully inserted into the database, when the system completes the creation process, the desired outcome is that cargo creation action is logged with relevant business details for audit and tracking purposes.
💻 Technical Criteria
Given A new cargo record has been successfully inserted into the database
When The system completes the creation process
Then Cargo creation action is logged with relevant business details for audit and tracking purposes
R-GCX016E-cbl-03160 Search Cargo by Car ID
Action Rules
📊 Business Logic Narrative
When the process 'Search Cargo by Car ID' is invoked, and assuming that cprs traffic processing is initiated and scac code status is determined, when the system searches for cargo records using car id, the desired outcome is that retrieve matching cargo records based on car identification number.
💻 Technical Criteria
Given CPRS traffic processing is initiated and SCAC code status is determined
When the system searches for cargo records using car ID
Then retrieve matching cargo records based on car identification number
R-GCX016E-cbl-03165 Create New CPRS Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Create New CPRS Cargo Record' is invoked, and assuming that cprs cargo creation rules have been applied successfully, when the system creates new cprs cargo record, the desired outcome is that establish new cargo record with cprs-specific data structure and attributes.
💻 Technical Criteria
Given CPRS cargo creation rules have been applied successfully
When the system creates new CPRS cargo record
Then establish new cargo record with CPRS-specific data structure and attributes
R-GCX016E-cbl-03166 Initialize CPRS-Specific Fields
Action Rules
📊 Business Logic Narrative
When the process 'Initialize CPRS-Specific Fields' is invoked, and assuming that new cprs cargo record has been created, when the system initializes cprs-specific fields, the desired outcome is that set default values and initialize all cprs-required data fields.
💻 Technical Criteria
Given new CPRS cargo record has been created
When the system initializes CPRS-specific fields
Then set default values and initialize all CPRS-required data fields
R-GCX016E-cbl-00325 Valid Disposition Code?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid Disposition Code?' is invoked, and assuming that a disposition code is received for cargo processing, when the system validates the disposition code against the dc table, the desired outcome is that if the disposition code exists in the dc table, continue processing; if not found, generate an error message for invalid disposition code.
💻 Technical Criteria
Given A disposition code is received for cargo processing
When The system validates the disposition code against the DC table
Then If the disposition code exists in the DC table, continue processing; if not found, generate an error message for invalid disposition code
R-GCX016E-cbl-00326 Duplicate Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Duplicate Found?' is invoked, and assuming that a disposition code is being added to a cargo's status array, when the system searches the existing status array for the same disposition code with matching entry number and quantity, the desired outcome is that if an exact duplicate is found, skip processing and continue; if no duplicate exists, proceed with adding the disposition code.
💻 Technical Criteria
Given A disposition code is being added to a cargo's status array
When The system searches the existing status array for the same disposition code with matching entry number and quantity
Then If an exact duplicate is found, skip processing and continue; if no duplicate exists, proceed with adding the disposition code
R-GCX016E-cbl-00328 Status Change Required?
Decision Rules
📊 Business Logic Narrative
When the process 'Status Change Required?' is invoked, and assuming that disposition codes have been processed and the status array is updated, when the system evaluates all disposition codes in the status array to determine the final cargo status, the desired outcome is that if the evaluated status differs from the current cargo status, proceed with status update; otherwise, complete processing without changes.
💻 Technical Criteria
Given Disposition codes have been processed and the status array is updated
When The system evaluates all disposition codes in the status array to determine the final cargo status
Then If the evaluated status differs from the current cargo status, proceed with status update; otherwise, complete processing without changes
R-GCX016E-cbl-00329 Calculate Release Quantities
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Release Quantities' is invoked, and assuming that the cargo has release disposition codes in its status array, when the system calculates the total released quantity by summing all release quantities from disposition codes, the desired outcome is that update the cargo's released quantity field with the calculated total and determine if the cargo is fully released, partially released, or held.
💻 Technical Criteria
Given The cargo has release disposition codes in its status array
When The system calculates the total released quantity by summing all release quantities from disposition codes
Then Update the cargo's released quantity field with the calculated total and determine if the cargo is fully released, partially released, or held
R-GCX016E-cbl-00330 Set Hold Flags
Decision Rules
📊 Business Logic Narrative
When the process 'Set Hold Flags' is invoked, and assuming that the cargo has hold disposition codes in its status array, when the system evaluates hold codes for border holds, destination holds, or fda holds, the desired outcome is that set the corresponding hold flags (held at border, held at destination, held for fda) and update the cargo status to reflect the hold condition.
💻 Technical Criteria
Given The cargo has hold disposition codes in its status array
When The system evaluates hold codes for border holds, destination holds, or FDA holds
Then Set the corresponding hold flags (held at border, held at destination, held for FDA) and update the cargo status to reflect the hold condition
R-GCX016E-cbl-00331 Set Release Flags
Decision Rules
📊 Business Logic Narrative
When the process 'Set Release Flags' is invoked, and assuming that the cargo has release disposition codes in its status array, when the system validates that the release quantity meets or exceeds the cargo quantity, the desired outcome is that set the released flag to true and update the cargo status to relsd (released) or holdpcs (hold pieces) based on partial release conditions.
💻 Technical Criteria
Given The cargo has release disposition codes in its status array
When The system validates that the release quantity meets or exceeds the cargo quantity
Then Set the released flag to true and update the cargo status to RELSD (Released) or HOLDPCS (Hold Pieces) based on partial release conditions
R-GCX016E-cbl-00332 Process In-Bond Entry
Process Rules
📊 Business Logic Narrative
When the process 'Process In-Bond Entry' is invoked, and assuming that the cargo has a proceed disposition code and entry type is 61, 62, 63, or 69, when the system processes the proceed status, the desired outcome is that update the cargo's in-bond information including broker details, bond numbers, and entry information, and set the cargo status to proceed.
💻 Technical Criteria
Given The cargo has a proceed disposition code and entry type is 61, 62, 63, or 69
When The system processes the proceed status
Then Update the cargo's in-bond information including broker details, bond numbers, and entry information, and set the cargo status to PROCEED
R-GCX016E-cbl-00333 Update Arrival/Export Flags
Process Rules
📊 Business Logic Narrative
When the process 'Update Arrival/Export Flags' is invoked, and assuming that the cargo has arrival or export disposition codes in its status array, when the system processes arrival or export status changes, the desired outcome is that for arrival codes, set arrival flag and update arrival date; for export codes, set export flag and clear destination index; update cargo status to arrival or export accordingly.
💻 Technical Criteria
Given The cargo has arrival or export disposition codes in its status array
When The system processes arrival or export status changes
Then For arrival codes, set arrival flag and update arrival date; for export codes, set export flag and clear destination index; update cargo status to ARRIVAL or EXPORT accordingly
R-GCX016E-cbl-00334 Generate Status Notifications
Action Rules
📊 Business Logic Narrative
When the process 'Generate Status Notifications' is invoked, and assuming that a cargo status has been updated with new disposition codes, when the system determines notification requirements based on the status change and freight forwarder setup, the desired outcome is that generate merlin messages for brokers, send email notifications to freight forwarders if configured, and make iis calls for equipment tracking as appropriate.
💻 Technical Criteria
Given A cargo status has been updated with new disposition codes
When The system determines notification requirements based on the status change and freight forwarder setup
Then Generate Merlin messages for brokers, send email notifications to freight forwarders if configured, and make IIS calls for equipment tracking as appropriate
R-GCX016E-cbl-02917 44: Duplicate Disposition Code Detection
Validation Rules
📊 Business Logic Narrative
When the process '44: Duplicate Disposition Code Detection' is invoked, and assuming that a valid disposition code needs to be added to the cargo status array, when the system searches the existing s09a status array for the same disposition code with matching entry number and quantity, the desired outcome is that if an exact duplicate is found, skip processing and do not add the code again.
💻 Technical Criteria
Given A valid disposition code needs to be added to the cargo status array
When The system searches the existing S09A status array for the same disposition code with matching entry number and quantity
Then If an exact duplicate is found, skip processing and do not add the code again
R-GCX016E-cbl-02919 157: Status Array Management and Processing
Process Rules
📊 Business Logic Narrative
When the process '157: Status Array Management and Processing' is invoked, and assuming that a validated disposition code needs to be added to the cargo status array, when the system processes the code insertion into the s09a status array, the desired outcome is that insert the new disposition code with its associated data (entry number, quantity, date/time) into the next available array position.
💻 Technical Criteria
Given A validated disposition code needs to be added to the cargo status array
When The system processes the code insertion into the S09A status array
Then Insert the new disposition code with its associated data (entry number, quantity, date/time) into the next available array position
R-GCX016E-cbl-03335 Load Current S09A Status Array
Action Rules
📊 Business Logic Narrative
When the process 'Load Current S09A Status Array' is invoked, and assuming that a cargo record exists with potential s09a status array data, when the status array loading process is executed, the desired outcome is that the current s09a status array is loaded into working storage for analysis.
💻 Technical Criteria
Given A cargo record exists with potential S09A status array data
When The status array loading process is executed
Then The current S09A status array is loaded into working storage for analysis
R-GCX016E-cbl-03336 Status Array Empty?
Decision Rules
📊 Business Logic Narrative
When the process 'Status Array Empty?' is invoked, and assuming that the s09a status array has been loaded, when the array is examined for content, the desired outcome is that if the array contains no entries, set array empty flag and terminate search; otherwise proceed with sequential search.
💻 Technical Criteria
Given The S09A status array has been loaded
When The array is examined for content
Then If the array contains no entries, set array empty flag and terminate search; otherwise proceed with sequential search
R-GCX016E-cbl-03337 Set Array Empty Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Array Empty Flag' is invoked, and assuming that the s09a status array has been examined and found to contain no entries, when the empty condition is confirmed, the desired outcome is that set the array empty flag to indicate no disposition codes exist for processing.
💻 Technical Criteria
Given The S09A status array has been examined and found to contain no entries
When The empty condition is confirmed
Then Set the array empty flag to indicate no disposition codes exist for processing
R-GCX016E-cbl-03464 Does Code Have Counterparts?
Validation Rules
📊 Business Logic Narrative
When the process 'Does Code Have Counterparts?' is invoked, and assuming that a disposition code is being processed for cargo status update, when the system checks the disposition code table for counterpart relationships, the desired outcome is that the system identifies if the code has any defined counterpart codes that require evaluation.
💻 Technical Criteria
Given A disposition code is being processed for cargo status update
When The system checks the disposition code table for counterpart relationships
Then The system identifies if the code has any defined counterpart codes that require evaluation
R-GCX016E-cbl-03466 Search Status Array for Counterparts
Decision Rules
📊 Business Logic Narrative
When the process 'Search Status Array for Counterparts' is invoked, and assuming that a list of counterpart codes has been retrieved from the disposition code table, when the system searches through the cargo's s09a status array, the desired outcome is that the system identifies any existing counterpart codes in the current status array.
💻 Technical Criteria
Given A list of counterpart codes has been retrieved from the disposition code table
When The system searches through the cargo's S09A status array
Then The system identifies any existing counterpart codes in the current status array
R-GCX016E-cbl-03468 Evaluate Regulatory Hierarchy
Policy Rules
📊 Business Logic Narrative
When the process 'Evaluate Regulatory Hierarchy' is invoked, and assuming that counterpart codes have been found in the cargo status array, when the system evaluates the regulatory hierarchy rules between codes, the desired outcome is that the system determines which code takes precedence based on regulatory requirements.
💻 Technical Criteria
Given Counterpart codes have been found in the cargo status array
When The system evaluates the regulatory hierarchy rules between codes
Then The system determines which code takes precedence based on regulatory requirements
R-GCX016E-cbl-03472 Remove Counterpart from Status Array
Action Rules
📊 Business Logic Narrative
When the process 'Remove Counterpart from Status Array' is invoked, and assuming that a counterpart code has been marked for removal and logged, when the system updates the cargo status array, the desired outcome is that the system removes the counterpart code from the s09a status array.
💻 Technical Criteria
Given A counterpart code has been marked for removal and logged
When The system updates the cargo status array
Then The system removes the counterpart code from the S09A status array
R-GCX016E-cbl-02922 Retrieve Current Cargo Status
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Cargo Status' is invoked, and assuming that a cargo record exists in the system, when the system needs to evaluate cargo status, the desired outcome is that the current cargo status, hold flags, release quantities, and processing flags are retrieved from the cargo record.
💻 Technical Criteria
Given A cargo record exists in the system
When The system needs to evaluate cargo status
Then The current cargo status, hold flags, release quantities, and processing flags are retrieved from the cargo record
R-GCX016E-cbl-02923 Analyze S09A Status Arrays
Process Rules
📊 Business Logic Narrative
When the process 'Analyze S09A Status Arrays' is invoked, and assuming that a cargo has s09a status arrays with disposition codes, when the system evaluates cargo status, the desired outcome is that all disposition codes in the status arrays are analyzed for hold conditions, release conditions, and quantity impacts.
💻 Technical Criteria
Given A cargo has S09A status arrays with disposition codes
When The system evaluates cargo status
Then All disposition codes in the status arrays are analyzed for hold conditions, release conditions, and quantity impacts
R-GCX016E-cbl-02924 Hold Conditions Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Hold Conditions Present?' is invoked, and assuming that a cargo with status arrays containing disposition codes, when the system checks for hold conditions, the desired outcome is that the system identifies if border holds, destination holds, fda holds, or piece count holds are active.
💻 Technical Criteria
Given A cargo with status arrays containing disposition codes
When The system checks for hold conditions
Then The system identifies if border holds, destination holds, FDA holds, or piece count holds are active
R-GCX016E-cbl-02925 Check Border Hold Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check Border Hold Status' is invoked, and assuming that a cargo with disposition codes in status arrays, when the system evaluates border hold conditions, the desired outcome is that the system determines if cargo is held at border based on specific disposition codes and location information.
💻 Technical Criteria
Given A cargo with disposition codes in status arrays
When The system evaluates border hold conditions
Then The system determines if cargo is held at border based on specific disposition codes and location information
R-GCX016E-cbl-02926 Check Destination Hold Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check Destination Hold Status' is invoked, and assuming that a cargo with disposition codes and destination information, when the system evaluates destination hold conditions, the desired outcome is that the system determines if cargo is held at destination based on disposition codes and destination location.
💻 Technical Criteria
Given A cargo with disposition codes and destination information
When The system evaluates destination hold conditions
Then The system determines if cargo is held at destination based on disposition codes and destination location
R-GCX016E-cbl-02927 Check FDA Hold Status
Policy Rules
📊 Business Logic Narrative
When the process 'Check FDA Hold Status' is invoked, and assuming that a cargo with disposition codes that may include fda-related holds, when the system evaluates fda hold conditions, the desired outcome is that the system determines if cargo requires fda clearance and sets holdfda status if applicable.
💻 Technical Criteria
Given A cargo with disposition codes that may include FDA-related holds
When The system evaluates FDA hold conditions
Then The system determines if cargo requires FDA clearance and sets HOLDFDA status if applicable
R-GCX016E-cbl-02928 Check Piece Count Hold Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check Piece Count Hold Status' is invoked, and assuming that a cargo with quantity information and release history, when the system evaluates piece count hold conditions, the desired outcome is that the system determines if cargo has piece count holds based on quantity discrepancies or partial release conditions.
💻 Technical Criteria
Given A cargo with quantity information and release history
When The system evaluates piece count hold conditions
Then The system determines if cargo has piece count holds based on quantity discrepancies or partial release conditions
R-GCX016E-cbl-02929 Check Manual Release Status
Authorization Rules
📊 Business Logic Narrative
When the process 'Check Manual Release Status' is invoked, and assuming that a cargo with disposition codes that may include manual release codes, when the system checks for manual release authorization, the desired outcome is that the system identifies if manual release (mrl) disposition codes are present and takes precedence over other status conditions.
💻 Technical Criteria
Given A cargo with disposition codes that may include manual release codes
When The system checks for manual release authorization
Then The system identifies if manual release (MRL) disposition codes are present and takes precedence over other status conditions
R-GCX016E-cbl-02930 Release Conditions Met?
Decision Rules
📊 Business Logic Narrative
When the process 'Release Conditions Met?' is invoked, and assuming that a cargo with analyzed hold and release conditions, when the system evaluates overall release eligibility, the desired outcome is that the system determines if cargo can be released based on absence of active holds and presence of valid release authorization.
💻 Technical Criteria
Given A cargo with analyzed hold and release conditions
When The system evaluates overall release eligibility
Then The system determines if cargo can be released based on absence of active holds and presence of valid release authorization
R-GCX016E-cbl-02931 Calculate Release Quantities
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Release Quantities' is invoked, and assuming that a cargo with disposition codes containing quantity information, when the system calculates release quantities, the desired outcome is that the system computes total cargo quantity, currently released quantity, remaining hold quantity, and validates quantity consistency across all disposition codes.
💻 Technical Criteria
Given A cargo with disposition codes containing quantity information
When The system calculates release quantities
Then The system computes total cargo quantity, currently released quantity, remaining hold quantity, and validates quantity consistency across all disposition codes
R-GCX016E-cbl-02932 Evaluate Proceed Conditions
Decision Rules
📊 Business Logic Narrative
When the process 'Evaluate Proceed Conditions' is invoked, and assuming that a cargo with analyzed status and release conditions, when the system evaluates proceed eligibility, the desired outcome is that the system determines if cargo can proceed based on release status, hold conditions, and processing requirements.
💻 Technical Criteria
Given A cargo with analyzed status and release conditions
When The system evaluates proceed eligibility
Then The system determines if cargo can proceed based on release status, hold conditions, and processing requirements
R-GCX016E-cbl-02933 In-Bond Entry?
Definitional Rules
📊 Business Logic Narrative
When the process 'In-Bond Entry?' is invoked, and assuming that a cargo with entry type information, when the system checks for in-bond entry classification, the desired outcome is that the system identifies if cargo has entry types 61, 62, 63, or 69 indicating in-bond processing requirements.
💻 Technical Criteria
Given A cargo with entry type information
When The system checks for in-bond entry classification
Then The system identifies if cargo has entry types 61, 62, 63, or 69 indicating in-bond processing requirements
R-GCX016E-cbl-02934 Process In-Bond Logic
Process Rules
📊 Business Logic Narrative
When the process 'Process In-Bond Logic' is invoked, and assuming that a cargo identified as in-bond entry type, when the system processes in-bond logic, the desired outcome is that the system sets in-bond information, updates broker details, handles bond numbers, and applies canadian border crossing vessel swap rules if applicable.
💻 Technical Criteria
Given A cargo identified as in-bond entry type
When The system processes in-bond logic
Then The system sets in-bond information, updates broker details, handles bond numbers, and applies Canadian border crossing vessel swap rules if applicable
R-GCX016E-cbl-02935 Set Master In-Bond Flags
Action Rules
📊 Business Logic Narrative
When the process 'Set Master In-Bond Flags' is invoked, and assuming that a cargo requiring in-bond processing, when the system sets master in-bond flags, the desired outcome is that the system establishes master-level in-bond indicators that control downstream processing and reporting.
💻 Technical Criteria
Given A cargo requiring in-bond processing
When The system sets master in-bond flags
Then The system establishes master-level in-bond indicators that control downstream processing and reporting
R-GCX016E-cbl-02936 Arrival Status Required?
Decision Rules
📊 Business Logic Narrative
When the process 'Arrival Status Required?' is invoked, and assuming that a cargo with disposition codes and location information, when the system evaluates arrival status requirements, the desired outcome is that the system determines if cargo needs arrival status based on disposition codes indicating arrival events (pod, aad) or arrival-related processing.
💻 Technical Criteria
Given A cargo with disposition codes and location information
When The system evaluates arrival status requirements
Then The system determines if cargo needs arrival status based on disposition codes indicating arrival events (POD, AAD) or arrival-related processing
R-GCX016E-cbl-02937 Validate Arrival Location
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Arrival Location' is invoked, and assuming that a cargo requiring arrival status with location information, when the system validates arrival location, the desired outcome is that the system confirms the arrival location is valid and matches expected destination or border crossing points.
💻 Technical Criteria
Given A cargo requiring arrival status with location information
When The system validates arrival location
Then The system confirms the arrival location is valid and matches expected destination or border crossing points
R-GCX016E-cbl-02938 Set Arrival Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Set Arrival Status Flags' is invoked, and assuming that a cargo with validated arrival location, when the system sets arrival status flags, the desired outcome is that the system sets arrival status flags, updates arrival dates, and establishes arrival processing indicators.
💻 Technical Criteria
Given A cargo with validated arrival location
When The system sets arrival status flags
Then The system sets arrival status flags, updates arrival dates, and establishes arrival processing indicators
R-GCX016E-cbl-02939 Export Status Required?
Decision Rules
📊 Business Logic Narrative
When the process 'Export Status Required?' is invoked, and assuming that a cargo with disposition codes and processing history, when the system evaluates export status requirements, the desired outcome is that the system determines if cargo needs export status based on disposition codes or processing flags indicating export operations.
💻 Technical Criteria
Given A cargo with disposition codes and processing history
When The system evaluates export status requirements
Then The system determines if cargo needs export status based on disposition codes or processing flags indicating export operations
R-GCX016E-cbl-02940 Validate Export Location
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Export Location' is invoked, and assuming that a cargo requiring export status with location information, when the system validates export location, the desired outcome is that the system confirms the export location is valid and appropriate for export processing.
💻 Technical Criteria
Given A cargo requiring export status with location information
When The system validates export location
Then The system confirms the export location is valid and appropriate for export processing
R-GCX016E-cbl-02941 Set Export Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Set Export Status Flags' is invoked, and assuming that a cargo with validated export location, when the system sets export status flags, the desired outcome is that the system sets export status flags, clears destination index, and establishes export processing indicators.
💻 Technical Criteria
Given A cargo with validated export location
When The system sets export status flags
Then The system sets export status flags, clears destination index, and establishes export processing indicators
R-GCX016E-cbl-02942 Determine Final Cargo Status
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Final Cargo Status' is invoked, and assuming that a cargo with analyzed hold conditions, release conditions, and processing flags, when the system determines final cargo status, the desired outcome is that the system applies status hierarchy: manual release → released, fda hold → holdfda, ptt conditions → ptt/ptt-ex, hold combinations → various hold statuses, release with quantity → relsd/holdpcs, export/arrival → respective status, default → ack/proceed.
💻 Technical Criteria
Given A cargo with analyzed hold conditions, release conditions, and processing flags
When The system determines final cargo status
Then The system applies status hierarchy: Manual Release → Released, FDA Hold → HOLDFDA, PTT conditions → PTT/PTT-EX, Hold combinations → various hold statuses, Release with quantity → RELSD/HOLDPCS, Export/Arrival → respective status, Default → ACK/PROCEED
R-GCX016E-cbl-02943 Status Changed?
Validation Rules
📊 Business Logic Narrative
When the process 'Status Changed?' is invoked, and assuming that a cargo with newly determined status and previous status information, when the system checks for status changes, the desired outcome is that the system compares the new status with the previous status to determine if a change has occurred.
💻 Technical Criteria
Given A cargo with newly determined status and previous status information
When The system checks for status changes
Then The system compares the new status with the previous status to determine if a change has occurred
R-GCX016E-cbl-02944 Preserve Previous Status for Audit
Policy Rules
📊 Business Logic Narrative
When the process 'Preserve Previous Status for Audit' is invoked, and assuming that a cargo with changed status, when the system preserves previous status for audit, the desired outcome is that the system saves the previous status information for audit trail and compliance tracking.
💻 Technical Criteria
Given A cargo with changed status
When The system preserves previous status for audit
Then The system saves the previous status information for audit trail and compliance tracking
R-GCX016E-cbl-02945 Update Cargo Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status Flags' is invoked, and assuming that a cargo with determined final status, when the system updates cargo status flags, the desired outcome is that the system updates all cargo status flags, processing indicators, and related status information in the cargo record.
💻 Technical Criteria
Given A cargo with determined final status
When The system updates cargo status flags
Then The system updates all cargo status flags, processing indicators, and related status information in the cargo record
R-GCX016E-cbl-02946 Calculate Cargo Age
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Cargo Age' is invoked, and assuming that a cargo with arrival date or initial processing date, when the system calculates cargo age, the desired outcome is that the system computes the number of days since cargo arrival or initial processing for aging analysis and reporting.
💻 Technical Criteria
Given A cargo with arrival date or initial processing date
When The system calculates cargo age
Then The system computes the number of days since cargo arrival or initial processing for aging analysis and reporting
R-GCX016E-cbl-02947 Generate Status Notifications
Action Rules
📊 Business Logic Narrative
When the process 'Generate Status Notifications' is invoked, and assuming that a cargo with updated status information, when the system generates status notifications, the desired outcome is that the system creates merlin messages, email notifications, or system alerts based on the status change and notification requirements.
💻 Technical Criteria
Given A cargo with updated status information
When The system generates status notifications
Then The system creates Merlin messages, email notifications, or system alerts based on the status change and notification requirements
R-GCX016E-cbl-02948 All Holds Released?
Decision Rules
📊 Business Logic Narrative
When the process 'All Holds Released?' is invoked, and assuming that a cargo with analyzed hold conditions, when the system checks if all holds are released, the desired outcome is that the system determines if no active hold conditions remain (no border holds, destination holds, fda holds, or piece count holds).
💻 Technical Criteria
Given A cargo with analyzed hold conditions
When The system checks if all holds are released
Then The system determines if no active hold conditions remain (no border holds, destination holds, FDA holds, or piece count holds)
R-GCX016E-cbl-02949 Partial Release?
Decision Rules
📊 Business Logic Narrative
When the process 'Partial Release?' is invoked, and assuming that a cargo with calculated release quantities and remaining holds, when the system checks for partial release status, the desired outcome is that the system determines if some cargo quantity has been released while other quantities remain held.
💻 Technical Criteria
Given A cargo with calculated release quantities and remaining holds
When The system checks for partial release status
Then The system determines if some cargo quantity has been released while other quantities remain held
R-GCX016E-cbl-02950 Full Hold Status?
Decision Rules
📊 Business Logic Narrative
When the process 'Full Hold Status?' is invoked, and assuming that a cargo with active hold conditions and no partial releases, when the system checks for full hold status, the desired outcome is that the system determines if the entire cargo quantity is held with no released portions.
💻 Technical Criteria
Given A cargo with active hold conditions and no partial releases
When The system checks for full hold status
Then The system determines if the entire cargo quantity is held with no released portions
R-GCX016E-cbl-02951 Set RELEASED Status
Action Rules
📊 Business Logic Narrative
When the process 'Set RELEASED Status' is invoked, and assuming that a cargo with all holds released and no remaining hold conditions, when the system sets released status, the desired outcome is that the system assigns released status and updates all related release flags and processing indicators.
💻 Technical Criteria
Given A cargo with all holds released and no remaining hold conditions
When The system sets released status
Then The system assigns RELEASED status and updates all related release flags and processing indicators
R-GCX016E-cbl-02952 Set PARTIAL RELEASE Status
Action Rules
📊 Business Logic Narrative
When the process 'Set PARTIAL RELEASE Status' is invoked, and assuming that a cargo with partial quantity released and remaining holds, when the system sets partial release status, the desired outcome is that the system assigns holdpcs or similar partial release status indicating mixed release/hold condition.
💻 Technical Criteria
Given A cargo with partial quantity released and remaining holds
When The system sets partial release status
Then The system assigns HOLDPCS or similar partial release status indicating mixed release/hold condition
R-GCX016E-cbl-02953 Set HOLD Status
Action Rules
📊 Business Logic Narrative
When the process 'Set HOLD Status' is invoked, and assuming that a cargo with active hold conditions and no releases, when the system sets hold status, the desired outcome is that the system assigns appropriate hold status (hold, hold-b for border, hold-d for destination, holdfda for fda) based on the type and location of holds.
💻 Technical Criteria
Given A cargo with active hold conditions and no releases
When The system sets hold status
Then The system assigns appropriate hold status (HOLD, HOLD-B for border, HOLD-D for destination, HOLDFDA for FDA) based on the type and location of holds
R-GCX016E-cbl-03188 Entry Number Present?
Validation Rules
📊 Business Logic Narrative
When the process 'Entry Number Present?' is invoked, and assuming that a cargo record is being processed for in-bond entry, when the system checks for entry number presence, the desired outcome is that if entry number is present, proceed to validation; if not present, complete processing without further validation.
💻 Technical Criteria
Given A cargo record is being processed for in-bond entry
When The system checks for entry number presence
Then If entry number is present, proceed to validation; if not present, complete processing without further validation
R-GCX016E-cbl-03189 Validate Against Broker Entry Numbers
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Against Broker Entry Numbers' is invoked, and assuming that an entry number is present in the cargo record, when the system validates the entry number against broker entry numbers, the desired outcome is that the entry number must match an existing broker entry number to be considered valid.
💻 Technical Criteria
Given An entry number is present in the cargo record
When The system validates the entry number against broker entry numbers
Then The entry number must match an existing broker entry number to be considered valid
R-GCX016E-cbl-03358 Entry Type Code Present?
Validation Rules
📊 Business Logic Narrative
When the process 'Entry Type Code Present?' is invoked, and assuming that an x4 segment is being processed for cargo disposition, when the system checks for the presence of an entry type code in the segment, the desired outcome is that if entry type code is present, continue with conversion process, otherwise skip entry type processing and continue with other segment processing.
💻 Technical Criteria
Given An X4 segment is being processed for cargo disposition
When The system checks for the presence of an entry type code in the segment
Then If entry type code is present, continue with conversion process, otherwise skip entry type processing and continue with other segment processing
R-GCX016E-cbl-03364 Map to Canadian Border Location
Action Rules
📊 Business Logic Narrative
When the process 'Map to Canadian Border Location' is invoked, and assuming that a border crossing entry type code requires location mapping, when the system maps the code to canadian border crossing locations, the desired outcome is that the appropriate canadian border location identifier is assigned to the cargo record.
💻 Technical Criteria
Given A border crossing entry type code requires location mapping
When The system maps the code to Canadian border crossing locations
Then The appropriate Canadian border location identifier is assigned to the cargo record
R-GCX016E-cbl-03365 Set Master In-Bond Flag for Codes 61,62,63,69
Policy Rules
📊 Business Logic Narrative
When the process 'Set Master In-Bond Flag for Codes 61,62,63,69' is invoked, and assuming that an entry type code has been processed (either border crossing or standard), when the entry type code is 61, 62, 63, or 69, the desired outcome is that the master in-bond flag is set to indicate this cargo requires in-bond processing.
💻 Technical Criteria
Given An entry type code has been processed (either border crossing or standard)
When The entry type code is 61, 62, 63, or 69
Then The master in-bond flag is set to indicate this cargo requires in-bond processing
R-GCX016E-cbl-03366 Code Validation Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Code Validation Successful?' is invoked, and assuming that entry type code processing including border crossing logic and in-bond flag setting has been completed, when the system evaluates whether all validation steps were successful, the desired outcome is that if validation is successful, update the cargo record with the internal code, otherwise generate an error message.
💻 Technical Criteria
Given Entry type code processing including border crossing logic and in-bond flag setting has been completed
When The system evaluates whether all validation steps were successful
Then If validation is successful, update the cargo record with the internal code, otherwise generate an error message
R-GCX016E-cbl-03367 Update Cargo Record with Internal Code
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Record with Internal Code' is invoked, and assuming that entry type code validation has been successful, when the system updates the cargo record with the converted entry type information, the desired outcome is that the cargo record is updated with the internal entry type code, border crossing information, and in-bond flags as applicable.
💻 Technical Criteria
Given Entry type code validation has been successful
When The system updates the cargo record with the converted entry type information
Then The cargo record is updated with the internal entry type code, border crossing information, and in-bond flags as applicable
R-GCX016E-cbl-03368 Log Code Conversion Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Code Conversion Action' is invoked, and assuming that the cargo record has been successfully updated with the converted entry type code, when the system logs the code conversion action, the desired outcome is that an audit log entry is created documenting the entry type code conversion from edi format to internal system format.
💻 Technical Criteria
Given The cargo record has been successfully updated with the converted entry type code
When The system logs the code conversion action
Then An audit log entry is created documenting the entry type code conversion from EDI format to internal system format
R-GCX016E-cbl-03476 Cargo Movement Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Movement Type?' is invoked, and assuming that a cargo record with origin and destination location information, when the system evaluates the cargo movement pattern for border crossing processing, the desired outcome is that the system classifies the movement as us to canada transit, canada to us transit, or us-canada-us transit based on origin and destination locations.
💻 Technical Criteria
Given A cargo record with origin and destination location information
When The system evaluates the cargo movement pattern for border crossing processing
Then The system classifies the movement as US to Canada Transit, Canada to US Transit, or US-Canada-US Transit based on origin and destination locations
R-GCX016E-cbl-03477 Map US Port Code to Canadian Border Location
Definitional Rules
📊 Business Logic Narrative
When the process 'Map US Port Code to Canadian Border Location' is invoked, and assuming that a us port code from cargo location information and a us port to canadian border mapping table, when the system needs to identify the corresponding canadian border location, the desired outcome is that the system retrieves the mapped canadian border location code from the mapping table.
💻 Technical Criteria
Given A US port code from cargo location information and a US Port to Canadian Border Mapping table
When The system needs to identify the corresponding Canadian border location
Then The system retrieves the mapped Canadian border location code from the mapping table
R-GCX016E-cbl-03479 Set Canadian Border Port Name
Action Rules
📊 Business Logic Narrative
When the process 'Set Canadian Border Port Name' is invoked, and assuming that a validated canadian border location code from the canadian border location table, when the canadian location is confirmed to exist, the desired outcome is that the system sets the canadian border port name for the cargo record.
💻 Technical Criteria
Given A validated Canadian border location code from the Canadian Border Location Table
When The Canadian location is confirmed to exist
Then The system sets the Canadian border port name for the cargo record
R-GCX016E-cbl-03480 Search Canadian Manifest Database
Action Rules
📊 Business Logic Narrative
When the process 'Search Canadian Manifest Database' is invoked, and assuming that cargo equipment information and access to gccc-cargo-root canadian cargo database, when the system needs to find corresponding canadian manifest records, the desired outcome is that the system searches the canadian manifest database using equipment identification criteria.
💻 Technical Criteria
Given Cargo equipment information and access to GCCC-CARGO-ROOT Canadian Cargo database
When The system needs to find corresponding Canadian manifest records
Then The system searches the Canadian manifest database using equipment identification criteria
R-GCX016E-cbl-03481 Equipment ID Matches?
Validation Rules
📊 Business Logic Narrative
When the process 'Equipment ID Matches?' is invoked, and assuming that a us cargo record with equipment id and a canadian manifest record with equipment id, when the system compares equipment ids for cross-border record linking, the desired outcome is that the system confirms whether the equipment ids match exactly between the us and canadian records.
💻 Technical Criteria
Given A US cargo record with equipment ID and a Canadian manifest record with equipment ID
When The system compares equipment IDs for cross-border record linking
Then The system confirms whether the equipment IDs match exactly between the US and Canadian records
R-GCX016E-cbl-03482 Link US and Canadian Records
Action Rules
📊 Business Logic Narrative
When the process 'Link US and Canadian Records' is invoked, and assuming that matching us and canadian cargo records with validated equipment ids, when equipment ids match between the records, the desired outcome is that the system establishes a cross-border linkage between the us and canadian cargo records.
💻 Technical Criteria
Given Matching US and Canadian cargo records with validated equipment IDs
When Equipment IDs match between the records
Then The system establishes a cross-border linkage between the US and Canadian cargo records
R-GCX016E-cbl-03483 Set Cross-Border Transit Flags
Action Rules
📊 Business Logic Narrative
When the process 'Set Cross-Border Transit Flags' is invoked, and assuming that successfully linked us and canadian cargo records, when cross-border record linkage is established, the desired outcome is that the system sets cross-border transit flags on both us and canadian cargo records.
💻 Technical Criteria
Given Successfully linked US and Canadian cargo records
When Cross-border record linkage is established
Then The system sets cross-border transit flags on both US and Canadian cargo records
R-GCX016E-cbl-03484 Apply Special Transit Rules
Policy Rules
📊 Business Logic Narrative
When the process 'Apply Special Transit Rules' is invoked, and assuming that a cargo record identified as us-canada-us transit movement, when the cargo movement type is us-canada-us transit, the desired outcome is that the system applies special transit processing rules specific to round-trip cross-border movements.
💻 Technical Criteria
Given A cargo record identified as US-Canada-US transit movement
When The cargo movement type is US-Canada-US Transit
Then The system applies special transit processing rules specific to round-trip cross-border movements
R-GCX016E-cbl-03485 Create Cross-Border Audit Trail
Process Rules
📊 Business Logic Narrative
When the process 'Create Cross-Border Audit Trail' is invoked, and assuming that a canadian manifest record found for cross-border cargo movement, when canadian manifest is successfully located, the desired outcome is that the system creates audit trail records documenting the cross-border cargo movement.
💻 Technical Criteria
Given A Canadian manifest record found for cross-border cargo movement
When Canadian manifest is successfully located
Then The system creates audit trail records documenting the cross-border cargo movement
R-GCX016E-cbl-03486 Generate Border Crossing Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Border Crossing Error', assuming that a cargo record requiring border crossing processing and canadian border location table, when the canadian location is not found in the reference table, the desired outcome is that the system generates a border crossing error indicating the location validation failure.
💻 Technical Criteria
EXCLUDING A cargo record requiring border crossing processing and Canadian Border Location Table
When The Canadian location is not found in the reference table
Then The system generates a border crossing error indicating the location validation failure
R-GCX016E-cbl-03487 Continue Standard Processing
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Continue Standard Processing', assuming that a cargo record undergoing border crossing logic where canadian manifest search fails or equipment id validation fails, when no canadian manifest is found or equipment ids do not match, the desired outcome is that the system continues with standard cargo processing without cross-border linkage.
💻 Technical Criteria
EXCLUDING A cargo record undergoing border crossing logic where Canadian manifest search fails or equipment ID validation fails
When No Canadian manifest is found OR equipment IDs do not match
Then The system continues with standard cargo processing without cross-border linkage
R-GCX016E-cbl-03488 Update Cargo Status for Border Transit
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status for Border Transit' is invoked, and assuming that a cargo record that has completed border crossing logic processing, when border crossing logic is complete (whether successful linkage, error, or standard processing), the desired outcome is that the system updates the cargo status to reflect the border transit processing results.
💻 Technical Criteria
Given A cargo record that has completed border crossing logic processing
When Border crossing logic is complete (whether successful linkage, error, or standard processing)
Then The system updates the cargo status to reflect the border transit processing results
R-GCX016E-cbl-00336 Clear BOL Type Code
Action Rules
📊 Business Logic Narrative
When the process 'Clear BOL Type Code' is invoked, and assuming that a valid disposition code 95 is being processed, when the system processes the bond cancellation, the desired outcome is that the bol type code is cleared from the cargo record.
💻 Technical Criteria
Given A valid disposition code 95 is being processed
When The system processes the bond cancellation
Then The BOL type code is cleared from the cargo record
R-GCX016E-cbl-00337 Clear M12 Bond Data
Action Rules
📊 Business Logic Narrative
When the process 'Clear M12 Bond Data' is invoked, and assuming that a disposition code 95 is being processed for bond cancellation, when the system clears bond information, the desired outcome is that all m12 bond segment data is removed from the cargo record.
💻 Technical Criteria
Given A disposition code 95 is being processed for bond cancellation
When The system clears bond information
Then All M12 bond segment data is removed from the cargo record
R-GCX016E-cbl-00338 Clear Bond Number Index
Action Rules
📊 Business Logic Narrative
When the process 'Clear Bond Number Index' is invoked, and assuming that a disposition code 95 is being processed, when the system processes bond cancellation, the desired outcome is that the bond number index is cleared from the cargo record.
💻 Technical Criteria
Given A disposition code 95 is being processed
When The system processes bond cancellation
Then The bond number index is cleared from the cargo record
R-GCX016E-cbl-00339 Clear Broker QP Information
Action Rules
📊 Business Logic Narrative
When the process 'Clear Broker QP Information' is invoked, and assuming that a disposition code 95 is being processed for bond cancellation, when the system clears bond-related information, the desired outcome is that all broker qp (qualified person) information is removed from the cargo record.
💻 Technical Criteria
Given A disposition code 95 is being processed for bond cancellation
When The system clears bond-related information
Then All broker QP (Qualified Person) information is removed from the cargo record
R-GCX016E-cbl-00340 Clear Bond Owner Information
Action Rules
📊 Business Logic Narrative
When the process 'Clear Bond Owner Information' is invoked, and assuming that a disposition code 95 is being processed, when the system processes bond cancellation, the desired outcome is that bond owner information is cleared from the cargo record.
💻 Technical Criteria
Given A disposition code 95 is being processed
When The system processes bond cancellation
Then Bond owner information is cleared from the cargo record
R-GCX016E-cbl-00342 Update Cargo Status Array
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status Array' is invoked, and assuming that a disposition code 95 has been processed and bond information cleared, when the system updates cargo status, the desired outcome is that the cargo status array is updated to reflect the bond cancellation with appropriate status codes.
💻 Technical Criteria
Given A disposition code 95 has been processed and bond information cleared
When The system updates cargo status
Then The cargo status array is updated to reflect the bond cancellation with appropriate status codes
R-GCX016E-cbl-00343 Log Bond Cancellation Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Bond Cancellation Action' is invoked, and assuming that a disposition code 95 has been processed and bond information cleared, when the system completes bond cancellation processing, the desired outcome is that the bond cancellation action is logged with relevant cargo and bond details.
💻 Technical Criteria
Given A disposition code 95 has been processed and bond information cleared
When The system completes bond cancellation processing
Then The bond cancellation action is logged with relevant cargo and bond details
R-GCX016E-cbl-00345 Update Database with Cleared Bond Info
Action Rules
📊 Business Logic Narrative
When the process 'Update Database with Cleared Bond Info' is invoked, and assuming that all bond information has been cleared for disposition code 95, when the system updates the database, the desired outcome is that the cargo database is updated with all cleared bond fields and updated status information.
💻 Technical Criteria
Given All bond information has been cleared for disposition code 95
When The system updates the database
Then The cargo database is updated with all cleared bond fields and updated status information
R-GCX016E-cbl-00347 132: In-Bond Entry Number Validation
Validation Rules
📊 Business Logic Narrative
When the process '132: In-Bond Entry Number Validation' is invoked, and assuming that a cargo record contains an in-bond entry number, when the system processes the cargo for in-bond validation, the desired outcome is that the entry number is validated for proper format and business rules compliance.
💻 Technical Criteria
Given A cargo record contains an in-bond entry number
When The system processes the cargo for in-bond validation
Then The entry number is validated for proper format and business rules compliance
R-GCX016E-cbl-00358 Update Cargo with Broker Information
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo with Broker Information' is invoked, and assuming that in-bond flag setting has been completed for the entry type, when the system updates the cargo record, the desired outcome is that broker information and in-bond details are stored in the cargo record.
💻 Technical Criteria
Given In-bond flag setting has been completed for the entry type
When The system updates the cargo record
Then Broker information and in-bond details are stored in the cargo record
R-GCX016E-cbl-00359 Log In-Bond Processing Action
Process Rules
📊 Business Logic Narrative
When the process 'Log In-Bond Processing Action' is invoked, and assuming that cargo has been updated with broker information, when the system logs the processing action, the desired outcome is that in-bond processing details are recorded in the system log.
💻 Technical Criteria
Given Cargo has been updated with broker information
When The system logs the processing action
Then In-bond processing details are recorded in the system log
R-GCX016E-cbl-00361 Continue Cargo Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue Cargo Processing' is invoked, and assuming that in-bond processing has completed (either successfully or with error handling), when the system continues with cargo processing, the desired outcome is that standard cargo processing workflow resumes.
💻 Technical Criteria
Given In-bond processing has completed (either successfully or with error handling)
When The system continues with cargo processing
Then Standard cargo processing workflow resumes
R-GCX016E-cbl-00367 Border Crossing Scenario?
Decision Rules
📊 Business Logic Narrative
When the process 'Border Crossing Scenario?' is invoked, and assuming that entry type processing is in progress, when the system evaluates if this is a border crossing scenario, the desired outcome is that if border crossing is detected, apply border crossing logic; otherwise update cargo record directly.
💻 Technical Criteria
Given Entry type processing is in progress
When The system evaluates if this is a border crossing scenario
Then If border crossing is detected, apply border crossing logic; otherwise update cargo record directly
R-GCX016E-cbl-00368 Apply Border Crossing Logic
Process Rules
📊 Business Logic Narrative
When the process 'Apply Border Crossing Logic' is invoked, and assuming that a border crossing scenario has been identified, when the system applies border crossing logic, the desired outcome is that execute special border crossing processing rules and update cargo accordingly.
💻 Technical Criteria
Given A border crossing scenario has been identified
When The system applies border crossing logic
Then Execute special border crossing processing rules and update cargo accordingly
R-GCX016E-cbl-00369 Update Cargo Record with Entry Type
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Record with Entry Type' is invoked, and assuming that entry type has been successfully processed and validated, when the system updates the cargo record, the desired outcome is that store the internal entry type code and any associated flags in the cargo record.
💻 Technical Criteria
Given Entry type has been successfully processed and validated
When The system updates the cargo record
Then Store the internal entry type code and any associated flags in the cargo record
R-GCX016E-cbl-00372 Extract US Port Code from Cargo Data
Process Rules
📊 Business Logic Narrative
When the process 'Extract US Port Code from Cargo Data' is invoked, and assuming that a cross-border cargo record is received for processing, when the system processes the cargo data, the desired outcome is that the us port code is extracted from the cargo record for border location mapping.
💻 Technical Criteria
Given A cross-border cargo record is received for processing
When The system processes the cargo data
Then The US port code is extracted from the cargo record for border location mapping
R-GCX016E-cbl-00373 Access Canadian Border Location Mapping Table
Action Rules
📊 Business Logic Narrative
When the process 'Access Canadian Border Location Mapping Table' is invoked, and assuming that a us port code has been extracted from cargo data, when the system needs to determine the corresponding canadian border location, the desired outcome is that the canadian border location mapping table is accessed for lookup.
💻 Technical Criteria
Given A US port code has been extracted from cargo data
When The system needs to determine the corresponding Canadian border location
Then The Canadian border location mapping table is accessed for lookup
R-GCX016E-cbl-00374 US Port Code Found in Mapping?
Validation Rules
📊 Business Logic Narrative
When the process 'US Port Code Found in Mapping?' is invoked, and assuming that a us port code has been extracted from cargo data and the mapping table is accessed, when the system searches for the us port code in the mapping table, the desired outcome is that the system determines if a corresponding canadian border location mapping exists.
💻 Technical Criteria
Given A US port code has been extracted from cargo data and the mapping table is accessed
When The system searches for the US port code in the mapping table
Then The system determines if a corresponding Canadian border location mapping exists
R-GCX016E-cbl-00376 Update Cargo Record with Canadian Border Location
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Record with Canadian Border Location' is invoked, and assuming that a canadian border location name has been successfully retrieved from the mapping table, when the system processes the mapping result, the desired outcome is that the cargo record is updated with the canadian border location information.
💻 Technical Criteria
Given A Canadian border location name has been successfully retrieved from the mapping table
When The system processes the mapping result
Then The cargo record is updated with the Canadian border location information
R-GCX016E-cbl-00377 Log Border Location Mapping
Process Rules
📊 Business Logic Narrative
When the process 'Log Border Location Mapping' is invoked, and assuming that a cargo record has been updated with canadian border location information, when the border location mapping is completed, the desired outcome is that an audit log entry is created documenting the border location mapping operation.
💻 Technical Criteria
Given A cargo record has been updated with Canadian border location information
When The border location mapping is completed
Then An audit log entry is created documenting the border location mapping operation
R-GCX016E-cbl-00378 Generate Error for Unmapped Port Code
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error for Unmapped Port Code', assuming that a us port code has been extracted from cargo data, when the us port code is not found in the canadian border location mapping table, the desired outcome is that an error is generated indicating the port code cannot be mapped to a canadian border location.
💻 Technical Criteria
EXCLUDING A US port code has been extracted from cargo data
When The US port code is not found in the Canadian border location mapping table
Then An error is generated indicating the port code cannot be mapped to a Canadian border location
R-GCX016E-cbl-00379 Continue Cargo Processing with Border Location
Process Rules
📊 Business Logic Narrative
When the process 'Continue Cargo Processing with Border Location' is invoked, and assuming that border location mapping has been completed successfully or an error has been generated for unmapped port code, when the border location processing step is finished, the desired outcome is that the system continues with the next step in the cargo processing workflow.
💻 Technical Criteria
Given Border location mapping has been completed successfully or an error has been generated for unmapped port code
When The border location processing step is finished
Then The system continues with the next step in the cargo processing workflow
R-GCX016E-cbl-00380 A1 Disposition Code Processing
Decision Rules
📊 Business Logic Narrative
When the process 'A1 Disposition Code Processing' is invoked, and assuming that a cargo has an a1 disposition code for fda processing, when the system processes the a1 disposition code, the desired outcome is that the system retrieves the n9 reference number segment and formats the fda reference number with fda pn prefix.
💻 Technical Criteria
Given A cargo has an A1 disposition code for FDA processing
When The system processes the A1 disposition code
Then The system retrieves the N9 reference number segment and formats the FDA reference number with FDA PN prefix
R-GCX016E-cbl-00381 A3 Disposition Code Processing
Decision Rules
📊 Business Logic Narrative
When the process 'A3 Disposition Code Processing' is invoked, and assuming that a cargo has an a3 disposition code for fda processing, when the system processes the a3 disposition code, the desired outcome is that the system retrieves the n9 reference number segment and formats the fda reference number with fda prefix.
💻 Technical Criteria
Given A cargo has an A3 disposition code for FDA processing
When The system processes the A3 disposition code
Then The system retrieves the N9 reference number segment and formats the FDA reference number with FDA prefix
R-GCX016E-cbl-00382 Retrieve N9 Reference Number Segment
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve N9 Reference Number Segment' is invoked, and assuming that fda disposition code processing is required, when the system needs to process fda reference numbers, the desired outcome is that the system retrieves the n9 reference number segment from the cargo database.
💻 Technical Criteria
Given FDA disposition code processing is required
When The system needs to process FDA reference numbers
Then The system retrieves the N9 reference number segment from the cargo database
R-GCX016E-cbl-00387 Replace N9 Segment in Database
Action Rules
📊 Business Logic Narrative
When the process 'Replace N9 Segment in Database' is invoked, and assuming that n9 reference segment has been updated with fda reference number, when the system persists the changes, the desired outcome is that the system replaces the n9 segment in the cargo database with the updated information.
💻 Technical Criteria
Given N9 reference segment has been updated with FDA reference number
When The system persists the changes
Then The system replaces the N9 segment in the cargo database with the updated information
R-GCX016E-cbl-00389 Search Broker Database for Freight Forwarder Disposition Codes
Decision Rules
📊 Business Logic Narrative
When the process 'Search Broker Database for Freight Forwarder Disposition Codes' is invoked, and assuming that a cih hold has been detected for a cargo, when the system searches the broker name table for freight forwarder disposition codes, the desired outcome is that the system identifies whether freight forwarder disposition codes exist for the cargo.
💻 Technical Criteria
Given A CIH hold has been detected for a cargo
When The system searches the broker name table for freight forwarder disposition codes
Then The system identifies whether freight forwarder disposition codes exist for the cargo
R-GCX016E-cbl-00391 Retrieve Cargo Segment Data from GCSUSS03/GCSUSS07
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Cargo Segment Data from GCSUSS03/GCSUSS07' is invoked, and assuming that a freight forwarder has been found in the broker database, when the system needs cargo segment information, the desired outcome is that the system retrieves cargo segment data from both gcsuss03 and gcsuss07 databases.
💻 Technical Criteria
Given A freight forwarder has been found in the broker database
When The system needs cargo segment information
Then The system retrieves cargo segment data from both GCSUSS03 and GCSUSS07 databases
R-GCX016E-cbl-00392 Extract Freight Forwarder Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Freight Forwarder Information' is invoked, and assuming that cargo segment data has been retrieved from gcsuss03 and gcsuss07, when the system processes the cargo segment data, the desired outcome is that the system extracts freight forwarder identification and contact information.
💻 Technical Criteria
Given Cargo segment data has been retrieved from GCSUSS03 and GCSUSS07
When The system processes the cargo segment data
Then The system extracts freight forwarder identification and contact information
R-GCX016E-cbl-00393 Lookup Freight Forwarder Name from Broker Tables
Action Rules
📊 Business Logic Narrative
When the process 'Lookup Freight Forwarder Name from Broker Tables' is invoked, and assuming that freight forwarder information has been extracted from cargo segment data, when the system searches the broker name tables (gcst2rt), the desired outcome is that the system retrieves the complete freight forwarder name and details.
💻 Technical Criteria
Given Freight forwarder information has been extracted from cargo segment data
When The system searches the broker name tables (GCST2RT)
Then The system retrieves the complete freight forwarder name and details
R-GCX016E-cbl-00397 Include Equipment Details
Process Rules
📊 Business Logic Narrative
When the process 'Include Equipment Details' is invoked, and assuming that email content structure has been built, when the system adds equipment information to the email, the desired outcome is that the email includes equipment type, identification numbers, and related equipment details.
💻 Technical Criteria
Given Email content structure has been built
When The system adds equipment information to the email
Then The email includes equipment type, identification numbers, and related equipment details
R-GCX016E-cbl-00409 Initialize Empty Status Arrays
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Empty Status Arrays' is invoked, and assuming that a cargo record exists in the system, when no s09 status segments are found in the database for the cargo, the desired outcome is that the system initializes empty s09a status arrays with zero occurrence counts and clears all status tracking variables.
💻 Technical Criteria
Given A cargo record exists in the system
When No S09 status segments are found in the database for the cargo
Then The system initializes empty S09A status arrays with zero occurrence counts and clears all status tracking variables
R-GCX016E-cbl-00410 Populate S09A Status Arrays from Database
Process Rules
📊 Business Logic Narrative
When the process 'Populate S09A Status Arrays from Database' is invoked, and assuming that s09 status segments exist in the database for a cargo, when the system retrieves the status segments, the desired outcome is that the system populates the s09a status arrays with disposition codes, quantities, entry numbers, and sequence information from each database segment.
💻 Technical Criteria
Given S09 status segments exist in the database for a cargo
When The system retrieves the status segments
Then The system populates the S09A status arrays with disposition codes, quantities, entry numbers, and sequence information from each database segment
R-GCX016E-cbl-00412 Duplicate Code Check
Validation Rules
📊 Business Logic Narrative
When the process 'Duplicate Code Check' is invoked, and assuming that a new disposition code is being processed for a cargo, when the system searches existing status arrays, the desired outcome is that if a disposition code with identical code, entry number, and quantity already exists, the system flags it as a duplicate; otherwise, it is marked as a new code.
💻 Technical Criteria
Given A new disposition code is being processed for a cargo
When The system searches existing status arrays
Then If a disposition code with identical code, entry number, and quantity already exists, the system flags it as a duplicate; otherwise, it is marked as a new code
R-GCX016E-cbl-00416 Reorganize Array Sequences
Process Rules
📊 Business Logic Narrative
When the process 'Reorganize Array Sequences' is invoked, and assuming that status array entries have been added, updated, or removed, when finalizing status array changes, the desired outcome is that the system reorganizes the arrays by reassigning sequential numbers starting from 1, compacting the arrays to eliminate empty slots, and updating occurrence counts.
💻 Technical Criteria
Given Status array entries have been added, updated, or removed
When Finalizing status array changes
Then The system reorganizes the arrays by reassigning sequential numbers starting from 1, compacting the arrays to eliminate empty slots, and updating occurrence counts
R-GCX016E-cbl-00417 Calculate Status Array Changes
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Status Array Changes' is invoked, and assuming that status arrays have been modified with new or updated disposition codes, when calculating the impact of changes, the desired outcome is that the system determines how the changes affect release quantities, hold status, and overall cargo processing status based on the disposition code types and quantities.
💻 Technical Criteria
Given Status arrays have been modified with new or updated disposition codes
When Calculating the impact of changes
Then The system determines how the changes affect release quantities, hold status, and overall cargo processing status based on the disposition code types and quantities
R-GCX016E-cbl-00419 Replace Status Segments in Database
Action Rules
📊 Business Logic Narrative
When the process 'Replace Status Segments in Database' is invoked, and assuming that status segments have been converted to database format, when updating the cargo record in the database, the desired outcome is that the system replaces the existing s09 status segments with the updated segments and commits the changes to maintain data integrity.
💻 Technical Criteria
Given Status segments have been converted to database format
When Updating the cargo record in the database
Then The system replaces the existing S09 status segments with the updated segments and commits the changes to maintain data integrity
R-GCX016E-cbl-00420 Update Car ID Information
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Update Car ID Information', assuming that a cargo is not a cprs shipment and n7 equipment data is available, when processing car id updates, the desired outcome is that the system updates the cargo record with car id information from the n7 segment, including equipment initial and number, while preserving existing data for cprs shipments.
💻 Technical Criteria
EXCLUDING A cargo is not a CPRS shipment and N7 equipment data is available
When Processing car ID updates
Then The system updates the cargo record with car ID information from the N7 segment, including equipment initial and number, while preserving existing data for CPRS shipments
R-GCX016E-cbl-00421 Track Status Change History
Process Rules
📊 Business Logic Narrative
When the process 'Track Status Change History' is invoked, and assuming that status arrays have been modified for a cargo, when completing status array processing, the desired outcome is that the system creates history records documenting the status changes, including timestamps, disposition codes added or removed, and the resulting cargo status.
💻 Technical Criteria
Given Status arrays have been modified for a cargo
When Completing status array processing
Then The system creates history records documenting the status changes, including timestamps, disposition codes added or removed, and the resulting cargo status
R-GCX016E-cbl-00425 Include Disposition Codes in Message
Process Rules
📊 Business Logic Narrative
When the process 'Include Disposition Codes in Message' is invoked, and assuming that a follower manifest message is being prepared and disposition codes exist for the cargo, when the message content is assembled, the desired outcome is that all relevant disposition codes are included in the follower manifest message.
💻 Technical Criteria
Given A follower manifest message is being prepared AND disposition codes exist for the cargo
When The message content is assembled
Then All relevant disposition codes are included in the follower manifest message
R-GCX016E-cbl-00430 Update Comprehensive Cargo Tracking
Process Rules
📊 Business Logic Narrative
When the process 'Update Comprehensive Cargo Tracking' is invoked, and assuming that all follower manifests have been processed and linked to their lead manifest, when the multi-manifest processing is completing, the desired outcome is that the comprehensive cargo tracking system is updated with all manifest relationships and cargo status information.
💻 Technical Criteria
Given All follower manifests have been processed and linked to their lead manifest
When The multi-manifest processing is completing
Then The comprehensive cargo tracking system is updated with all manifest relationships and cargo status information
R-GCX016E-cbl-00431 Identify Transit Cargo
Decision Rules
📊 Business Logic Narrative
When the process 'Identify Transit Cargo' is invoked, and assuming that a cargo record is being processed, when the system evaluates cargo routing and destination information, the desired outcome is that the cargo is flagged for transit processing if it meets us-canada-us movement criteria.
💻 Technical Criteria
Given A cargo record is being processed
When The system evaluates cargo routing and destination information
Then The cargo is flagged for transit processing if it meets US-Canada-US movement criteria
R-GCX016E-cbl-00432 Cargo Moving Through Canada?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Moving Through Canada?' is invoked, and assuming that a cargo has been identified for potential transit processing, when the system checks if the cargo routing involves movement through canadian territory, the desired outcome is that the cargo is processed for canadian transit if routing goes through canada, otherwise standard processing continues.
💻 Technical Criteria
Given A cargo has been identified for potential transit processing
When The system checks if the cargo routing involves movement through Canadian territory
Then The cargo is processed for Canadian transit if routing goes through Canada, otherwise standard processing continues
R-GCX016E-cbl-00433 Map US Port to Canadian Border Location
Computation Rules
📊 Business Logic Narrative
When the process 'Map US Port to Canadian Border Location' is invoked, and assuming that a cargo requires canadian transit processing, when the system needs to identify the canadian border location, the desired outcome is that the us port is mapped to the corresponding canadian border crossing location using border location mapping tables.
💻 Technical Criteria
Given A cargo requires Canadian transit processing
When The system needs to identify the Canadian border location
Then The US port is mapped to the corresponding Canadian border crossing location using border location mapping tables
R-GCX016E-cbl-00434 Search Canadian Cargo Database
Action Rules
📊 Business Logic Narrative
When the process 'Search Canadian Cargo Database' is invoked, and assuming that a canadian border location has been identified for the cargo, when the system searches the canadian cargo database using cargo identifiers, the desired outcome is that the system retrieves matching canadian cargo records from gccc-cargo-root database.
💻 Technical Criteria
Given A Canadian border location has been identified for the cargo
When The system searches the Canadian cargo database using cargo identifiers
Then The system retrieves matching Canadian cargo records from GCCC-CARGO-ROOT database
R-GCX016E-cbl-00435 Canadian Manifest Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Canadian Manifest Found?' is invoked, and assuming that the system has searched the canadian cargo database, when the search results are evaluated for matching manifests, the desired outcome is that processing continues with equipment validation if canadian manifest found, otherwise error is generated.
💻 Technical Criteria
Given The system has searched the Canadian cargo database
When The search results are evaluated for matching manifests
Then Processing continues with equipment validation if Canadian manifest found, otherwise error is generated
R-GCX016E-cbl-00436 Validate Equipment ID Match
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Equipment ID Match' is invoked, and assuming that a canadian manifest has been found for the cargo, when the system compares equipment ids between us and canadian records, the desired outcome is that the equipment ids must match exactly for the records to be linked for transit processing.
💻 Technical Criteria
Given A Canadian manifest has been found for the cargo
When The system compares equipment IDs between US and Canadian records
Then The equipment IDs must match exactly for the records to be linked for transit processing
R-GCX016E-cbl-00437 Equipment ID Matches?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment ID Matches?' is invoked, and assuming that equipment id validation has been performed, when the system evaluates the match results, the desired outcome is that cross-border tracking link is created if equipment ids match, otherwise error is generated for no canadian match.
💻 Technical Criteria
Given Equipment ID validation has been performed
When The system evaluates the match results
Then Cross-border tracking link is created if equipment IDs match, otherwise error is generated for no Canadian match
R-GCX016E-cbl-00438 Create Cross-Border Tracking Link
Process Rules
📊 Business Logic Narrative
When the process 'Create Cross-Border Tracking Link' is invoked, and assuming that equipment ids match between us and canadian cargo records, when the system creates cross-border tracking relationships, the desired outcome is that a tracking link is established connecting the us and canadian cargo records for transit monitoring.
💻 Technical Criteria
Given Equipment IDs match between US and Canadian cargo records
When The system creates cross-border tracking relationships
Then A tracking link is established connecting the US and Canadian cargo records for transit monitoring
R-GCX016E-cbl-00439 Update Transit Status
Process Rules
📊 Business Logic Narrative
When the process 'Update Transit Status' is invoked, and assuming that a cross-border tracking link has been created, when the system updates cargo status information, the desired outcome is that the cargo status is updated to reflect transit processing status and cross-border movement tracking.
💻 Technical Criteria
Given A cross-border tracking link has been created
When The system updates cargo status information
Then The cargo status is updated to reflect transit processing status and cross-border movement tracking
R-GCX016E-cbl-00440 Exclude Deleted Canadian Records
Validation Rules
📊 Business Logic Narrative
When the process 'Exclude Deleted Canadian Records' is invoked, and assuming that canadian cargo records are being evaluated for transit processing, when the system checks the status of canadian records, the desired outcome is that records marked as deleted are excluded from transit processing consideration.
💻 Technical Criteria
Given Canadian cargo records are being evaluated for transit processing
When The system checks the status of Canadian records
Then Records marked as deleted are excluded from transit processing consideration
R-GCX016E-cbl-00441 Exclude New Bond Created Records
Validation Rules
📊 Business Logic Narrative
When the process 'Exclude New Bond Created Records' is invoked, and assuming that canadian cargo records are being evaluated for transit processing, when the system checks for new bond created status, the desired outcome is that records with new bond created status are excluded from transit processing consideration.
💻 Technical Criteria
Given Canadian cargo records are being evaluated for transit processing
When The system checks for new bond created status
Then Records with new bond created status are excluded from transit processing consideration
R-GCX016E-cbl-00443 Update US Destination Information
Process Rules
📊 Business Logic Narrative
When the process 'Update US Destination Information' is invoked, and assuming that transit routing has been processed, when the system updates destination information, the desired outcome is that the final us destination information is updated to reflect the cargo's ultimate destination after canadian transit.
💻 Technical Criteria
Given Transit routing has been processed
When The system updates destination information
Then The final US destination information is updated to reflect the cargo's ultimate destination after Canadian transit
R-GCX016E-cbl-00444 Generate Transit Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Transit Notification' is invoked, and assuming that us destination information has been updated for transit cargo, when the system generates processing notifications, the desired outcome is that transit processing notifications are generated and sent to appropriate parties for cross-border movement tracking.
💻 Technical Criteria
Given US destination information has been updated for transit cargo
When The system generates processing notifications
Then Transit processing notifications are generated and sent to appropriate parties for cross-border movement tracking
R-GCX016E-cbl-00446 Generate Error - No Canadian Match
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error - No Canadian Match', assuming that no canadian manifest is found or equipment ids do not match, when the system cannot establish cross-border tracking, the desired outcome is that an error is generated indicating no canadian match found and standard processing continues.
💻 Technical Criteria
EXCLUDING No Canadian manifest is found or equipment IDs do not match
When The system cannot establish cross-border tracking
Then An error is generated indicating no Canadian match found and standard processing continues
R-GCX016E-cbl-00447 Continue Standard Processing
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Continue Standard Processing', assuming that cargo does not require canadian transit processing or transit processing has failed, when the system determines standard processing should continue, the desired outcome is that standard cargo processing procedures are followed without transit-specific handling.
💻 Technical Criteria
EXCLUDING Cargo does not require Canadian transit processing or transit processing has failed
When The system determines standard processing should continue
Then Standard cargo processing procedures are followed without transit-specific handling
R-GCX016E-cbl-00450 Set Bond Number as Search Key
Process Rules
📊 Business Logic Narrative
When the process 'Set Bond Number as Search Key' is invoked, and assuming that a valid bond number has been extracted and validated, when the system prepares for cargo database lookup, the desired outcome is that the bond number is set as the search key for cargo record retrieval.
💻 Technical Criteria
Given A valid bond number has been extracted and validated
When The system prepares for cargo database lookup
Then The bond number is set as the search key for cargo record retrieval
R-GCX016E-cbl-00451 Call GCCUSIO2 Database Access
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCUSIO2 Database Access' is invoked, and assuming that a bond number search key has been configured, when the system needs to retrieve cargo records from the database, the desired outcome is that the gccusio2 database access module is called with the bond number search key.
💻 Technical Criteria
Given A bond number search key has been configured
When The system needs to retrieve cargo records from the database
Then The GCCUSIO2 database access module is called with the bond number search key
R-GCX016E-cbl-00452 Search GCSUSRT Cargo Root Segments
Process Rules
📊 Business Logic Narrative
When the process 'Search GCSUSRT Cargo Root Segments' is invoked, and assuming that database access has been initiated with a bond number search key, when the system searches the gcsusrt cargo root segments table, the desired outcome is that all cargo records with matching bond numbers are identified for retrieval.
💻 Technical Criteria
Given Database access has been initiated with a bond number search key
When The system searches the GCSUSRT cargo root segments table
Then All cargo records with matching bond numbers are identified for retrieval
R-GCX016E-cbl-00453 First Cargo Record Found?
Decision Rules
📊 Business Logic Narrative
When the process 'First Cargo Record Found?' is invoked, and assuming that a search has been performed on cargo root segments using bond number, when the system evaluates the search results, the desired outcome is that if at least one cargo record is found, processing continues; if no records found, bond not found error is generated.
💻 Technical Criteria
Given A search has been performed on cargo root segments using bond number
When The system evaluates the search results
Then If at least one cargo record is found, processing continues; if no records found, bond not found error is generated
R-GCX016E-cbl-00454 Retrieve First Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve First Cargo Record' is invoked, and assuming that at least one cargo record exists with the specified bond number, when the system retrieves cargo records, the desired outcome is that the first matching cargo record is retrieved and made available for processing.
💻 Technical Criteria
Given At least one cargo record exists with the specified bond number
When The system retrieves cargo records
Then The first matching cargo record is retrieved and made available for processing
R-GCX016E-cbl-00455 Set Cargo Found Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Cargo Found Flag' is invoked, and assuming that the first cargo record has been successfully retrieved, when the system updates processing status, the desired outcome is that the cargo found flag is set to indicate successful cargo location.
💻 Technical Criteria
Given The first cargo record has been successfully retrieved
When The system updates processing status
Then The cargo found flag is set to indicate successful cargo location
R-GCX016E-cbl-00456 Check for Additional Records
Process Rules
📊 Business Logic Narrative
When the process 'Check for Additional Records' is invoked, and assuming that the first cargo record has been retrieved and cargo found flag is set, when the system checks for additional records with the same bond number, the desired outcome is that the system determines if more cargo records exist with the same bond number.
💻 Technical Criteria
Given The first cargo record has been retrieved and cargo found flag is set
When The system checks for additional records with the same bond number
Then The system determines if more cargo records exist with the same bond number
R-GCX016E-cbl-00458 Retrieve Next Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Next Cargo Record' is invoked, and assuming that additional cargo records exist with the same bond number, when the system retrieves the next cargo record, the desired outcome is that the next matching cargo record is retrieved and prepared for processing.
💻 Technical Criteria
Given Additional cargo records exist with the same bond number
When The system retrieves the next cargo record
Then The next matching cargo record is retrieved and prepared for processing
R-GCX016E-cbl-00459 Add to Cargo Processing List
Process Rules
📊 Business Logic Narrative
When the process 'Add to Cargo Processing List' is invoked, and assuming that a cargo record has been retrieved (first or subsequent), when the system manages the cargo processing list, the desired outcome is that the cargo record is added to the processing list for subsequent operations.
💻 Technical Criteria
Given A cargo record has been retrieved (first or subsequent)
When The system manages the cargo processing list
Then The cargo record is added to the processing list for subsequent operations
R-GCX016E-cbl-00460 Set Bond Index for Processing
Process Rules
📊 Business Logic Narrative
When the process 'Set Bond Index for Processing' is invoked, and assuming that all cargo records with the bond number have been retrieved and added to processing list, when the system prepares for cargo processing operations, the desired outcome is that the bond index is configured for processing all associated cargo records.
💻 Technical Criteria
Given All cargo records with the bond number have been retrieved and added to processing list
When The system prepares for cargo processing operations
Then The bond index is configured for processing all associated cargo records
R-GCX016E-cbl-00461 Return Cargo Records for Processing
Process Rules
📊 Business Logic Narrative
When the process 'Return Cargo Records for Processing' is invoked, and assuming that bond index has been configured and all cargo records are in the processing list, when the cargo lookup operation completes successfully, the desired outcome is that all cargo records associated with the bond number are returned for processing.
💻 Technical Criteria
Given Bond index has been configured and all cargo records are in the processing list
When The cargo lookup operation completes successfully
Then All cargo records associated with the bond number are returned for processing
R-GCX016E-cbl-00462 Generate Bond Not Found Error
Validation Rules
📊 Business Logic Narrative
When the process 'Generate Bond Not Found Error' is invoked, and assuming that a bond number search has been performed and no cargo records were found, when the system processes the empty search result, the desired outcome is that a bond not found error is generated for the specified bond number.
💻 Technical Criteria
Given A bond number search has been performed and no cargo records were found
When The system processes the empty search result
Then A bond not found error is generated for the specified bond number
R-GCX016E-cbl-00465 Format Car ID using Standard Rules
Definitional Rules
📊 Business Logic Narrative
When the process 'Format Car ID using Standard Rules' is invoked, and assuming that a car equipment initial and number are provided from n7 segment, when the system needs to create a car id key for cargo lookup, the desired outcome is that the car id is formatted by concatenating equipment initial and number with proper spacing and validation.
💻 Technical Criteria
Given A car equipment initial and number are provided from N7 segment
When The system needs to create a car ID key for cargo lookup
Then The car ID is formatted by concatenating equipment initial and number with proper spacing and validation
R-GCX016E-cbl-00466 Search Cargo Database by Car ID
Action Rules
📊 Business Logic Narrative
When the process 'Search Cargo Database by Car ID' is invoked, and assuming that a formatted car id key exists, when the system searches for cargo records in the database, the desired outcome is that the system queries both us cargo root segments and car id index tables to find matching records.
💻 Technical Criteria
Given A formatted car ID key exists
When The system searches for cargo records in the database
Then The system queries both US cargo root segments and car ID index tables to find matching records
R-GCX016E-cbl-00467 Cargo Record Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Record Found?' is invoked, and assuming that a database search has been performed for a car id, when the system evaluates the search results, the desired outcome is that if a cargo record is found, retrieve the existing record; otherwise proceed to cprs traffic check.
💻 Technical Criteria
Given A database search has been performed for a car ID
When The system evaluates the search results
Then If a cargo record is found, retrieve the existing record; otherwise proceed to CPRS traffic check
R-GCX016E-cbl-00468 Retrieve Existing Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Existing Cargo Record' is invoked, and assuming that a cargo record exists in the database for the car id, when the system needs to process the cargo, the desired outcome is that the existing cargo record is retrieved and made available for further processing.
💻 Technical Criteria
Given A cargo record exists in the database for the car ID
When The system needs to process the cargo
Then The existing cargo record is retrieved and made available for further processing
R-GCX016E-cbl-00469 Is CPRS Traffic?
Decision Rules
📊 Business Logic Narrative
When the process 'Is CPRS Traffic?' is invoked, and assuming that no cargo record was found in the initial database search, when the system evaluates the traffic type, the desired outcome is that if the cargo is identified as cprs traffic, apply cprs special processing; otherwise generate error message for missing cargo.
💻 Technical Criteria
Given No cargo record was found in the initial database search
When The system evaluates the traffic type
Then If the cargo is identified as CPRS traffic, apply CPRS special processing; otherwise generate error message for missing cargo
R-GCX016E-cbl-00474 Record Found After CPRS Processing?
Decision Rules
📊 Business Logic Narrative
When the process 'Record Found After CPRS Processing?' is invoked, and assuming that cprs special processing and secondary search have been completed, when the system evaluates the search results, the desired outcome is that if a record is found, retrieve the existing cargo record; otherwise create a new cprs cargo record.
💻 Technical Criteria
Given CPRS special processing and secondary search have been completed
When The system evaluates the search results
Then If a record is found, retrieve the existing cargo record; otherwise create a new CPRS cargo record
R-GCX016E-cbl-00475 Create New CPRS Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Create New CPRS Cargo Record' is invoked, and assuming that no cargo record exists after cprs processing and secondary search, when a new cprs cargo record needs to be created, the desired outcome is that the system initiates creation of a new cargo record with cprs-specific attributes.
💻 Technical Criteria
Given No cargo record exists after CPRS processing and secondary search
When A new CPRS cargo record needs to be created
Then The system initiates creation of a new cargo record with CPRS-specific attributes
R-GCX016E-cbl-00476 Initialize New Record with Car ID
Process Rules
📊 Business Logic Narrative
When the process 'Initialize New Record with Car ID' is invoked, and assuming that a new cprs cargo record is being created, when the record initialization process begins, the desired outcome is that the new record is populated with the car id and basic identification information.
💻 Technical Criteria
Given A new CPRS cargo record is being created
When The record initialization process begins
Then The new record is populated with the car ID and basic identification information
R-GCX016E-cbl-00477 Set CPRS-Specific Flags
Definitional Rules
📊 Business Logic Narrative
When the process 'Set CPRS-Specific Flags' is invoked, and assuming that a new cprs cargo record is being initialized, when cprs-specific attributes need to be set, the desired outcome is that the system applies cprs-specific flags, processing indicators, and business rule markers.
💻 Technical Criteria
Given A new CPRS cargo record is being initialized
When CPRS-specific attributes need to be set
Then The system applies CPRS-specific flags, processing indicators, and business rule markers
R-GCX016E-cbl-00478 Insert New Record into Database
Action Rules
📊 Business Logic Narrative
When the process 'Insert New Record into Database' is invoked, and assuming that a new cprs cargo record has been fully initialized, when the record is ready for database storage, the desired outcome is that the system inserts the new record into the us cargo root segments database.
💻 Technical Criteria
Given A new CPRS cargo record has been fully initialized
When The record is ready for database storage
Then The system inserts the new record into the US cargo root segments database
R-GCX016E-cbl-00479 Log CPRS Cargo Creation
Process Rules
📊 Business Logic Narrative
When the process 'Log CPRS Cargo Creation' is invoked, and assuming that a new cprs cargo record has been successfully inserted into the database, when audit logging is required, the desired outcome is that the system creates log entries documenting the cprs cargo creation event.
💻 Technical Criteria
Given A new CPRS cargo record has been successfully inserted into the database
When Audit logging is required
Then The system creates log entries documenting the CPRS cargo creation event
R-GCX016E-cbl-00480 Return Cargo Record for Processing
Process Rules
📊 Business Logic Narrative
When the process 'Return Cargo Record for Processing' is invoked, and assuming that a cargo record has been found or created successfully, when the lookup process is complete, the desired outcome is that the system returns the cargo record to the calling process for further business operations.
💻 Technical Criteria
Given A cargo record has been found or created successfully
When The lookup process is complete
Then The system returns the cargo record to the calling process for further business operations
R-GCX016E-cbl-00481 Generate Error Message for Missing Cargo
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error Message for Missing Cargo', assuming that no cargo record exists and the traffic is not cprs type, when the cargo lookup process fails, the desired outcome is that the system generates an error message indicating the cargo could not be located for the given car id.
💻 Technical Criteria
EXCLUDING No cargo record exists and the traffic is not CPRS type
When The cargo lookup process fails
Then The system generates an error message indicating the cargo could not be located for the given car ID
R-GCX016E-cbl-00482 Format Car ID using Standard Rules
Definitional Rules
📊 Business Logic Narrative
When the process 'Format Car ID using Standard Rules' is invoked, and assuming that equipment initial and equipment number are provided from n7 segment, when system needs to format car id for cargo lookup, the desired outcome is that system concatenates equipment initial and equipment number to create standardized car id format.
💻 Technical Criteria
Given Equipment initial and equipment number are provided from N7 segment
When System needs to format car ID for cargo lookup
Then System concatenates equipment initial and equipment number to create standardized car ID format
R-GCX016E-cbl-00487 Store Cargo Information
Process Rules
📊 Business Logic Narrative
When the process 'Store Cargo Information' is invoked, and assuming that first cargo record is successfully retrieved, when system processes the cargo record data, the desired outcome is that system stores cargo information in working storage for further processing.
💻 Technical Criteria
Given First cargo record is successfully retrieved
When System processes the cargo record data
Then System stores cargo information in working storage for further processing
R-GCX016E-cbl-00489 More Records Found?
Validation Rules
📊 Business Logic Narrative
When the process 'More Records Found?' is invoked, and assuming that search for additional cargo records is completed, when system evaluates search results for more records, the desired outcome is that system determines if additional records exist and continues retrieval or proceeds to next processing step.
💻 Technical Criteria
Given Search for additional cargo records is completed
When System evaluates search results for more records
Then System determines if additional records exist and continues retrieval or proceeds to next processing step
R-GCX016E-cbl-00491 Add to Cargo Collection
Process Rules
📊 Business Logic Narrative
When the process 'Add to Cargo Collection' is invoked, and assuming that additional cargo record is successfully retrieved, when system processes the additional cargo record, the desired outcome is that system adds cargo record to the collection and continues search for more records.
💻 Technical Criteria
Given Additional cargo record is successfully retrieved
When System processes the additional cargo record
Then System adds cargo record to the collection and continues search for more records
R-GCX016E-cbl-00493 Apply CPRS Handling Rules
Policy Rules
📊 Business Logic Narrative
When the process 'Apply CPRS Handling Rules' is invoked, and assuming that cargo is identified as cprs traffic, when system applies cprs handling rules, the desired outcome is that system clears car id information and applies cprs-specific processing logic.
💻 Technical Criteria
Given Cargo is identified as CPRS traffic
When System applies CPRS handling rules
Then System clears car ID information and applies CPRS-specific processing logic
R-GCX016E-cbl-00494 Validate Car ID Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Car ID Format' is invoked, and assuming that car id is formatted and cprs processing is completed if applicable, when system validates car id format, the desired outcome is that system ensures car id meets format requirements and is ready for processing.
💻 Technical Criteria
Given Car ID is formatted and CPRS processing is completed if applicable
When System validates car ID format
Then System ensures car ID meets format requirements and is ready for processing
R-GCX016E-cbl-00495 Return All Matching Cargo Records
Process Rules
📊 Business Logic Narrative
When the process 'Return All Matching Cargo Records' is invoked, and assuming that all cargo records are retrieved, validated, and processed, when system completes cargo lookup operation, the desired outcome is that system returns complete collection of matching cargo records for further processing.
💻 Technical Criteria
Given All cargo records are retrieved, validated, and processed
When System completes cargo lookup operation
Then System returns complete collection of matching cargo records for further processing
R-GCX016E-cbl-00497 Log Search Results
Process Rules
📊 Business Logic Narrative
When the process 'Log Search Results' is invoked, and assuming that cargo lookup operation is completed with or without results, when system logs search results, the desired outcome is that system records search outcome including number of records found or not found status.
💻 Technical Criteria
Given Cargo lookup operation is completed with or without results
When System logs search results
Then System records search outcome including number of records found or not found status
R-GCX016E-cbl-00498 Disposition Code Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Disposition Code Type?' is invoked, and assuming that a disposition code is received for cargo processing, when the system evaluates the disposition code type, the desired outcome is that the system must categorize it as hold, release, arrival, export, seizure, status information, or cancellation action type.
💻 Technical Criteria
Given A disposition code is received for cargo processing
When The system evaluates the disposition code type
Then The system must categorize it as Hold, Release, Arrival, Export, Seizure, Status Information, or Cancellation action type
R-GCX016E-cbl-00506 Prepare Log Message
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Log Message' is invoked, and assuming that a disposition code action has been categorized and logged, when the system prepares the log message structure, the desired outcome is that the system must create a standardized message format ready for timestamp, equipment, disposition, and user information.
💻 Technical Criteria
Given A disposition code action has been categorized and logged
When The system prepares the log message structure
Then The system must create a standardized message format ready for timestamp, equipment, disposition, and user information
R-GCX016E-cbl-00507 Add Timestamp Information
Process Rules
📊 Business Logic Narrative
When the process 'Add Timestamp Information' is invoked, and assuming that a log message structure has been prepared for cargo disposition action, when the system adds timestamp information to the log message, the desired outcome is that the system must include the current processing timestamp in the log message.
💻 Technical Criteria
Given A log message structure has been prepared for cargo disposition action
When The system adds timestamp information to the log message
Then The system must include the current processing timestamp in the log message
R-GCX016E-cbl-00509 Add Disposition Code Details
Process Rules
📊 Business Logic Narrative
When the process 'Add Disposition Code Details' is invoked, and assuming that a log message has equipment details added, when the system adds disposition code details to the log message, the desired outcome is that the system must include the disposition code and corresponding action description in the log message.
💻 Technical Criteria
Given A log message has equipment details added
When The system adds disposition code details to the log message
Then The system must include the disposition code and corresponding action description in the log message
R-GCX016E-cbl-00512 Write to Audit Trail
Process Rules
📊 Business Logic Narrative
When the process 'Write to Audit Trail' is invoked, and assuming that gct1051e transaction has been spawned with the log message, when the system writes to the audit trail, the desired outcome is that the system must permanently store the cargo disposition log message in the audit trail database.
💻 Technical Criteria
Given GCT1051E transaction has been spawned with the log message
When The system writes to the audit trail
Then The system must permanently store the cargo disposition log message in the audit trail database
R-GCX016E-cbl-00514 Continue Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue Processing' is invoked, and assuming that the cargo disposition logging has been validated as successful, when the system continues processing, the desired outcome is that the system must proceed with the next step in the cargo processing workflow.
💻 Technical Criteria
Given The cargo disposition logging has been validated as successful
When The system continues processing
Then The system must proceed with the next step in the cargo processing workflow
R-GCX016E-cbl-00515 Handle Logging Error
Process Rules
📊 Business Logic Narrative
When the process 'Handle Logging Error' is invoked, and assuming that the cargo disposition logging has been validated as unsuccessful, when the system handles the logging error, the desired outcome is that the system must implement appropriate error handling procedures and may generate error notifications.
💻 Technical Criteria
Given The cargo disposition logging has been validated as unsuccessful
When The system handles the logging error
Then The system must implement appropriate error handling procedures and may generate error notifications
R-GCX016E-cbl-00516 End Logging Process
Process Rules
📊 Business Logic Narrative
When the process 'End Logging Process' is invoked, and assuming that the cargo disposition logging process has either completed successfully or error handling has been performed, when the system ends the logging process, the desired outcome is that the system must properly terminate the logging process and clean up any resources used.
💻 Technical Criteria
Given The cargo disposition logging process has either completed successfully or error handling has been performed
When The system ends the logging process
Then The system must properly terminate the logging process and clean up any resources used
R-GCX016E-cbl-00517 Message Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Message Type?' is invoked, and assuming that a k1 segment is received for processing, when the system evaluates the message context to determine processing type, the desired outcome is that the k1 segment is classified as either train message or cargo message for appropriate processing workflow.
💻 Technical Criteria
Given A K1 segment is received for processing
When The system evaluates the message context to determine processing type
Then The K1 segment is classified as either train message or cargo message for appropriate processing workflow
R-GCX016E-cbl-00521 Store K1 Message for Cargo
Process Rules
📊 Business Logic Narrative
When the process 'Store K1 Message for Cargo' is invoked, and assuming that a valid k1 message is classified as cargo-related, when the system processes the validated k1 content, the desired outcome is that the k1 message is stored in cargo message repository for inclusion in cargo notifications.
💻 Technical Criteria
Given A valid K1 message is classified as cargo-related
When The system processes the validated K1 content
Then The K1 message is stored in cargo message repository for inclusion in cargo notifications
R-GCX016E-cbl-00522 Log K1 Message Action
Process Rules
📊 Business Logic Narrative
When the process 'Log K1 Message Action' is invoked, and assuming that a k1 message has been stored for either train or cargo processing, when the system completes k1 message storage, the desired outcome is that the k1 message processing action is logged with appropriate details for audit purposes.
💻 Technical Criteria
Given A K1 message has been stored for either train or cargo processing
When The system completes K1 message storage
Then The K1 message processing action is logged with appropriate details for audit purposes
R-GCX016E-cbl-00528 Format K1 Comments
Process Rules
📊 Business Logic Narrative
When the process 'Format K1 Comments' is invoked, and assuming that k1 messages are included in cargo and train notifications, when the system formats the notification content, the desired outcome is that k1 comments are formatted with up to 4 lines of k1 segment comments as available and properly structured for recipient systems.
💻 Technical Criteria
Given K1 messages are included in cargo and train notifications
When The system formats the notification content
Then K1 comments are formatted with up to 4 lines of K1 segment comments as available and properly structured for recipient systems
R-GCX016E-cbl-00529 Integrate with Status Updates
Process Rules
📊 Business Logic Narrative
When the process 'Integrate with Status Updates' is invoked, and assuming that k1 comments have been formatted for notifications, when the system processes status updates for cargo or train operations, the desired outcome is that the formatted k1 comments are integrated with status updates to provide complete information context.
💻 Technical Criteria
Given K1 comments have been formatted for notifications
When The system processes status updates for cargo or train operations
Then The formatted K1 comments are integrated with status updates to provide complete information context
R-GCX016E-cbl-00530 Cargo Found in System?
Validation Rules
📊 Business Logic Narrative
When the process 'Cargo Found in System?' is invoked, and assuming that a cprs cargo lookup request is initiated, when the system searches for the cargo in the database, the desired outcome is that the system determines if the cargo exists and routes to appropriate processing path.
💻 Technical Criteria
Given A CPRS cargo lookup request is initiated
When The system searches for the cargo in the database
Then The system determines if the cargo exists and routes to appropriate processing path
R-GCX016E-cbl-00531 Check CPRS Traffic Flag
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Check CPRS Traffic Flag', assuming that cargo is not found in the system, when the system checks the cprs traffic designation flag, the desired outcome is that the system identifies whether this is cprs traffic requiring special error handling.
💻 Technical Criteria
EXCLUDING Cargo is not found in the system
When The system checks the CPRS traffic designation flag
Then The system identifies whether this is CPRS traffic requiring special error handling
R-GCX016E-cbl-00532 Is CPRS Traffic?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Is CPRS Traffic?', assuming that the cprs traffic flag has been checked for cargo not found in system, when the system evaluates if the cargo is designated as cprs traffic, the desired outcome is that if cprs traffic, generate specific error message; otherwise continue with normal processing.
💻 Technical Criteria
EXCLUDING The CPRS traffic flag has been checked for cargo not found in system
When The system evaluates if the cargo is designated as CPRS traffic
Then If CPRS traffic, generate specific error message; otherwise continue with normal processing
R-GCX016E-cbl-00533 Generate CPRS Cargo Not Found Error
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate CPRS Cargo Not Found Error', assuming that cargo is not found in system and is designated as cprs traffic, when the system initiates error message generation, the desired outcome is that a cprs-specific cargo not found error message is created.
💻 Technical Criteria
EXCLUDING Cargo is not found in system and is designated as CPRS traffic
When The system initiates error message generation
Then A CPRS-specific cargo not found error message is created
R-GCX016E-cbl-00534 Format Error Message with Car ID
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Format Error Message with Car ID', assuming that a cprs cargo not found error is being generated, when the system formats the error message, the desired outcome is that the car id information is included in the error message format.
💻 Technical Criteria
EXCLUDING A CPRS cargo not found error is being generated
When The system formats the error message
Then The car ID information is included in the error message format
R-GCX016E-cbl-00535 Include Equipment Details in Error
Process Rules
📊 Business Logic Narrative
When the process 'Include Equipment Details in Error' is invoked, and assuming that the error message is being formatted with car id, when equipment details are available for the cargo, the desired outcome is that equipment information is included in the error message.
💻 Technical Criteria
Given The error message is being formatted with car ID
When Equipment details are available for the cargo
Then Equipment information is included in the error message
R-GCX016E-cbl-00537 Set Error Message Type
Process Rules
📊 Business Logic Narrative
When the process 'Set Error Message Type' is invoked, and assuming that the error message content is complete with all required information, when the system sets the message type, the desired outcome is that the error message is classified with the appropriate type for cprs cargo not found scenarios.
💻 Technical Criteria
Given The error message content is complete with all required information
When The system sets the message type
Then The error message is classified with the appropriate type for CPRS cargo not found scenarios
R-GCX016E-cbl-00540 Continue Processing Other Cargo
Process Rules
📊 Business Logic Narrative
When the process 'Continue Processing Other Cargo' is invoked, and assuming that cprs error has been processed and logged, when the system continues with remaining processing, the desired outcome is that normal cargo processing workflow resumes for other cargo items.
💻 Technical Criteria
Given CPRS error has been processed and logged
When The system continues with remaining processing
Then Normal cargo processing workflow resumes for other cargo items
R-GCX016E-cbl-00541 Normal Cargo Processing
Process Rules
📊 Business Logic Narrative
When the process 'Normal Cargo Processing' is invoked, and assuming that cargo is found in the system, when the system initiates cargo processing, the desired outcome is that cargo follows the normal processing workflow without error handling.
💻 Technical Criteria
Given Cargo is found in the system
When The system initiates cargo processing
Then Cargo follows the normal processing workflow without error handling
R-GCX016E-cbl-00568 Format Car ID using Standard Rules
Definitional Rules
📊 Business Logic Narrative
When the process 'Format Car ID using Standard Rules' is invoked, and assuming that a raw car identification needs to be processed for cargo search, when the system applies standard car id formatting rules, the desired outcome is that the car id is formatted according to business standards for consistent cargo matching.
💻 Technical Criteria
Given A raw car identification needs to be processed for cargo search
When The system applies standard car ID formatting rules
Then The car ID is formatted according to business standards for consistent cargo matching
R-GCX016E-cbl-00572 Cargo Found with Car ID Only?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Found with Car ID Only?' is invoked, and assuming that a secondary search has been performed using only car id, when the system evaluates the search results, the desired outcome is that if cargo records are found, proceed to handle scac scenarios; if no records found, handle cargo not found scenario.
💻 Technical Criteria
Given A secondary search has been performed using only car ID
When The system evaluates the search results
Then If cargo records are found, proceed to handle SCAC scenarios; if no records found, handle cargo not found scenario
R-GCX016E-cbl-00575 Return Found Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Return Found Cargo Record' is invoked, and assuming that cargo records have been successfully found and processed through either primary or secondary search, when the system completes cargo record processing, the desired outcome is that the found cargo record is returned to the requesting process for further business operations.
💻 Technical Criteria
Given Cargo records have been successfully found and processed through either primary or secondary search
When The system completes cargo record processing
Then The found cargo record is returned to the requesting process for further business operations
R-GCX016E-cbl-00576 Handle Cargo Not Found Scenario
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Handle Cargo Not Found Scenario', assuming that both primary and secondary cargo searches have failed to locate any matching cargo records, when the system processes the cargo not found scenario, the desired outcome is that the system initiates appropriate error handling procedures for missing cargo situations.
💻 Technical Criteria
EXCLUDING Both primary and secondary cargo searches have failed to locate any matching cargo records
When The system processes the cargo not found scenario
Then The system initiates appropriate error handling procedures for missing cargo situations
R-GCX016E-cbl-00577 Generate CPRS Error Message if Applicable
Action Rules
📊 Business Logic Narrative
When the process 'Generate CPRS Error Message if Applicable' is invoked, and assuming that cargo search has failed and the cargo may be related to cprs operations, when the system determines cprs error message generation is applicable, the desired outcome is that a cprs-specific error message is generated to inform users of the cargo search failure.
💻 Technical Criteria
Given Cargo search has failed and the cargo may be related to CPRS operations
When The system determines CPRS error message generation is applicable
Then A CPRS-specific error message is generated to inform users of the cargo search failure
R-GCX016E-cbl-00578 Cargo Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Cargo Record Found?' is invoked, and assuming that a cargo processing request is initiated, when the system checks for the existence of the cargo record, the desired outcome is that if cargo record exists, proceed to fetch status segments; if not, initialize empty status arrays.
💻 Technical Criteria
Given A cargo processing request is initiated
When The system checks for the existence of the cargo record
Then If cargo record exists, proceed to fetch status segments; if not, initialize empty status arrays
R-GCX016E-cbl-00579 Fetch S09 Status Segments from Database
Action Rules
📊 Business Logic Narrative
When the process 'Fetch S09 Status Segments from Database' is invoked, and assuming that a valid cargo record exists, when the system fetches s09 status segments from the database, the desired outcome is that all status segments associated with the cargo are retrieved for processing.
💻 Technical Criteria
Given A valid cargo record exists
When The system fetches S09 status segments from the database
Then All status segments associated with the cargo are retrieved for processing
R-GCX016E-cbl-00580 Status Segments Exist?
Decision Rules
📊 Business Logic Narrative
When the process 'Status Segments Exist?' is invoked, and assuming that status segment fetch operation has completed, when the system checks if any status segments were found, the desired outcome is that if segments exist, populate status arrays from database; if not, initialize empty arrays.
💻 Technical Criteria
Given Status segment fetch operation has completed
When The system checks if any status segments were found
Then If segments exist, populate status arrays from database; if not, initialize empty arrays
R-GCX016E-cbl-00581 Initialize Empty Status Arrays
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Initialize Empty Status Arrays', assuming that no status segments exist for the cargo or cargo record not found, when the system initializes status processing, the desired outcome is that empty status arrays are created to prepare for new status information.
💻 Technical Criteria
EXCLUDING No status segments exist for the cargo OR cargo record not found
When The system initializes status processing
Then Empty status arrays are created to prepare for new status information
R-GCX016E-cbl-00582 Populate Status Arrays from Database Segments
Process Rules
📊 Business Logic Narrative
When the process 'Populate Status Arrays from Database Segments' is invoked, and assuming that status segments exist in the database for the cargo, when the system populates status arrays, the desired outcome is that all existing status information is loaded into memory arrays for processing.
💻 Technical Criteria
Given Status segments exist in the database for the cargo
When The system populates status arrays
Then All existing status information is loaded into memory arrays for processing
R-GCX016E-cbl-00584 Process Status Array Updates
Process Rules
📊 Business Logic Narrative
When the process 'Process Status Array Updates' is invoked, and assuming that status arrays are initialized (either empty or populated from database), when the system processes status updates from disposition codes or events, the desired outcome is that status arrays are modified according to business rules for holds, releases, and other status changes.
💻 Technical Criteria
Given Status arrays are initialized (either empty or populated from database)
When The system processes status updates from disposition codes or events
Then Status arrays are modified according to business rules for holds, releases, and other status changes
R-GCX016E-cbl-00587 Update Car ID Information for Non-CPRS Cargo
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Update Car ID Information for Non-CPRS Cargo', assuming that status arrays have been converted to database format and cargo is not cprs type, when the system updates car id information, the desired outcome is that car identification data is updated in the cargo record based on n7 segment information.
💻 Technical Criteria
EXCLUDING Status arrays have been converted to database format AND cargo is not CPRS type
When The system updates car ID information
Then Car identification data is updated in the cargo record based on N7 segment information
R-GCX016E-cbl-00588 Replace Status Segments in Database
Action Rules
📊 Business Logic Narrative
When the process 'Replace Status Segments in Database' is invoked, and assuming that status segments have been formatted for database storage and car id has been updated, when the system replaces status segments in the database, the desired outcome is that all modified status information is persisted to the gcsuss09 database.
💻 Technical Criteria
Given Status segments have been formatted for database storage AND car ID has been updated
When The system replaces status segments in the database
Then All modified status information is persisted to the GCSUSS09 database
R-GCX016E-cbl-02954 Retrieve S09 Status Segments from Database
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve S09 Status Segments from Database' is invoked, and assuming that a cargo record exists in the system, when the system needs to process cargo status information, the desired outcome is that the system retrieves all s09 status segments from the gcsuss09 database for the cargo.
💻 Technical Criteria
Given A cargo record exists in the system
When The system needs to process cargo status information
Then The system retrieves all S09 status segments from the GCSUSS09 database for the cargo
R-GCX016E-cbl-02956 Initialize S09A Status Array
Process Rules
📊 Business Logic Narrative
When the process 'Initialize S09A Status Array' is invoked, and assuming that status segments exist in the database for the cargo, when the system begins status array population, the desired outcome is that the system initializes the s09a status array structure to receive the segment data.
💻 Technical Criteria
Given Status segments exist in the database for the cargo
When The system begins status array population
Then The system initializes the S09A status array structure to receive the segment data
R-GCX016E-cbl-02957 Initialize Empty Status Array
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Empty Status Array' is invoked, and assuming that no status segments exist in the database for the cargo, when the system needs to create a status array, the desired outcome is that the system initializes an empty s09a status array structure.
💻 Technical Criteria
Given No status segments exist in the database for the cargo
When The system needs to create a status array
Then The system initializes an empty S09A status array structure
R-GCX016E-cbl-03219 Retrieve S09 Status Segment from Database
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve S09 Status Segment from Database' is invoked, and assuming that a cargo record exists in the system with associated status segments, when the system attempts to retrieve the s09 status segment from the database, the desired outcome is that the segment data is successfully fetched and made available for processing.
💻 Technical Criteria
Given A cargo record exists in the system with associated status segments
When The system attempts to retrieve the S09 status segment from the database
Then The segment data is successfully fetched and made available for processing
R-GCX016E-cbl-03229 Mark Segment as Valid for Processing
Process Rules
📊 Business Logic Narrative
When the process 'Mark Segment as Valid for Processing' is invoked, and assuming that s09 segment has passed all validation checks and maximum sequence has been tracked, when the system finalizes segment validation, the desired outcome is that segment is marked as valid and ready for cargo status processing.
💻 Technical Criteria
Given S09 segment has passed all validation checks and maximum sequence has been tracked
When The system finalizes segment validation
Then Segment is marked as valid and ready for cargo status processing
R-GCX016E-cbl-03232 Attempt Segment Reconstruction
Process Rules
📊 Business Logic Narrative
When the process 'Attempt Segment Reconstruction' is invoked, and assuming that s09 segment is invalid, corrupted, or has format errors, when the system attempts segment reconstruction, the desired outcome is that reconstruction process is executed using available cargo data and default values.
💻 Technical Criteria
Given S09 segment is invalid, corrupted, or has format errors
When The system attempts segment reconstruction
Then Reconstruction process is executed using available cargo data and default values
R-GCX016E-cbl-03239 Validation Complete - Segment Ready
Process Rules
📊 Business Logic Narrative
When the process 'Validation Complete - Segment Ready' is invoked, and assuming that s09 segment has passed all validation checks and is marked as valid, when the system completes validation process, the desired outcome is that segment is confirmed ready for cargo status processing and business logic application.
💻 Technical Criteria
Given S09 segment has passed all validation checks and is marked as valid
When The system completes validation process
Then Segment is confirmed ready for cargo status processing and business logic application
R-GCX016E-cbl-03380 Retrieve S09 Status Segment from Database
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve S09 Status Segment from Database' is invoked, and assuming that a cargo record exists in the system, when the system needs to retrieve s09 status segments from the database, the desired outcome is that the system should fetch the status segment data from gcsuss09 table.
💻 Technical Criteria
Given A cargo record exists in the system
When The system needs to retrieve S09 status segments from the database
Then The system should fetch the status segment data from GCSUSS09 table
R-GCX016E-cbl-03388 More Segments Available?
Decision Rules
📊 Business Logic Narrative
When the process 'More Segments Available?' is invoked, and assuming that status segments are being processed for a cargo record, when the system checks for more segments availability, the desired outcome is that the system should determine if additional s09 segments exist that need to be processed for the current cargo.
💻 Technical Criteria
Given Status segments are being processed for a cargo record
When The system checks for more segments availability
Then The system should determine if additional S09 segments exist that need to be processed for the current cargo
R-GCX016E-cbl-03489 Retrieve S09 Segment from Database
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve S09 Segment from Database' is invoked, and assuming that a cargo record requires s09 segment validation, when the system attempts to retrieve the s09 segment from the gcsuss09 database, the desired outcome is that the s09 segment data is successfully retrieved and made available for validation.
💻 Technical Criteria
Given A cargo record requires S09 segment validation
When The system attempts to retrieve the S09 segment from the GCSUSS09 database
Then The S09 segment data is successfully retrieved and made available for validation
R-GCX016E-cbl-03504 Continue to Status Array Population
Process Rules
📊 Business Logic Narrative
When the process 'Continue to Status Array Population' is invoked, and assuming that s09 segment has been marked as valid after successful validation, when the system continues processing, the desired outcome is that the valid segment data is used to populate status arrays for cargo processing.
💻 Technical Criteria
Given S09 segment has been marked as valid after successful validation
When The system continues processing
Then The valid segment data is used to populate status arrays for cargo processing
R-GCX016E-cbl-02982 Update Car ID Information
Process Rules
📊 Business Logic Narrative
When the process 'Update Car ID Information' is invoked, and assuming that database segment requires car id information, when car id update is performed, the desired outcome is that current car identification data is added to database segment.
💻 Technical Criteria
Given Database segment requires car ID information
When Car ID update is performed
Then Current car identification data is added to database segment
R-GCX016E-cbl-02983 Non-CPRS Cargo?
Decision Rules
📊 Business Logic Narrative
When the process 'Non-CPRS Cargo?' is invoked, and assuming that cargo type needs to be evaluated for car id processing, when cprs status check is performed, the desired outcome is that non-cprs cargos proceed to car id update, cprs cargos skip car id update.
💻 Technical Criteria
Given Cargo type needs to be evaluated for car ID processing
When CPRS status check is performed
Then Non-CPRS cargos proceed to car ID update, CPRS cargos skip car ID update
R-GCX016E-cbl-02984 Update Car ID in Database Segment
Process Rules
📊 Business Logic Narrative
When the process 'Update Car ID in Database Segment' is invoked, and assuming that cargo is confirmed as non-cprs type, when car id database update is executed, the desired outcome is that car identification information is updated in the database segment.
💻 Technical Criteria
Given Cargo is confirmed as non-CPRS type
When Car ID database update is executed
Then Car identification information is updated in the database segment
R-GCX016E-cbl-00595 Continue Processing with Valid Code
Process Rules
📊 Business Logic Narrative
When the process 'Continue Processing with Valid Code' is invoked, and assuming that a disposition code has been validated and flagged as valid, when all processing rules have been satisfied, the desired outcome is that the system continues with normal cargo processing using the validated disposition code.
💻 Technical Criteria
Given A disposition code has been validated and flagged as valid
When All processing rules have been satisfied
Then The system continues with normal cargo processing using the validated disposition code
R-GCX016E-cbl-00596 Skip Processing for Invalid Code
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Skip Processing for Invalid Code', assuming that a disposition code has been flagged as invalid, when the invalid code flag is set, the desired outcome is that the system skips further processing for that cargo to prevent errors.
💻 Technical Criteria
EXCLUDING A disposition code has been flagged as invalid
When The invalid code flag is set
Then The system skips further processing for that cargo to prevent errors
R-GCX016E-cbl-03511 Add Equipment/Cargo Identification
Process Rules
📊 Business Logic Narrative
When the process 'Add Equipment/Cargo Identification' is invoked, and assuming that an error message is being prepared for an unknown disposition code, when the system adds identification information, the desired outcome is that the error message includes equipment identifiers, cargo details, and other relevant identification data.
💻 Technical Criteria
Given An error message is being prepared for an unknown disposition code
When The system adds identification information
Then The error message includes equipment identifiers, cargo details, and other relevant identification data
R-GCX016E-cbl-00597 Status Array Empty?
Validation Rules
📊 Business Logic Narrative
When the process 'Status Array Empty?' is invoked, and assuming that a cargo status array (s09a) needs to be checked for existing disposition codes, when the system accesses the status array to determine if it contains any entries, the desired outcome is that if the status array is empty, set no duplicates found flag and skip duplicate detection process.
💻 Technical Criteria
Given A cargo status array (S09A) needs to be checked for existing disposition codes
When The system accesses the status array to determine if it contains any entries
Then If the status array is empty, set no duplicates found flag and skip duplicate detection process
R-GCX016E-cbl-00604 Remove Hold Codes when Release Code Added
Decision Rules
📊 Business Logic Narrative
When the process 'Remove Hold Codes when Release Code Added' is invoked, and assuming that a cargo has existing hold disposition codes in its status array and a new release disposition code is being processed, when the system processes the release disposition code and identifies conflicting hold codes in the status array, the desired outcome is that the system removes all conflicting hold disposition codes from the status array and maintains the release code as the active status.
💻 Technical Criteria
Given A cargo has existing hold disposition codes in its status array AND a new release disposition code is being processed
When The system processes the release disposition code AND identifies conflicting hold codes in the status array
Then The system removes all conflicting hold disposition codes from the status array AND maintains the release code as the active status
R-GCX016E-cbl-00605 Remove Release Codes when Hold Code Added
Decision Rules
📊 Business Logic Narrative
When the process 'Remove Release Codes when Hold Code Added' is invoked, and assuming that a cargo has existing release disposition codes in its status array and a new hold disposition code is being processed, when the system processes the hold disposition code and identifies conflicting release codes in the status array, the desired outcome is that the system removes all conflicting release disposition codes from the status array and maintains the hold code as the active status.
💻 Technical Criteria
Given A cargo has existing release disposition codes in its status array AND a new hold disposition code is being processed
When The system processes the hold disposition code AND identifies conflicting release codes in the status array
Then The system removes all conflicting release disposition codes from the status array AND maintains the hold code as the active status
R-GCX016E-cbl-00606 Remove Superseded Status Information Codes
Process Rules
📊 Business Logic Narrative
When the process 'Remove Superseded Status Information Codes' is invoked, and assuming that a cargo has existing status information codes in its status array and new status information codes are being processed, when the system identifies that existing status information codes are superseded by the new codes, the desired outcome is that the system removes the outdated status information codes from the status array and retains only the current status information.
💻 Technical Criteria
Given A cargo has existing status information codes in its status array AND new status information codes are being processed
When The system identifies that existing status information codes are superseded by the new codes
Then The system removes the outdated status information codes from the status array AND retains only the current status information
R-GCX016E-cbl-00607 Remove Cancelled Disposition Codes
Process Rules
📊 Business Logic Narrative
When the process 'Remove Cancelled Disposition Codes' is invoked, and assuming that a cargo has disposition codes in its status array and some codes have been marked as cancelled or superseded, when the system processes disposition code updates and identifies cancelled or superseded codes, the desired outcome is that the system removes all cancelled and superseded disposition codes from the status array and maintains only active disposition codes.
💻 Technical Criteria
Given A cargo has disposition codes in its status array AND some codes have been marked as cancelled or superseded
When The system processes disposition code updates AND identifies cancelled or superseded codes
Then The system removes all cancelled and superseded disposition codes from the status array AND maintains only active disposition codes
R-GCX016E-cbl-00609 Reorganize Status Array Structure
Process Rules
📊 Business Logic Narrative
When the process 'Reorganize Status Array Structure' is invoked, and assuming that disposition codes have been removed from the status array and gaps exist in the array structure, when the code removal process is complete, the desired outcome is that the system compacts the status array by moving remaining codes to fill gaps and maintains proper array structure without empty slots.
💻 Technical Criteria
Given Disposition codes have been removed from the status array AND gaps exist in the array structure
When The code removal process is complete
Then The system compacts the status array by moving remaining codes to fill gaps AND maintains proper array structure without empty slots
R-GCX016E-cbl-00610 Log Counterpart Code Removal Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Counterpart Code Removal Action' is invoked, and assuming that counterpart disposition codes are being removed from a cargo status array, when the removal action is executed, the desired outcome is that the system logs the removal action with details of which codes were removed and the reason for removal and the timestamp of the action.
💻 Technical Criteria
Given Counterpart disposition codes are being removed from a cargo status array
When The removal action is executed
Then The system logs the removal action with details of which codes were removed AND the reason for removal AND the timestamp of the action
R-GCX016E-cbl-00615 Remove Counterpart Hold Codes
Process Rules
📊 Business Logic Narrative
When the process 'Remove Counterpart Hold Codes' is invoked, and assuming that a manual release code is being added to cargo status, when the system identifies existing hold codes that conflict with the release, the desired outcome is that all counterpart hold codes are removed from the status array before adding the release code.
💻 Technical Criteria
Given A manual release code is being added to cargo status
When The system identifies existing hold codes that conflict with the release
Then All counterpart hold codes are removed from the status array before adding the release code
R-GCX016E-cbl-00617 Update Release Quantities
Computation Rules
📊 Business Logic Narrative
When the process 'Update Release Quantities' is invoked, and assuming that a manual release code has been added to the status array, when the system processes quantity information from the release request, the desired outcome is that the cargo's released quantity is updated to reflect the manual release amount.
💻 Technical Criteria
Given A manual release code has been added to the status array
When The system processes quantity information from the release request
Then The cargo's released quantity is updated to reflect the manual release amount
R-GCX016E-cbl-00619 Evaluate Final Cargo Status
Decision Rules
📊 Business Logic Narrative
When the process 'Evaluate Final Cargo Status' is invoked, and assuming that manual release has been logged and quantities updated, when the system evaluates all disposition codes in the status array, the desired outcome is that the final cargo status is determined based on the hierarchy of all active disposition codes.
💻 Technical Criteria
Given Manual release has been logged and quantities updated
When The system evaluates all disposition codes in the status array
Then The final cargo status is determined based on the hierarchy of all active disposition codes
R-GCX016E-cbl-00620 Cargo Fully Released?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Fully Released?' is invoked, and assuming that final cargo status has been evaluated, when the system compares released quantities against total cargo quantities, the desired outcome is that cargo is marked as fully released if all quantities are released, otherwise marked as partially released.
💻 Technical Criteria
Given Final cargo status has been evaluated
When The system compares released quantities against total cargo quantities
Then Cargo is marked as fully released if all quantities are released, otherwise marked as partially released
R-GCX016E-cbl-00621 Generate Release Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Release Notification' is invoked, and assuming that cargo has been determined to be fully released, when the system processes the full release status, the desired outcome is that a release notification is generated for appropriate parties including brokers and freight forwarders.
💻 Technical Criteria
Given Cargo has been determined to be fully released
When The system processes the full release status
Then A release notification is generated for appropriate parties including brokers and freight forwarders
R-GCX016E-cbl-00622 Update Cargo Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status Flags' is invoked, and assuming that release notification has been generated or cargo is partially released, when the system updates the cargo record, the desired outcome is that all relevant status flags are updated to reflect the current release state of the cargo.
💻 Technical Criteria
Given Release notification has been generated or cargo is partially released
When The system updates the cargo record
Then All relevant status flags are updated to reflect the current release state of the cargo
R-GCX016E-cbl-00624 Skip Processing
Process Rules
📊 Business Logic Narrative
When the process 'Skip Processing' is invoked, and assuming that a manual release code already exists in the cargo's status array, when the system detects the duplicate during processing, the desired outcome is that processing is skipped for this code and continues with next item without error.
💻 Technical Criteria
Given A manual release code already exists in the cargo's status array
When The system detects the duplicate during processing
Then Processing is skipped for this code and continues with next item without error
R-GCX016E-cbl-00625 Send Merlin Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send Merlin Notification' is invoked, and assuming that cargo status flags have been updated or error/skip condition occurred, when the system completes manual release processing, the desired outcome is that appropriate notifications are sent through merlin system to relevant parties based on the processing outcome.
💻 Technical Criteria
Given Cargo status flags have been updated or error/skip condition occurred
When The system completes manual release processing
Then Appropriate notifications are sent through Merlin system to relevant parties based on the processing outcome
R-GCX016E-cbl-00627 Disposition Code Exists in Status Array?
Decision Rules
📊 Business Logic Narrative
When the process 'Disposition Code Exists in Status Array?' is invoked, and assuming that a validated disposition code removal request and cargo status array, when the system searches for the target disposition code in the status array, the desired outcome is that if the disposition code exists in the array, proceed with removal process, otherwise generate error message for code not found.
💻 Technical Criteria
Given A validated disposition code removal request and cargo status array
When The system searches for the target disposition code in the status array
Then If the disposition code exists in the array, proceed with removal process, otherwise generate error message for code not found
R-GCX016E-cbl-00629 Removal Allowed?
Authorization Rules
📊 Business Logic Narrative
When the process 'Removal Allowed?' is invoked, and assuming that a located disposition code in the status array and current cargo status, when the system evaluates removal authorization rules, the desired outcome is that if the code can be removed without violating business constraints, authorize removal, otherwise deny and generate error.
💻 Technical Criteria
Given A located disposition code in the status array and current cargo status
When The system evaluates removal authorization rules
Then If the code can be removed without violating business constraints, authorize removal, otherwise deny and generate error
R-GCX016E-cbl-00633 Log Removal Action
Policy Rules
📊 Business Logic Narrative
When the process 'Log Removal Action' is invoked, and assuming that a successfully removed disposition code from cargo status array, when the system logs the removal action, the desired outcome is that an audit entry must be created containing cargo identifier, removed disposition code, removal timestamp, and user information.
💻 Technical Criteria
Given A successfully removed disposition code from cargo status array
When The system logs the removal action
Then An audit entry must be created containing cargo identifier, removed disposition code, removal timestamp, and user information
R-GCX016E-cbl-00634 Generate Removal Confirmation
Action Rules
📊 Business Logic Narrative
When the process 'Generate Removal Confirmation' is invoked, and assuming that a successfully completed disposition code removal with updated status array, when the system generates removal confirmation, the desired outcome is that a confirmation message must be created containing cargo details, removed disposition code, and updated status information.
💻 Technical Criteria
Given A successfully completed disposition code removal with updated status array
When The system generates removal confirmation
Then A confirmation message must be created containing cargo details, removed disposition code, and updated status information
R-GCX016E-cbl-00635 Update Cargo Status
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status' is invoked, and assuming that a cargo with updated status array after disposition code removal, when the system updates the cargo record, the desired outcome is that the cargo record must be updated with the new status array and any derived status changes resulting from the removal.
💻 Technical Criteria
Given A cargo with updated status array after disposition code removal
When The system updates the cargo record
Then The cargo record must be updated with the new status array and any derived status changes resulting from the removal
R-GCX016E-cbl-00636 Trigger Status Re-evaluation
Process Rules
📊 Business Logic Narrative
When the process 'Trigger Status Re-evaluation' is invoked, and assuming that a cargo record with updated status array after disposition code removal, when the system triggers status re-evaluation process, the desired outcome is that the cargo's overall status must be recalculated based on remaining disposition codes using standard status determination rules.
💻 Technical Criteria
Given A cargo record with updated status array after disposition code removal
When The system triggers status re-evaluation process
Then The cargo's overall status must be recalculated based on remaining disposition codes using standard status determination rules
R-GCX016E-cbl-00637 Send Status Change Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send Status Change Notification' is invoked, and assuming that a cargo with updated status after disposition code removal and re-evaluation, when the system sends status change notifications, the desired outcome is that notifications must be sent to brokers, freight forwarders, and other stakeholders based on cargo notification rules and new status.
💻 Technical Criteria
Given A cargo with updated status after disposition code removal and re-evaluation
When The system sends status change notifications
Then Notifications must be sent to brokers, freight forwarders, and other stakeholders based on cargo notification rules and new status
R-GCX016E-cbl-00639 Log Removal Failure
Policy Rules
📊 Business Logic Narrative
When the process 'Log Removal Failure' is invoked, and assuming that a failed disposition code removal request with generated error message, when the system logs the removal failure, the desired outcome is that a failure audit entry must be created containing cargo identifier, attempted disposition code, failure reason, and timestamp.
💻 Technical Criteria
Given A failed disposition code removal request with generated error message
When The system logs the removal failure
Then A failure audit entry must be created containing cargo identifier, attempted disposition code, failure reason, and timestamp
R-GCX016E-cbl-00640 Search Existing S09A Status Arrays
Validation Rules
📊 Business Logic Narrative
When the process 'Search Existing S09A Status Arrays' is invoked, and assuming that a status information disposition code is received for processing and the cargo has existing s09a status array segments, when the system searches through all existing status array entries for the same disposition code, the desired outcome is that the system identifies whether the status information code already exists in the status array.
💻 Technical Criteria
Given A status information disposition code is received for processing AND the cargo has existing S09A status array segments
When The system searches through all existing status array entries for the same disposition code
Then The system identifies whether the status information code already exists in the status array
R-GCX016E-cbl-00641 Skip Processing - Code Already Exists
Decision Rules
📊 Business Logic Narrative
When the process 'Skip Processing - Code Already Exists' is invoked, and assuming that a status information disposition code is being processed and the same disposition code already exists in the cargo's status array, when the system detects the duplicate status information code, the desired outcome is that the system skips adding the disposition code and continues to the next disposition code for processing.
💻 Technical Criteria
Given A status information disposition code is being processed AND the same disposition code already exists in the cargo's status array
When The system detects the duplicate status information code
Then The system skips adding the disposition code AND continues to the next disposition code for processing
R-GCX016E-cbl-00642 Validate Available Space in Status Array
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Available Space in Status Array' is invoked, and assuming that a new status information disposition code needs to be added to the cargo's status array and the status array has a maximum capacity limit, when the system checks the current number of entries against the maximum allowed entries, the desired outcome is that the system determines whether there is available space for the new status information code.
💻 Technical Criteria
Given A new status information disposition code needs to be added to the cargo's status array AND the status array has a maximum capacity limit
When The system checks the current number of entries against the maximum allowed entries
Then The system determines whether there is available space for the new status information code
R-GCX016E-cbl-00643 Generate Array Full Warning
Action Rules
📊 Business Logic Narrative
When the process 'Generate Array Full Warning' is invoked, and assuming that a status information disposition code needs to be added and the cargo's status array has reached maximum capacity, when the system attempts to insert the new status information code, the desired outcome is that the system generates an array full warning and continues processing the next disposition code.
💻 Technical Criteria
Given A status information disposition code needs to be added AND the cargo's status array has reached maximum capacity
When The system attempts to insert the new status information code
Then The system generates an array full warning AND continues processing the next disposition code
R-GCX016E-cbl-00646 Set Status Information Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Status Information Flag' is invoked, and assuming that a status information disposition code has been successfully added to the cargo's status array, when the status information code insertion is completed, the desired outcome is that the system sets the status information flag to indicate the presence of status information codes.
💻 Technical Criteria
Given A status information disposition code has been successfully added to the cargo's status array
When The status information code insertion is completed
Then The system sets the status information flag to indicate the presence of status information codes
R-GCX016E-cbl-00647 Log Status Information Code Addition
Process Rules
📊 Business Logic Narrative
When the process 'Log Status Information Code Addition' is invoked, and assuming that a status information disposition code has been successfully added to the cargo's status array and the status information flag has been set, when the status information processing is completed, the desired outcome is that the system logs the status information code addition for audit trail purposes.
💻 Technical Criteria
Given A status information disposition code has been successfully added to the cargo's status array AND the status information flag has been set
When The status information processing is completed
Then The system logs the status information code addition for audit trail purposes
R-GCX016E-cbl-00648 Disposition Code Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Disposition Code Type?' is invoked, and assuming that a disposition code is received for cargo processing, when the system evaluates the disposition code type, the desired outcome is that the code is classified as either a hold code or release code based on the disposition code table definition.
💻 Technical Criteria
Given A disposition code is received for cargo processing
When The system evaluates the disposition code type
Then The code is classified as either a hold code or release code based on the disposition code table definition
R-GCX016E-cbl-00649 Code Already Exists?
Validation Rules
📊 Business Logic Narrative
When the process 'Code Already Exists?' is invoked, and assuming that a hold or release disposition code needs to be added to cargo status array, when the system searches the existing status array for the same disposition code with matching entry number and quantity, the desired outcome is that if an exact match is found, the duplicate processing is skipped, otherwise the code is processed.
💻 Technical Criteria
Given A hold or release disposition code needs to be added to cargo status array
When The system searches the existing status array for the same disposition code with matching entry number and quantity
Then If an exact match is found, the duplicate processing is skipped, otherwise the code is processed
R-GCX016E-cbl-00653 Set Cargo Hold Status
Action Rules
📊 Business Logic Narrative
When the process 'Set Cargo Hold Status' is invoked, and assuming that a hold disposition code has been successfully added to the status array, when the system processes hold code implications, the desired outcome is that the cargo hold status is set with appropriate hold type (border hold, destination hold, fda hold) based on the disposition code.
💻 Technical Criteria
Given A hold disposition code has been successfully added to the status array
When The system processes hold code implications
Then The cargo hold status is set with appropriate hold type (border hold, destination hold, FDA hold) based on the disposition code
R-GCX016E-cbl-00654 Update Hold Flags
Action Rules
📊 Business Logic Narrative
When the process 'Update Hold Flags' is invoked, and assuming that cargo hold status has been set for a disposition code, when the system updates hold-related information, the desired outcome is that hold flags are updated including held at border flag, held at destination flag, held for fda flag, and hold location information.
💻 Technical Criteria
Given Cargo hold status has been set for a disposition code
When The system updates hold-related information
Then Hold flags are updated including held at border flag, held at destination flag, held for FDA flag, and hold location information
R-GCX016E-cbl-00655 Calculate Release Quantities
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Release Quantities' is invoked, and assuming that a release disposition code is being processed, when the system calculates release quantities, the desired outcome is that release quantities are calculated based on the disposition code quantity, existing released quantities, and total cargo quantities with validation that release does not exceed available quantities.
💻 Technical Criteria
Given A release disposition code is being processed
When The system calculates release quantities
Then Release quantities are calculated based on the disposition code quantity, existing released quantities, and total cargo quantities with validation that release does not exceed available quantities
R-GCX016E-cbl-00657 Set Cargo Release Status
Action Rules
📊 Business Logic Narrative
When the process 'Set Cargo Release Status' is invoked, and assuming that a release disposition code has been processed and quantities calculated, when the system sets cargo release status, the desired outcome is that the cargo release status is updated with release type, release quantities, and release location based on the disposition code.
💻 Technical Criteria
Given A release disposition code has been processed and quantities calculated
When The system sets cargo release status
Then The cargo release status is updated with release type, release quantities, and release location based on the disposition code
R-GCX016E-cbl-00658 Update Release Flags
Action Rules
📊 Business Logic Narrative
When the process 'Update Release Flags' is invoked, and assuming that cargo release status has been set for a disposition code, when the system updates release-related information, the desired outcome is that release flags are updated including released flag, ptt flag, ptt exam flag, and release quantity information.
💻 Technical Criteria
Given Cargo release status has been set for a disposition code
When The system updates release-related information
Then Release flags are updated including released flag, PTT flag, PTT exam flag, and release quantity information
R-GCX016E-cbl-00664 Validate Release Conditions
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Release Conditions' is invoked, and assuming that an automatic release is being processed, when the system validates release conditions, the desired outcome is that all release conditions are validated including cargo status, hold status, quantity availability, and regulatory compliance before allowing the release.
💻 Technical Criteria
Given An automatic release is being processed
When The system validates release conditions
Then All release conditions are validated including cargo status, hold status, quantity availability, and regulatory compliance before allowing the release
R-GCX016E-cbl-00666 Generate Hold Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Hold Notification' is invoked, and assuming that a hold disposition code has been processed and cargo status updated, when the system generates hold notifications, the desired outcome is that hold notifications are sent to brokers, freight forwarders, and other relevant parties with hold details, reason, and required actions.
💻 Technical Criteria
Given A hold disposition code has been processed and cargo status updated
When The system generates hold notifications
Then Hold notifications are sent to brokers, freight forwarders, and other relevant parties with hold details, reason, and required actions
R-GCX016E-cbl-00667 Generate Release Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Release Notification' is invoked, and assuming that a release disposition code has been processed and cargo status updated, when the system generates release notifications, the desired outcome is that release notifications are sent to brokers, freight forwarders, and other relevant parties with release details, quantities, and pickup authorization.
💻 Technical Criteria
Given A release disposition code has been processed and cargo status updated
When The system generates release notifications
Then Release notifications are sent to brokers, freight forwarders, and other relevant parties with release details, quantities, and pickup authorization
R-GCX016E-cbl-00668 CPRS Cargo Identified?
Decision Rules
📊 Business Logic Narrative
When the process 'CPRS Cargo Identified?' is invoked, and assuming that a cargo record is being processed for bond assignment, when the system checks the cargo type or carrier information, the desired outcome is that the cargo is identified as cprs cargo if it meets cprs criteria, otherwise it is processed as regular cargo.
💻 Technical Criteria
Given A cargo record is being processed for bond assignment
When The system checks the cargo type or carrier information
Then The cargo is identified as CPRS cargo if it meets CPRS criteria, otherwise it is processed as regular cargo
R-GCX016E-cbl-00669 Retrieve CPRS Bond Information
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve CPRS Bond Information' is invoked, and assuming that a cprs cargo has been identified for bond processing, when the system accesses the us cargo root record, the desired outcome is that current bond number, broker information, and bond status are retrieved from the cargo record.
💻 Technical Criteria
Given A CPRS cargo has been identified for bond processing
When The system accesses the US cargo root record
Then Current bond number, broker information, and bond status are retrieved from the cargo record
R-GCX016E-cbl-00670 Validate Bond Assignment
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Bond Assignment' is invoked, and assuming that cprs bond information has been retrieved, when the system validates the bond assignment against cargo entry type and requirements, the desired outcome is that the bond assignment is confirmed as valid or flagged for correction.
💻 Technical Criteria
Given CPRS bond information has been retrieved
When The system validates the bond assignment against cargo entry type and requirements
Then The bond assignment is confirmed as valid or flagged for correction
R-GCX016E-cbl-00671 Bond Already Assigned?
Decision Rules
📊 Business Logic Narrative
When the process 'Bond Already Assigned?' is invoked, and assuming that bond assignment validation has been completed, when the system checks if a bond number already exists for the cargo, the desired outcome is that if bond number exists and is valid, proceed to update existing bond, otherwise create new bond assignment.
💻 Technical Criteria
Given Bond assignment validation has been completed
When The system checks if a bond number already exists for the cargo
Then If bond number exists and is valid, proceed to update existing bond, otherwise create new bond assignment
R-GCX016E-cbl-00672 Create New Bond Assignment
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Create New Bond Assignment', assuming that cprs cargo does not have an existing valid bond assignment, when the system creates a new bond assignment, the desired outcome is that a new bond number is assigned to the cargo and bond creation is logged.
💻 Technical Criteria
EXCLUDING CPRS cargo does not have an existing valid bond assignment
When The system creates a new bond assignment
Then A new bond number is assigned to the cargo and bond creation is logged
R-GCX016E-cbl-00673 Update Existing Bond
Action Rules
📊 Business Logic Narrative
When the process 'Update Existing Bond' is invoked, and assuming that cprs cargo has an existing valid bond assignment, when the system updates the bond information, the desired outcome is that existing bond record is updated with current cargo processing information and status.
💻 Technical Criteria
Given CPRS cargo has an existing valid bond assignment
When The system updates the bond information
Then Existing bond record is updated with current cargo processing information and status
R-GCX016E-cbl-00679 Clear Previous Bond Data
Action Rules
📊 Business Logic Narrative
When the process 'Clear Previous Bond Data' is invoked, and assuming that bond owner information has been updated, when the system clears previous bond data, the desired outcome is that any conflicting or outdated bond information is removed from the cargo record.
💻 Technical Criteria
Given Bond owner information has been updated
When The system clears previous bond data
Then Any conflicting or outdated bond information is removed from the cargo record
R-GCX016E-cbl-00682 Generate Bond Creation Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Bond Creation Notification' is invoked, and assuming that bond assignment action has been logged, when the system generates bond creation notification, the desired outcome is that notification message is prepared with bond details, cargo information, and routing instructions.
💻 Technical Criteria
Given Bond assignment action has been logged
When The system generates bond creation notification
Then Notification message is prepared with bond details, cargo information, and routing instructions
R-GCX016E-cbl-00684 Update Cargo Record with Bond Info
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Record with Bond Info' is invoked, and assuming that k1 message for bond creation has been sent, when the system updates the cargo record with bond information, the desired outcome is that cargo record is updated with complete bond assignment details, broker information, and processing status.
💻 Technical Criteria
Given K1 message for bond creation has been sent
When The system updates the cargo record with bond information
Then Cargo record is updated with complete bond assignment details, broker information, and processing status
R-GCX016E-cbl-00685 Arrival Disposition Code Received?
Decision Rules
📊 Business Logic Narrative
When the process 'Arrival Disposition Code Received?' is invoked, and assuming that a cargo disposition code is being processed, when the system checks if the disposition code indicates an arrival event, the desired outcome is that the system proceeds with arrival processing if arrival disposition code is present, otherwise skips arrival processing.
💻 Technical Criteria
Given A cargo disposition code is being processed
When The system checks if the disposition code indicates an arrival event
Then The system proceeds with arrival processing if arrival disposition code is present, otherwise skips arrival processing
R-GCX016E-cbl-00687 Set Cargo Arrival Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Cargo Arrival Flag' is invoked, and assuming that a valid arrival location has been confirmed, when the system processes the arrival event, the desired outcome is that the cargo arrival flag is set to indicate arrival status.
💻 Technical Criteria
Given A valid arrival location has been confirmed
When The system processes the arrival event
Then The cargo arrival flag is set to indicate arrival status
R-GCX016E-cbl-00688 Clear Bond Start Date
Action Rules
📊 Business Logic Narrative
When the process 'Clear Bond Start Date' is invoked, and assuming that cargo arrival flag has been set, when the system processes bond-related information for the arrived cargo, the desired outcome is that the bond start date is cleared to reset bond timing.
💻 Technical Criteria
Given Cargo arrival flag has been set
When The system processes bond-related information for the arrived cargo
Then The bond start date is cleared to reset bond timing
R-GCX016E-cbl-00689 Set Arrival Index
Action Rules
📊 Business Logic Narrative
When the process 'Set Arrival Index' is invoked, and assuming that bond start date has been cleared for arrived cargo, when the system assigns location tracking information, the desired outcome is that an arrival index is set to identify the specific arrival location.
💻 Technical Criteria
Given Bond start date has been cleared for arrived cargo
When The system assigns location tracking information
Then An arrival index is set to identify the specific arrival location
R-GCX016E-cbl-00690 Calculate Cargo Age
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Cargo Age' is invoked, and assuming that arrival index has been set for the cargo, when the system calculates cargo timing information, the desired outcome is that cargo age is calculated based on arrival date and relevant timing factors.
💻 Technical Criteria
Given Arrival index has been set for the cargo
When The system calculates cargo timing information
Then Cargo age is calculated based on arrival date and relevant timing factors
R-GCX016E-cbl-00691 Update Cargo Status to Arrived
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status to Arrived' is invoked, and assuming that cargo age has been calculated, when the system updates cargo status information, the desired outcome is that the cargo status is updated to 'arrived' to reflect current state.
💻 Technical Criteria
Given Cargo age has been calculated
When The system updates cargo status information
Then The cargo status is updated to 'Arrived' to reflect current state
R-GCX016E-cbl-00692 Generate Arrival Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Arrival Notification' is invoked, and assuming that cargo status has been updated to arrived, when the system processes notification requirements, the desired outcome is that an arrival notification is generated for internal tracking and reporting.
💻 Technical Criteria
Given Cargo status has been updated to arrived
When The system processes notification requirements
Then An arrival notification is generated for internal tracking and reporting
R-GCX016E-cbl-00693 Send AEI Notification Message
Action Rules
📊 Business Logic Narrative
When the process 'Send AEI Notification Message' is invoked, and assuming that arrival notification has been generated, when the system processes external notification requirements, the desired outcome is that an aei notification message is sent to external systems for equipment tracking.
💻 Technical Criteria
Given Arrival notification has been generated
When The system processes external notification requirements
Then An AEI notification message is sent to external systems for equipment tracking
R-GCX016E-cbl-00695 Update Destination Index
Action Rules
📊 Business Logic Narrative
When the process 'Update Destination Index' is invoked, and assuming that arrival action has been logged, when the system updates location tracking information, the desired outcome is that the destination index is updated to reflect the current cargo location.
💻 Technical Criteria
Given Arrival action has been logged
When The system updates location tracking information
Then The destination index is updated to reflect the current cargo location
R-GCX016E-cbl-00696 Trigger GCCIIS Status Update
Action Rules
📊 Business Logic Narrative
When the process 'Trigger GCCIIS Status Update' is invoked, and assuming that destination index has been updated, when the system processes external system synchronization requirements, the desired outcome is that a gcciis status update is triggered to synchronize cargo information with external systems.
💻 Technical Criteria
Given Destination index has been updated
When The system processes external system synchronization requirements
Then A GCCIIS status update is triggered to synchronize cargo information with external systems
R-GCX016E-cbl-00698 Export Disposition Code Received?
Decision Rules
📊 Business Logic Narrative
When the process 'Export Disposition Code Received?' is invoked, and assuming that a disposition code has been received for cargo processing, when the system evaluates the disposition code type, the desired outcome is that the system identifies if it is an export disposition code and proceeds with export processing or skips to completion.
💻 Technical Criteria
Given A disposition code has been received for cargo processing
When The system evaluates the disposition code type
Then The system identifies if it is an export disposition code and proceeds with export processing or skips to completion
R-GCX016E-cbl-00701 Set Export Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Export Status Flag' is invoked, and assuming that a valid export port has been confirmed for the cargo, when the system processes the export disposition code, the desired outcome is that the system sets the export status flag to active in the cargo record.
💻 Technical Criteria
Given A valid export port has been confirmed for the cargo
When The system processes the export disposition code
Then The system sets the export status flag to active in the cargo record
R-GCX016E-cbl-00702 Clear Destination Index
Action Rules
📊 Business Logic Narrative
When the process 'Clear Destination Index' is invoked, and assuming that the export status flag has been set for the cargo, when the system processes the export status change, the desired outcome is that the system clears the destination index field to remove domestic destination references.
💻 Technical Criteria
Given The export status flag has been set for the cargo
When The system processes the export status change
Then The system clears the destination index field to remove domestic destination references
R-GCX016E-cbl-00703 Update Export Date/Time
Action Rules
📊 Business Logic Narrative
When the process 'Update Export Date/Time' is invoked, and assuming that the destination index has been cleared for the export cargo, when the system finalizes the export status change, the desired outcome is that the system updates the export date and time fields with the current timestamp.
💻 Technical Criteria
Given The destination index has been cleared for the export cargo
When The system finalizes the export status change
Then The system updates the export date and time fields with the current timestamp
R-GCX016E-cbl-00704 Check Previous Export Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check Previous Export Status' is invoked, and assuming that the export date and time have been updated for the cargo, when the system checks the cargo's previous processing history, the desired outcome is that the system retrieves the current export status to determine if duplicate processing should be prevented.
💻 Technical Criteria
Given The export date and time have been updated for the cargo
When The system checks the cargo's previous processing history
Then The system retrieves the current export status to determine if duplicate processing should be prevented
R-GCX016E-cbl-00705 Already Exported?
Decision Rules
📊 Business Logic Narrative
When the process 'Already Exported?' is invoked, and assuming that the system has checked the cargo's previous export status, when the system evaluates if the cargo already has an active export status, the desired outcome is that the system either skips duplicate processing or continues with new export notification.
💻 Technical Criteria
Given The system has checked the cargo's previous export status
When The system evaluates if the cargo already has an active export status
Then The system either skips duplicate processing or continues with new export notification
R-GCX016E-cbl-00706 Skip Duplicate Export
Process Rules
📊 Business Logic Narrative
When the process 'Skip Duplicate Export' is invoked, and assuming that the cargo has already been processed for export, when the system detects duplicate export processing, the desired outcome is that the system skips the export notification and completes processing without generating duplicate messages.
💻 Technical Criteria
Given The cargo has already been processed for export
When The system detects duplicate export processing
Then The system skips the export notification and completes processing without generating duplicate messages
R-GCX016E-cbl-00707 Generate Export Notification
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Export Notification', assuming that the cargo has not been previously exported, when the system processes the export status change, the desired outcome is that the system generates a new export notification message for distribution.
💻 Technical Criteria
EXCLUDING The cargo has not been previously exported
When The system processes the export status change
Then The system generates a new export notification message for distribution
R-GCX016E-cbl-00709 Include Cargo Details
Process Rules
📊 Business Logic Narrative
When the process 'Include Cargo Details' is invoked, and assuming that the export message format has been established, when the system populates the message content, the desired outcome is that the system includes cargo identification, quantities, and relevant cargo details in the export message.
💻 Technical Criteria
Given The export message format has been established
When The system populates the message content
Then The system includes cargo identification, quantities, and relevant cargo details in the export message
R-GCX016E-cbl-00710 Add Location Information
Process Rules
📊 Business Logic Narrative
When the process 'Add Location Information' is invoked, and assuming that cargo details have been included in the export message, when the system completes the message content, the desired outcome is that the system adds the export port code, location name, and relevant geographic information to the message.
💻 Technical Criteria
Given Cargo details have been included in the export message
When The system completes the message content
Then The system adds the export port code, location name, and relevant geographic information to the message
R-GCX016E-cbl-00711 Send Export Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send Export Notification' is invoked, and assuming that the export notification message has been fully formatted with cargo and location details, when the system is ready to distribute the notification, the desired outcome is that the system sends the export notification to designated recipients and systems.
💻 Technical Criteria
Given The export notification message has been fully formatted with cargo and location details
When The system is ready to distribute the notification
Then The system sends the export notification to designated recipients and systems
R-GCX016E-cbl-00712 Update Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Record' is invoked, and assuming that the export notification has been successfully sent, when the system finalizes the export processing, the desired outcome is that the system updates the cargo record in the database with the export status, date, time, and location information.
💻 Technical Criteria
Given The export notification has been successfully sent
When The system finalizes the export processing
Then The system updates the cargo record in the database with the export status, date, time, and location information
R-GCX016E-cbl-00713 Log Export Action
Action Rules
📊 Business Logic Narrative
When the process 'Log Export Action' is invoked, and assuming that the cargo record has been updated with export information, when the system completes the export processing workflow, the desired outcome is that the system creates a log entry documenting the export action, timestamp, and processing details.
💻 Technical Criteria
Given The cargo record has been updated with export information
When The system completes the export processing workflow
Then The system creates a log entry documenting the export action, timestamp, and processing details
R-GCX016E-cbl-00716 Cargo Has Arrival Status?
Validation Rules
📊 Business Logic Narrative
When the process 'Cargo Has Arrival Status?' is invoked, and assuming that a cargo record exists in the system, when cancel arrival processing is triggered for the cargo, the desired outcome is that system checks if cargo has arrival status and only proceeds with cancellation if arrival status exists, otherwise skips cancellation processing.
💻 Technical Criteria
Given A cargo record exists in the system
When Cancel arrival processing is triggered for the cargo
Then System checks if cargo has arrival status and only proceeds with cancellation if arrival status exists, otherwise skips cancellation processing
R-GCX016E-cbl-00717 Reset Arrival Flag to False
Action Rules
📊 Business Logic Narrative
When the process 'Reset Arrival Flag to False' is invoked, and assuming that cargo has been validated to have arrival status, when arrival cancellation is authorized and processed, the desired outcome is that system sets the cargo arrival flag to false to indicate cargo is no longer in arrived status.
💻 Technical Criteria
Given Cargo has been validated to have arrival status
When Arrival cancellation is authorized and processed
Then System sets the cargo arrival flag to false to indicate cargo is no longer in arrived status
R-GCX016E-cbl-00718 Clear Arrival Date Information
Action Rules
📊 Business Logic Narrative
When the process 'Clear Arrival Date Information' is invoked, and assuming that cargo arrival flag has been reset to false, when arrival cancellation processing continues, the desired outcome is that system clears all arrival date and time fields from the cargo record.
💻 Technical Criteria
Given Cargo arrival flag has been reset to false
When Arrival cancellation processing continues
Then System clears all arrival date and time fields from the cargo record
R-GCX016E-cbl-00719 Update Cargo Status Arrays
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status Arrays' is invoked, and assuming that arrival date information has been cleared from cargo record, when status array processing is performed, the desired outcome is that system updates cargo status arrays to remove arrival-related status entries and recalculate current status.
💻 Technical Criteria
Given Arrival date information has been cleared from cargo record
When Status array processing is performed
Then System updates cargo status arrays to remove arrival-related status entries and recalculate current status
R-GCX016E-cbl-00720 Remove Arrival Disposition Codes
Action Rules
📊 Business Logic Narrative
When the process 'Remove Arrival Disposition Codes' is invoked, and assuming that cargo status arrays have been updated for cancellation, when disposition code processing is performed, the desired outcome is that system removes all arrival-related disposition codes from cargo status array.
💻 Technical Criteria
Given Cargo status arrays have been updated for cancellation
When Disposition code processing is performed
Then System removes all arrival-related disposition codes from cargo status array
R-GCX016E-cbl-00721 Restore Previous Bond Information
Action Rules
📊 Business Logic Narrative
When the process 'Restore Previous Bond Information' is invoked, and assuming that arrival disposition codes have been removed from cargo, when bond information restoration is processed, the desired outcome is that system restores the cargo's previous bond number and related bond information that existed before arrival processing.
💻 Technical Criteria
Given Arrival disposition codes have been removed from cargo
When Bond information restoration is processed
Then System restores the cargo's previous bond number and related bond information that existed before arrival processing
R-GCX016E-cbl-00722 Recalculate Cargo Age
Computation Rules
📊 Business Logic Narrative
When the process 'Recalculate Cargo Age' is invoked, and assuming that previous bond information has been restored to cargo, when cargo age calculation is performed, the desired outcome is that system recalculates cargo age using original entry date and current date, excluding the cancelled arrival period.
💻 Technical Criteria
Given Previous bond information has been restored to cargo
When Cargo age calculation is performed
Then System recalculates cargo age using original entry date and current date, excluding the cancelled arrival period
R-GCX016E-cbl-00723 Clear Destination Index
Action Rules
📊 Business Logic Narrative
When the process 'Clear Destination Index' is invoked, and assuming that cargo age has been recalculated after cancellation, when destination processing is performed, the desired outcome is that system clears the destination index field to remove destination-specific routing information.
💻 Technical Criteria
Given Cargo age has been recalculated after cancellation
When Destination processing is performed
Then System clears the destination index field to remove destination-specific routing information
R-GCX016E-cbl-00727 Generate Arrival Cancellation Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Arrival Cancellation Notification' is invoked, and assuming that all cargo records have been verified as updated or single cargo processing is complete, when notification generation is triggered, the desired outcome is that system creates arrival cancellation notification message with cargo details and cancellation information.
💻 Technical Criteria
Given All cargo records have been verified as updated OR single cargo processing is complete
When Notification generation is triggered
Then System creates arrival cancellation notification message with cargo details and cancellation information
R-GCX016E-cbl-00728 Update Audit Trail
Process Rules
📊 Business Logic Narrative
When the process 'Update Audit Trail' is invoked, and assuming that arrival cancellation notification has been generated, when audit trail processing is performed, the desired outcome is that system records arrival cancellation transaction in audit trail with timestamp, user information, and affected cargo details.
💻 Technical Criteria
Given Arrival cancellation notification has been generated
When Audit trail processing is performed
Then System records arrival cancellation transaction in audit trail with timestamp, user information, and affected cargo details
R-GCX016E-cbl-00730 Validate Cancel Export Request
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Cancel Export Request' is invoked, and assuming that a cancel export disposition code is received for a cargo, when the system processes the cancel export request, the desired outcome is that the system validates the request parameters and ensures the cargo exists and is accessible.
💻 Technical Criteria
Given A cancel export disposition code is received for a cargo
When The system processes the cancel export request
Then The system validates the request parameters and ensures the cargo exists and is accessible
R-GCX016E-cbl-00731 Export Status Currently Active?
Decision Rules
📊 Business Logic Narrative
When the process 'Export Status Currently Active?' is invoked, and assuming that a cancel export request is being processed for a cargo, when the system checks the current cargo status, the desired outcome is that the system determines if export status is currently active and proceeds only if export status exists.
💻 Technical Criteria
Given A cancel export request is being processed for a cargo
When The system checks the current cargo status
Then The system determines if export status is currently active and proceeds only if export status exists
R-GCX016E-cbl-00732 Retrieve Current Export Information
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Export Information' is invoked, and assuming that a cargo has active export status that needs to be cancelled, when the system needs to process the export cancellation, the desired outcome is that the system retrieves current export date, destination information, and export status flags from the cargo record.
💻 Technical Criteria
Given A cargo has active export status that needs to be cancelled
When The system needs to process the export cancellation
Then The system retrieves current export date, destination information, and export status flags from the cargo record
R-GCX016E-cbl-00733 Clear Export Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Clear Export Status Flag' is invoked, and assuming that a cargo export cancellation is being processed and current export information has been retrieved, when the system clears the export status, the desired outcome is that the export status flag is set to inactive or cleared in the cargo record.
💻 Technical Criteria
Given A cargo export cancellation is being processed and current export information has been retrieved
When The system clears the export status
Then The export status flag is set to inactive or cleared in the cargo record
R-GCX016E-cbl-00734 Reset Export Date Fields
Action Rules
📊 Business Logic Narrative
When the process 'Reset Export Date Fields' is invoked, and assuming that a cargo export status is being cancelled and export status flag has been cleared, when the system resets export date information, the desired outcome is that export date fields are cleared or reset to null values in the cargo record.
💻 Technical Criteria
Given A cargo export status is being cancelled and export status flag has been cleared
When The system resets export date information
Then Export date fields are cleared or reset to null values in the cargo record
R-GCX016E-cbl-00735 Clear Destination Index
Action Rules
📊 Business Logic Narrative
When the process 'Clear Destination Index' is invoked, and assuming that a cargo export is being cancelled and export date fields have been reset, when the system clears destination information, the desired outcome is that the destination index is cleared or reset in the cargo record.
💻 Technical Criteria
Given A cargo export is being cancelled and export date fields have been reset
When The system clears destination information
Then The destination index is cleared or reset in the cargo record
R-GCX016E-cbl-00736 Restore Previous Cargo Status
Process Rules
📊 Business Logic Narrative
When the process 'Restore Previous Cargo Status' is invoked, and assuming that a cargo export has been cancelled and destination index has been cleared, when the system restores the previous cargo status, the desired outcome is that the cargo status is reverted to the status it had before export processing, typically 'ack' or previous processing status.
💻 Technical Criteria
Given A cargo export has been cancelled and destination index has been cleared
When The system restores the previous cargo status
Then The cargo status is reverted to the status it had before export processing, typically 'ACK' or previous processing status
R-GCX016E-cbl-00737 Update Cargo Status Arrays
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status Arrays' is invoked, and assuming that a cargo export has been cancelled and previous status has been restored, when the system updates status tracking arrays, the desired outcome is that the s09 status arrays are updated to remove export-related status entries and add cancellation status information.
💻 Technical Criteria
Given A cargo export has been cancelled and previous status has been restored
When The system updates status tracking arrays
Then The S09 status arrays are updated to remove export-related status entries and add cancellation status information
R-GCX016E-cbl-00738 Generate Cancel Export Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Cancel Export Notification' is invoked, and assuming that a cargo export has been cancelled and status arrays have been updated, when the system generates export cancellation notification, the desired outcome is that a notification message is created containing cargo details, cancellation information, and relevant business data for stakeholders.
💻 Technical Criteria
Given A cargo export has been cancelled and status arrays have been updated
When The system generates export cancellation notification
Then A notification message is created containing cargo details, cancellation information, and relevant business data for stakeholders
R-GCX016E-cbl-00739 Log Cancel Export Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Cancel Export Action' is invoked, and assuming that an export cancellation notification has been generated, when the system logs the cancellation action, the desired outcome is that the export cancellation action is recorded with timestamp, user information, cargo details, and cancellation reason for audit trail.
💻 Technical Criteria
Given An export cancellation notification has been generated
When The system logs the cancellation action
Then The export cancellation action is recorded with timestamp, user information, cargo details, and cancellation reason for audit trail
R-GCX016E-cbl-00741 Update Cargo Record in Database
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Record in Database' is invoked, and assuming that all export cancellation processing has been completed and notifications sent, when the system updates the cargo record in the database, the desired outcome is that the cargo record is updated in the database with all export cancellation changes, including cleared export status, reset dates, restored previous status, and updated status arrays.
💻 Technical Criteria
Given All export cancellation processing has been completed and notifications sent
When The system updates the cargo record in the database
Then The cargo record is updated in the database with all export cancellation changes, including cleared export status, reset dates, restored previous status, and updated status arrays
R-GCX016E-cbl-00742 Retrieve Current Cargo Release Quantity
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Cargo Release Quantity' is invoked, and assuming that a cargo record exists in the system, when the release quantity management process is initiated, the desired outcome is that the current release quantity is retrieved from the cargo record and stored for processing.
💻 Technical Criteria
Given A cargo record exists in the system
When The release quantity management process is initiated
Then The current release quantity is retrieved from the cargo record and stored for processing
R-GCX016E-cbl-00743 Get Disposition Code from Status Array
Action Rules
📊 Business Logic Narrative
When the process 'Get Disposition Code from Status Array' is invoked, and assuming that a cargo status array (s09a) contains disposition codes, when processing release quantity calculations, the desired outcome is that the disposition code is extracted from the status array for further processing.
💻 Technical Criteria
Given A cargo status array (S09A) contains disposition codes
When Processing release quantity calculations
Then The disposition code is extracted from the status array for further processing
R-GCX016E-cbl-00751 Validate Release Quantity Against Total Quantity
Process Rules
📊 Business Logic Narrative
When the process 'Validate Release Quantity Against Total Quantity' is invoked, and assuming that release quantity has been calculated based on disposition code action, when the system validates the calculated release quantity, the desired outcome is that the release quantity is compared against the total cargo quantity for validation.
💻 Technical Criteria
Given Release quantity has been calculated based on disposition code action
When The system validates the calculated release quantity
Then The release quantity is compared against the total cargo quantity for validation
R-GCX016E-cbl-00752 Release Quantity > Total Quantity?
Validation Rules
📊 Business Logic Narrative
When the process 'Release Quantity > Total Quantity?' is invoked, and assuming that a calculated release quantity exists, when the release quantity is validated against total cargo quantity, the desired outcome is that if release quantity exceeds total quantity, the release quantity is set equal to total quantity.
💻 Technical Criteria
Given A calculated release quantity exists
When The release quantity is validated against total cargo quantity
Then If release quantity exceeds total quantity, the release quantity is set equal to total quantity
R-GCX016E-cbl-00753 Set Release Quantity = Total Quantity
Validation Rules
📊 Business Logic Narrative
When the process 'Set Release Quantity = Total Quantity' is invoked, and assuming that the calculated release quantity exceeds the total cargo quantity, when the system applies quantity validation rules, the desired outcome is that the release quantity is set equal to the total cargo quantity.
💻 Technical Criteria
Given The calculated release quantity exceeds the total cargo quantity
When The system applies quantity validation rules
Then The release quantity is set equal to the total cargo quantity
R-GCX016E-cbl-00756 Update Cargo Record with New Release Quantity
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Record with New Release Quantity' is invoked, and assuming that a validated release quantity has been calculated, when the quantity processing is complete, the desired outcome is that the cargo record is updated with the new release quantity.
💻 Technical Criteria
Given A validated release quantity has been calculated
When The quantity processing is complete
Then The cargo record is updated with the new release quantity
R-GCX016E-cbl-00757 Calculate Quantity Impact for Merlin Message
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Quantity Impact for Merlin Message' is invoked, and assuming that the cargo record has been updated with new release quantity, when preparing merlin notification messages, the desired outcome is that the quantity impact (difference between old and new release quantity) is calculated for message content.
💻 Technical Criteria
Given The cargo record has been updated with new release quantity
When Preparing Merlin notification messages
Then The quantity impact (difference between old and new release quantity) is calculated for message content
R-GCX016E-cbl-02999 Retrieve Current Release Quantity
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Release Quantity' is invoked, and assuming that a cargo record exists with release quantity information, when the system processes a disposition code that may affect quantities, the desired outcome is that the current release quantity is retrieved and stored for calculation purposes.
💻 Technical Criteria
Given A cargo record exists with release quantity information
When The system processes a disposition code that may affect quantities
Then The current release quantity is retrieved and stored for calculation purposes
R-GCX016E-cbl-03005 Validate Against Total Quantity
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Against Total Quantity' is invoked, and assuming that a new release quantity has been calculated, when the system validates the calculated quantity, the desired outcome is that the release quantity is checked against total cargo quantity for validity.
💻 Technical Criteria
Given A new release quantity has been calculated
When The system validates the calculated quantity
Then The release quantity is checked against total cargo quantity for validity
R-GCX016E-cbl-03006 Set Release Qty = Total Qty
Validation Rules
📊 Business Logic Narrative
When the process 'Set Release Qty = Total Qty' is invoked, and assuming that calculated release quantity exceeds total cargo quantity, when the system applies quantity validation rules, the desired outcome is that release quantity is set equal to total cargo quantity.
💻 Technical Criteria
Given Calculated release quantity exceeds total cargo quantity
When The system applies quantity validation rules
Then Release quantity is set equal to total cargo quantity
R-GCX016E-cbl-03008 Update Release Quantity
Process Rules
📊 Business Logic Narrative
When the process 'Update Release Quantity' is invoked, and assuming that a validated new release quantity is available, when the system updates cargo information, the desired outcome is that the cargo record release quantity is updated with the new validated amount.
💻 Technical Criteria
Given A validated new release quantity is available
When The system updates cargo information
Then The cargo record release quantity is updated with the new validated amount
R-GCX016E-cbl-00762 Hold Status Detected in Cargo
Decision Rules
📊 Business Logic Narrative
When the process 'Hold Status Detected in Cargo' is invoked, and assuming that a cargo record exists with status information, when the system evaluates cargo status and finds hold conditions are present, the desired outcome is that the hold notification process is triggered and hold information gathering begins.
💻 Technical Criteria
Given A cargo record exists with status information
When The system evaluates cargo status and finds hold conditions are present
Then The hold notification process is triggered and hold information gathering begins
R-GCX016E-cbl-00763 Gather Hold Information
Process Rules
📊 Business Logic Narrative
When the process 'Gather Hold Information' is invoked, and assuming that hold status has been detected for a cargo, when the system begins gathering hold information from gcsuss09 status segments, the desired outcome is that all relevant hold data including hold type, priority, and status validation is collected.
💻 Technical Criteria
Given Hold status has been detected for a cargo
When The system begins gathering hold information from GCSUSS09 status segments
Then All relevant hold data including hold type, priority, and status validation is collected
R-GCX016E-cbl-00764 Check Hold Type
Decision Rules
📊 Business Logic Narrative
When the process 'Check Hold Type' is invoked, and assuming that hold information is being gathered for a cargo, when the system examines the hold status codes and disposition information, the desired outcome is that the hold type is classified as border hold, destination hold, fda hold, or other specific hold category.
💻 Technical Criteria
Given Hold information is being gathered for a cargo
When The system examines the hold status codes and disposition information
Then The hold type is classified as border hold, destination hold, FDA hold, or other specific hold category
R-GCX016E-cbl-00765 Validate Hold Status
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Hold Status' is invoked, and assuming that a hold type has been identified for cargo, when the system validates the hold status against current business rules, the desired outcome is that the hold status is confirmed as valid and active, or flagged for correction.
💻 Technical Criteria
Given A hold type has been identified for cargo
When The system validates the hold status against current business rules
Then The hold status is confirmed as valid and active, or flagged for correction
R-GCX016E-cbl-00766 Determine Hold Priority
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Hold Priority' is invoked, and assuming that hold status has been validated for cargo, when the system evaluates hold type and associated business rules, the desired outcome is that hold priority is determined based on hold type hierarchy and urgency requirements.
💻 Technical Criteria
Given Hold status has been validated for cargo
When The system evaluates hold type and associated business rules
Then Hold priority is determined based on hold type hierarchy and urgency requirements
R-GCX016E-cbl-00767 Collect Disposition Code Details
Process Rules
📊 Business Logic Narrative
When the process 'Collect Disposition Code Details' is invoked, and assuming that hold information has been gathered for cargo, when the system accesses gcstbrt table segments for disposition code details, the desired outcome is that complete disposition code information including descriptions and hold reasons is collected.
💻 Technical Criteria
Given Hold information has been gathered for cargo
When The system accesses GCSTBRT table segments for disposition code details
Then Complete disposition code information including descriptions and hold reasons is collected
R-GCX016E-cbl-00771 Format Hold Notification Message
Process Rules
📊 Business Logic Narrative
When the process 'Format Hold Notification Message' is invoked, and assuming that all hold information and location data have been retrieved, when the system begins formatting the notification message, the desired outcome is that a structured message template is prepared with placeholders for equipment, cargo, and location details.
💻 Technical Criteria
Given All hold information and location data have been retrieved
When The system begins formatting the notification message
Then A structured message template is prepared with placeholders for equipment, cargo, and location details
R-GCX016E-cbl-00773 Format Car ID
Computation Rules
📊 Business Logic Narrative
When the process 'Format Car ID' is invoked, and assuming that equipment details are being included in the notification, when the system processes car identification data, the desired outcome is that car id is formatted according to standard notation and included in the message.
💻 Technical Criteria
Given Equipment details are being included in the notification
When The system processes car identification data
Then Car ID is formatted according to standard notation and included in the message
R-GCX016E-cbl-00777 Include Hold Reason Code
Process Rules
📊 Business Logic Narrative
When the process 'Include Hold Reason Code' is invoked, and assuming that cargo identification has been added to the notification, when the system processes hold reason information, the desired outcome is that hold reason codes and associated explanations are included in the notification message.
💻 Technical Criteria
Given Cargo identification has been added to the notification
When The system processes hold reason information
Then Hold reason codes and associated explanations are included in the notification message
R-GCX016E-cbl-00783 Combine All Elements
Process Rules
📊 Business Logic Narrative
When the process 'Combine All Elements' is invoked, and assuming that all individual message components have been prepared, when the system combines equipment, cargo, location, and hold information, the desired outcome is that all elements are properly integrated into a single comprehensive message structure.
💻 Technical Criteria
Given All individual message components have been prepared
When The system combines equipment, cargo, location, and hold information
Then All elements are properly integrated into a single comprehensive message structure
R-GCX016E-cbl-00788 Initialize Status Analysis Variables
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Status Analysis Variables' is invoked, and assuming that a cargo status array verification process is starting, when the system begins status analysis, the desired outcome is that all hold status flags, release status flags, proceed status flags, and information status flags are set to initial values.
💻 Technical Criteria
Given A cargo status array verification process is starting
When The system begins status analysis
Then All hold status flags, release status flags, proceed status flags, and information status flags are set to initial values
R-GCX016E-cbl-00789 Loop Through S09A Status Array Entries
Process Rules
📊 Business Logic Narrative
When the process 'Loop Through S09A Status Array Entries' is invoked, and assuming that a cargo has s09a status array entries, when the system processes the status array, the desired outcome is that each status entry in the array is examined sequentially until all entries are processed.
💻 Technical Criteria
Given A cargo has S09A status array entries
When The system processes the status array
Then Each status entry in the array is examined sequentially until all entries are processed
R-GCX016E-cbl-00796 Process Status Information Code
Process Rules
📊 Business Logic Narrative
When the process 'Process Status Information Code' is invoked, and assuming that a status entry contains an information-type disposition code, when the information disposition code is processed, the desired outcome is that informational data is extracted and recorded without affecting cargo processing status.
💻 Technical Criteria
Given A status entry contains an information-type disposition code
When The information disposition code is processed
Then Informational data is extracted and recorded without affecting cargo processing status
R-GCX016E-cbl-00799 Update Proceed Status Flags
Process Rules
📊 Business Logic Narrative
When the process 'Update Proceed Status Flags' is invoked, and assuming that a proceed disposition code has been processed, when proceed status flags are updated, the desired outcome is that proceed flags are set to indicate cargo can proceed to destination or next processing step.
💻 Technical Criteria
Given A proceed disposition code has been processed
When Proceed status flags are updated
Then Proceed flags are set to indicate cargo can proceed to destination or next processing step
R-GCX016E-cbl-00802 Has Hold Codes?
Decision Rules
📊 Business Logic Narrative
When the process 'Has Hold Codes?' is invoked, and assuming that status array processing is complete, when hold code presence is evaluated, the desired outcome is that if any hold flags are set, the cargo has hold conditions; otherwise proceed to check other status types.
💻 Technical Criteria
Given Status array processing is complete
When Hold code presence is evaluated
Then If any hold flags are set, the cargo has hold conditions; otherwise proceed to check other status types
R-GCX016E-cbl-00805 Set Final Status: HELD
Decision Rules
📊 Business Logic Narrative
When the process 'Set Final Status: HELD' is invoked, and assuming that hold codes exist and no overriding release codes are present, when final status is determined, the desired outcome is that the cargo status is set to held with appropriate hold reason and location.
💻 Technical Criteria
Given Hold codes exist and no overriding release codes are present
When Final status is determined
Then The cargo status is set to HELD with appropriate hold reason and location
R-GCX016E-cbl-00806 Set Final Status: RELEASED
Decision Rules
📊 Business Logic Narrative
When the process 'Set Final Status: RELEASED' is invoked, and assuming that release codes exist that override any hold conditions, when final status is determined, the desired outcome is that the cargo status is set to released with appropriate release quantity and authority.
💻 Technical Criteria
Given Release codes exist that override any hold conditions
When Final status is determined
Then The cargo status is set to RELEASED with appropriate release quantity and authority
R-GCX016E-cbl-00807 Set Final Status: PROCEED
Decision Rules
📊 Business Logic Narrative
When the process 'Set Final Status: PROCEED' is invoked, and assuming that proceed codes exist and no hold or overriding release codes are present, when final status is determined, the desired outcome is that the cargo status is set to proceed allowing movement to next processing step.
💻 Technical Criteria
Given Proceed codes exist and no hold or overriding release codes are present
When Final status is determined
Then The cargo status is set to PROCEED allowing movement to next processing step
R-GCX016E-cbl-00808 Set Final Status: INFORMATION ONLY
Decision Rules
📊 Business Logic Narrative
When the process 'Set Final Status: INFORMATION ONLY' is invoked, and assuming that only information codes exist with no hold, release, or proceed codes, when final status is determined, the desired outcome is that the cargo status is set to information only indicating no action required.
💻 Technical Criteria
Given Only information codes exist with no hold, release, or proceed codes
When Final status is determined
Then The cargo status is set to INFORMATION ONLY indicating no action required
R-GCX016E-cbl-00810 Determine Final Cargo Status
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Final Cargo Status' is invoked, and assuming that status evaluation and quantity calculations are complete, when final cargo status is determined, the desired outcome is that the definitive cargo status is established considering all disposition codes, quantities, and business rules.
💻 Technical Criteria
Given Status evaluation and quantity calculations are complete
When Final cargo status is determined
Then The definitive cargo status is established considering all disposition codes, quantities, and business rules
R-GCX016E-cbl-00811 Update Cargo Status Flags
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status Flags' is invoked, and assuming that final cargo status has been determined, when cargo status flags are updated, the desired outcome is that the cargo record is updated with the new status, quantities, and any status-related data.
💻 Technical Criteria
Given Final cargo status has been determined
When Cargo status flags are updated
Then The cargo record is updated with the new status, quantities, and any status-related data
R-GCX016E-cbl-00812 Initialize Status Flags
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Status Flags' is invoked, and assuming that a cargo status analysis process is starting, when the system begins individual status analysis, the desired outcome is that all status flags (hold, release, proceed, status info, manual release) are set to false or initial values.
💻 Technical Criteria
Given A cargo status analysis process is starting
When The system begins individual status analysis
Then All status flags (hold, release, proceed, status info, manual release) are set to false or initial values
R-GCX016E-cbl-00813 Get Next Status Array Entry
Process Rules
📊 Business Logic Narrative
When the process 'Get Next Status Array Entry' is invoked, and assuming that a cargo status array contains multiple disposition code entries, when the system processes status entries sequentially, the desired outcome is that the next unprocessed status array entry is retrieved for evaluation.
💻 Technical Criteria
Given A cargo status array contains multiple disposition code entries
When The system processes status entries sequentially
Then The next unprocessed status array entry is retrieved for evaluation
R-GCX016E-cbl-00814 More Entries?
Decision Rules
📊 Business Logic Narrative
When the process 'More Entries?' is invoked, and assuming that a cargo status array is being processed sequentially, when the system checks for remaining entries after processing current entry, the desired outcome is that if more entries exist, continue processing; otherwise proceed to final status determination.
💻 Technical Criteria
Given A cargo status array is being processed sequentially
When The system checks for remaining entries after processing current entry
Then If more entries exist, continue processing; otherwise proceed to final status determination
R-GCX016E-cbl-00821 Evaluate Hold Conditions
Decision Rules
📊 Business Logic Narrative
When the process 'Evaluate Hold Conditions' is invoked, and assuming that a hold status flag has been set from disposition code analysis, when the system evaluates hold-specific business conditions (location, quantity, regulatory requirements), the desired outcome is that hold conditions are assessed to determine if cargo hold business flag should be activated.
💻 Technical Criteria
Given A hold status flag has been set from disposition code analysis
When The system evaluates hold-specific business conditions (location, quantity, regulatory requirements)
Then Hold conditions are assessed to determine if cargo hold business flag should be activated
R-GCX016E-cbl-00822 Hold Status Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Hold Status Found?' is invoked, and assuming that hold conditions have been evaluated for a cargo, when the system checks if hold status should be applied, the desired outcome is that if hold conditions are met, set cargo hold business flag; otherwise proceed to release evaluation.
💻 Technical Criteria
Given Hold conditions have been evaluated for a cargo
When The system checks if hold status should be applied
Then If hold conditions are met, set cargo hold business flag; otherwise proceed to release evaluation
R-GCX016E-cbl-00823 Set Cargo Hold Business Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Cargo Hold Business Flag' is invoked, and assuming that hold conditions have been evaluated and determined to be applicable, when the system confirms hold status should be applied to cargo, the desired outcome is that the cargo hold business flag is set to indicate cargo is in hold status.
💻 Technical Criteria
Given Hold conditions have been evaluated and determined to be applicable
When The system confirms hold status should be applied to cargo
Then The cargo hold business flag is set to indicate cargo is in hold status
R-GCX016E-cbl-00824 Evaluate Release Conditions
Decision Rules
📊 Business Logic Narrative
When the process 'Evaluate Release Conditions' is invoked, and assuming that a release status flag has been set or hold evaluation is complete, when the system evaluates release-specific business conditions (quantity validation, regulatory clearance), the desired outcome is that release conditions are assessed to determine if cargo release business flag should be activated.
💻 Technical Criteria
Given A release status flag has been set or hold evaluation is complete
When The system evaluates release-specific business conditions (quantity validation, regulatory clearance)
Then Release conditions are assessed to determine if cargo release business flag should be activated
R-GCX016E-cbl-00825 Release Status Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Release Status Found?' is invoked, and assuming that release conditions have been evaluated for a cargo, when the system checks if release status should be applied, the desired outcome is that if release conditions are met, set cargo release business flag; otherwise proceed to proceed evaluation.
💻 Technical Criteria
Given Release conditions have been evaluated for a cargo
When The system checks if release status should be applied
Then If release conditions are met, set cargo release business flag; otherwise proceed to proceed evaluation
R-GCX016E-cbl-00826 Set Cargo Release Business Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Cargo Release Business Flag' is invoked, and assuming that release conditions have been evaluated and determined to be applicable, when the system confirms release status should be applied to cargo, the desired outcome is that the cargo release business flag is set to indicate cargo is released.
💻 Technical Criteria
Given Release conditions have been evaluated and determined to be applicable
When The system confirms release status should be applied to cargo
Then The cargo release business flag is set to indicate cargo is released
R-GCX016E-cbl-00828 Proceed Status Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Proceed Status Found?' is invoked, and assuming that proceed conditions have been evaluated for a cargo, when the system checks if proceed status should be applied, the desired outcome is that if proceed conditions are met, set in-bond proceed business flag; otherwise proceed to manual release evaluation.
💻 Technical Criteria
Given Proceed conditions have been evaluated for a cargo
When The system checks if proceed status should be applied
Then If proceed conditions are met, set in-bond proceed business flag; otherwise proceed to manual release evaluation
R-GCX016E-cbl-00829 Set In-Bond Proceed Business Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set In-Bond Proceed Business Flag' is invoked, and assuming that proceed conditions have been evaluated and determined to be applicable, when the system confirms proceed status should be applied to cargo, the desired outcome is that the in-bond proceed business flag is set to indicate cargo can proceed in-bond.
💻 Technical Criteria
Given Proceed conditions have been evaluated and determined to be applicable
When The system confirms proceed status should be applied to cargo
Then The in-bond proceed business flag is set to indicate cargo can proceed in-bond
R-GCX016E-cbl-00831 Manual Release Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Manual Release Found?' is invoked, and assuming that manual release conditions have been evaluated for a cargo, when the system checks if manual release status should be applied, the desired outcome is that if manual release conditions are met, set manual release business flag; otherwise continue to next entry.
💻 Technical Criteria
Given Manual release conditions have been evaluated for a cargo
When The system checks if manual release status should be applied
Then If manual release conditions are met, set manual release business flag; otherwise continue to next entry
R-GCX016E-cbl-00832 Set Manual Release Business Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Manual Release Business Flag' is invoked, and assuming that manual release conditions have been evaluated and determined to be applicable, when the system confirms manual release status should be applied to cargo, the desired outcome is that the manual release business flag is set to indicate cargo has been manually released.
💻 Technical Criteria
Given Manual release conditions have been evaluated and determined to be applicable
When The system confirms manual release status should be applied to cargo
Then The manual release business flag is set to indicate cargo has been manually released
R-GCX016E-cbl-00833 Set Final Status Flags
Process Rules
📊 Business Logic Narrative
When the process 'Set Final Status Flags' is invoked, and assuming that all status array entries have been processed and individual flags have been set, when the system completes individual status analysis, the desired outcome is that final cargo status flags are determined based on the combination of hold, release, proceed, and manual release flags.
💻 Technical Criteria
Given All status array entries have been processed and individual flags have been set
When The system completes individual status analysis
Then Final cargo status flags are determined based on the combination of hold, release, proceed, and manual release flags
R-GCX016E-cbl-00834 Analyze Complete S09A Status Arrays
Decision Rules
📊 Business Logic Narrative
When the process 'Analyze Complete S09A Status Arrays' is invoked, and assuming that a cargo has s09a status arrays containing disposition codes with associated flags and quantities, when the system processes the status arrays to evaluate cargo conditions, the desired outcome is that the system identifies hold status types, release conditions, proceed dispositions, arrival/export flags, and manual processing indicators for subsequent status determination.
💻 Technical Criteria
Given A cargo has S09A status arrays containing disposition codes with associated flags and quantities
When The system processes the status arrays to evaluate cargo conditions
Then The system identifies hold status types, release conditions, proceed dispositions, arrival/export flags, and manual processing indicators for subsequent status determination
R-GCX016E-cbl-00835 Border Hold Status
Decision Rules
📊 Business Logic Narrative
When the process 'Border Hold Status' is invoked, and assuming that a cargo has disposition codes in its status array, when the system finds disposition codes that indicate border hold conditions, the desired outcome is that the system sets the border hold flag to indicate cargo is held at border location.
💻 Technical Criteria
Given A cargo has disposition codes in its status array
When The system finds disposition codes that indicate border hold conditions
Then The system sets the border hold flag to indicate cargo is held at border location
R-GCX016E-cbl-00836 Destination Hold Status
Decision Rules
📊 Business Logic Narrative
When the process 'Destination Hold Status' is invoked, and assuming that a cargo has disposition codes in its status array, when the system finds disposition codes that indicate destination hold conditions, the desired outcome is that the system sets the destination hold flag to indicate cargo is held at destination location.
💻 Technical Criteria
Given A cargo has disposition codes in its status array
When The system finds disposition codes that indicate destination hold conditions
Then The system sets the destination hold flag to indicate cargo is held at destination location
R-GCX016E-cbl-00837 FDA Hold Status
Decision Rules
📊 Business Logic Narrative
When the process 'FDA Hold Status' is invoked, and assuming that a cargo has disposition codes in its status array, when the system finds disposition codes that indicate fda hold requirements, the desired outcome is that the system sets the fda hold flag to indicate cargo requires fda clearance.
💻 Technical Criteria
Given A cargo has disposition codes in its status array
When The system finds disposition codes that indicate FDA hold requirements
Then The system sets the FDA hold flag to indicate cargo requires FDA clearance
R-GCX016E-cbl-00838 Piece Count Hold Status
Decision Rules
📊 Business Logic Narrative
When the process 'Piece Count Hold Status' is invoked, and assuming that a cargo has disposition codes with associated release quantities in its status array, when the system compares released quantities against total cargo quantities, the desired outcome is that the system sets piece count hold flag if cargo has partial releases or quantity discrepancies.
💻 Technical Criteria
Given A cargo has disposition codes with associated release quantities in its status array
When The system compares released quantities against total cargo quantities
Then The system sets piece count hold flag if cargo has partial releases or quantity discrepancies
R-GCX016E-cbl-00839 Manual Release Processing
Decision Rules
📊 Business Logic Narrative
When the process 'Manual Release Processing' is invoked, and assuming that a cargo has disposition codes in its status array with manual processing indicators, when the system finds manual release disposition codes or manual processing flags, the desired outcome is that the system prioritizes manual release status and sets appropriate processing flags for manual intervention.
💻 Technical Criteria
Given A cargo has disposition codes in its status array with manual processing indicators
When The system finds manual release disposition codes or manual processing flags
Then The system prioritizes manual release status and sets appropriate processing flags for manual intervention
R-GCX016E-cbl-00840 Automatic Release Processing
Decision Rules
📊 Business Logic Narrative
When the process 'Automatic Release Processing' is invoked, and assuming that a cargo has disposition codes in its status array with automatic processing indicators, when the system finds automatic release disposition codes without hold conditions, the desired outcome is that the system sets automatic release processing flags and prepares cargo for automated release workflow.
💻 Technical Criteria
Given A cargo has disposition codes in its status array with automatic processing indicators
When The system finds automatic release disposition codes without hold conditions
Then The system sets automatic release processing flags and prepares cargo for automated release workflow
R-GCX016E-cbl-00841 Proceed Disposition Processing
Decision Rules
📊 Business Logic Narrative
When the process 'Proceed Disposition Processing' is invoked, and assuming that a cargo has proceed disposition codes in its status array, when the system processes proceed dispositions with associated location and timing information, the desired outcome is that the system sets proceed status flags and updates cargo movement authorization while maintaining compliance tracking.
💻 Technical Criteria
Given A cargo has proceed disposition codes in its status array
When The system processes proceed dispositions with associated location and timing information
Then The system sets proceed status flags and updates cargo movement authorization while maintaining compliance tracking
R-GCX016E-cbl-00842 Arrival Status Management
Process Rules
📊 Business Logic Narrative
When the process 'Arrival Status Management' is invoked, and assuming that a cargo has arrival disposition codes in its status array with location and date information, when the system processes arrival events and validates arrival conditions, the desired outcome is that the system updates arrival status flags, records arrival location and date, and triggers arrival-related processing workflows.
💻 Technical Criteria
Given A cargo has arrival disposition codes in its status array with location and date information
When The system processes arrival events and validates arrival conditions
Then The system updates arrival status flags, records arrival location and date, and triggers arrival-related processing workflows
R-GCX016E-cbl-00843 Export Status Management
Process Rules
📊 Business Logic Narrative
When the process 'Export Status Management' is invoked, and assuming that a cargo has export disposition codes in its status array with export requirements, when the system processes export events and validates export conditions, the desired outcome is that the system updates export status flags, clears destination requirements, and ensures export compliance processing.
💻 Technical Criteria
Given A cargo has export disposition codes in its status array with export requirements
When The system processes export events and validates export conditions
Then The system updates export status flags, clears destination requirements, and ensures export compliance processing
R-GCX016E-cbl-00844 Canadian Manifest Processing
Policy Rules
📊 Business Logic Narrative
When the process 'Canadian Manifest Processing' is invoked, and assuming that a cargo is associated with canadian manifests and has cross-border movement requirements, when the system processes canadian manifest disposition codes and cross-border conditions, the desired outcome is that the system applies canadian regulatory requirements, updates cross-border tracking, and ensures compliance with bilateral trade agreements.
💻 Technical Criteria
Given A cargo is associated with Canadian manifests and has cross-border movement requirements
When The system processes Canadian manifest disposition codes and cross-border conditions
Then The system applies Canadian regulatory requirements, updates cross-border tracking, and ensures compliance with bilateral trade agreements
R-GCX016E-cbl-00845 Hold vs Release Priority
Decision Rules
📊 Business Logic Narrative
When the process 'Hold vs Release Priority' is invoked, and assuming that a cargo has both hold and release disposition codes in its status array, when the system evaluates conflicting disposition codes with different priorities and timestamps, the desired outcome is that the system applies business priority rules where holds generally override releases unless specific release conditions supersede hold requirements.
💻 Technical Criteria
Given A cargo has both hold and release disposition codes in its status array
When The system evaluates conflicting disposition codes with different priorities and timestamps
Then The system applies business priority rules where holds generally override releases unless specific release conditions supersede hold requirements
R-GCX016E-cbl-00846 Proceed vs Hold Priority
Decision Rules
📊 Business Logic Narrative
When the process 'Proceed vs Hold Priority' is invoked, and assuming that a cargo has both proceed and hold disposition codes in its status array, when the system evaluates conflicting disposition codes with different business priorities, the desired outcome is that the system applies priority rules where active holds override proceed dispositions unless proceed has regulatory precedence or proper release authorization.
💻 Technical Criteria
Given A cargo has both proceed and hold disposition codes in its status array
When The system evaluates conflicting disposition codes with different business priorities
Then The system applies priority rules where active holds override proceed dispositions unless proceed has regulatory precedence or proper release authorization
R-GCX016E-cbl-00847 Status Information Codes
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Status Information Codes', assuming that a cargo has informational disposition codes in its status array, when the system processes status information codes that do not affect cargo movement, the desired outcome is that the system records informational status updates for tracking and reporting purposes without altering cargo processing workflow or hold/release states.
💻 Technical Criteria
EXCLUDING A cargo has informational disposition codes in its status array
When The system processes status information codes that do not affect cargo movement
Then The system records informational status updates for tracking and reporting purposes without altering cargo processing workflow or hold/release states
R-GCX016E-cbl-00848 Set Final Hold Status
Decision Rules
📊 Business Logic Narrative
When the process 'Set Final Hold Status' is invoked, and assuming that a cargo has multiple hold conditions identified from disposition code analysis, when the system applies hold priority rules considering fda holds, border holds, destination holds, and piece count holds, the desired outcome is that the system sets the highest priority hold status (fda > border > destination > piece count) and updates cargo status accordingly.
💻 Technical Criteria
Given A cargo has multiple hold conditions identified from disposition code analysis
When The system applies hold priority rules considering FDA holds, border holds, destination holds, and piece count holds
Then The system sets the highest priority hold status (FDA > Border > Destination > Piece Count) and updates cargo status accordingly
R-GCX016E-cbl-00849 Set Final Release Status
Decision Rules
📊 Business Logic Narrative
When the process 'Set Final Release Status' is invoked, and assuming that a cargo has release disposition codes and no overriding hold conditions, when the system validates release quantities match cargo quantities and all release requirements are satisfied, the desired outcome is that the system sets released status, updates release quantities, and enables cargo for movement processing.
💻 Technical Criteria
Given A cargo has release disposition codes and no overriding hold conditions
When The system validates release quantities match cargo quantities and all release requirements are satisfied
Then The system sets released status, updates release quantities, and enables cargo for movement processing
R-GCX016E-cbl-00850 Set Final Proceed Status
Decision Rules
📊 Business Logic Narrative
When the process 'Set Final Proceed Status' is invoked, and assuming that a cargo has proceed disposition codes and meets movement authorization requirements, when the system validates proceed conditions and ensures no conflicting holds prevent movement, the desired outcome is that the system sets proceed status, authorizes cargo movement, and maintains compliance tracking for in-transit cargo.
💻 Technical Criteria
Given A cargo has proceed disposition codes and meets movement authorization requirements
When The system validates proceed conditions and ensures no conflicting holds prevent movement
Then The system sets proceed status, authorizes cargo movement, and maintains compliance tracking for in-transit cargo
R-GCX016E-cbl-00851 Set Final Arrival Status
Process Rules
📊 Business Logic Narrative
When the process 'Set Final Arrival Status' is invoked, and assuming that a cargo has arrival disposition codes with validated destination and arrival date information, when the system confirms cargo arrival at destination location and completes arrival validation, the desired outcome is that the system sets arrival status, records final arrival date and location, and triggers destination processing workflows.
💻 Technical Criteria
Given A cargo has arrival disposition codes with validated destination and arrival date information
When The system confirms cargo arrival at destination location and completes arrival validation
Then The system sets arrival status, records final arrival date and location, and triggers destination processing workflows
R-GCX016E-cbl-00852 Set Final Export Status
Policy Rules
📊 Business Logic Narrative
When the process 'Set Final Export Status' is invoked, and assuming that a cargo has export disposition codes and meets all export regulatory requirements, when the system validates export documentation and compliance with international trade regulations, the desired outcome is that the system sets export status, clears domestic processing requirements, and enables international shipment processing.
💻 Technical Criteria
Given A cargo has export disposition codes and meets all export regulatory requirements
When The system validates export documentation and compliance with international trade regulations
Then The system sets export status, clears domestic processing requirements, and enables international shipment processing
R-GCX016E-cbl-00853 Update Cargo Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status Flags' is invoked, and assuming that the system has determined final cargo status through disposition code evaluation, when the system updates cargo records with new status flags and processing indicators, the desired outcome is that the system commits status changes to cargo database, updates status timestamps, and triggers downstream processing notifications.
💻 Technical Criteria
Given The system has determined final cargo status through disposition code evaluation
When The system updates cargo records with new status flags and processing indicators
Then The system commits status changes to cargo database, updates status timestamps, and triggers downstream processing notifications
R-GCX016E-cbl-03012 Border Hold Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Border Hold Present?' is invoked, and assuming that a cargo record with status array containing disposition codes, when the system analyzes the cargo status for border hold conditions, the desired outcome is that the system identifies if border hold is present and sets appropriate processing flags.
💻 Technical Criteria
Given A cargo record with status array containing disposition codes
When The system analyzes the cargo status for border hold conditions
Then The system identifies if border hold is present and sets appropriate processing flags
R-GCX016E-cbl-03013 Destination Hold Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Destination Hold Present?' is invoked, and assuming that a cargo record with status array and destination information, when the system checks for destination-specific hold conditions, the desired outcome is that the system determines if destination hold is active and updates processing flags accordingly.
💻 Technical Criteria
Given A cargo record with status array and destination information
When The system checks for destination-specific hold conditions
Then The system determines if destination hold is active and updates processing flags accordingly
R-GCX016E-cbl-03014 FDA Hold Present?
Policy Rules
📊 Business Logic Narrative
When the process 'FDA Hold Present?' is invoked, and assuming that a cargo record with regulatory status information, when the system checks for fda hold conditions in the status array, the desired outcome is that the system identifies fda hold presence and sets regulatory compliance flags.
💻 Technical Criteria
Given A cargo record with regulatory status information
When The system checks for FDA hold conditions in the status array
Then The system identifies FDA hold presence and sets regulatory compliance flags
R-GCX016E-cbl-03015 Piece Count Hold Present?
Validation Rules
📊 Business Logic Narrative
When the process 'Piece Count Hold Present?' is invoked, and assuming that a cargo record with quantity information and release data, when the system compares released quantities against total cargo quantities, the desired outcome is that the system determines if piece count hold exists and updates quantity validation flags.
💻 Technical Criteria
Given A cargo record with quantity information and release data
When The system compares released quantities against total cargo quantities
Then The system determines if piece count hold exists and updates quantity validation flags
R-GCX016E-cbl-03016 Manual Release Present?
Authorization Rules
📊 Business Logic Narrative
When the process 'Manual Release Present?' is invoked, and assuming that a cargo record with disposition codes and release information, when the system evaluates manual release status in the disposition code array, the desired outcome is that the system identifies manual release presence and sets override processing flags.
💻 Technical Criteria
Given A cargo record with disposition codes and release information
When The system evaluates manual release status in the disposition code array
Then The system identifies manual release presence and sets override processing flags
R-GCX016E-cbl-03017 Proceed Code Present?
Authorization Rules
📊 Business Logic Narrative
When the process 'Proceed Code Present?' is invoked, and assuming that a cargo record with disposition codes and processing status, when the system checks for proceed authorization in the status array, the desired outcome is that the system determines proceed code presence and enables movement authorization.
💻 Technical Criteria
Given A cargo record with disposition codes and processing status
When The system checks for proceed authorization in the status array
Then The system determines proceed code presence and enables movement authorization
R-GCX016E-cbl-03018 Auto Release Available?
Decision Rules
📊 Business Logic Narrative
When the process 'Auto Release Available?' is invoked, and assuming that a cargo record with status information and release criteria, when the system evaluates automatic release eligibility conditions, the desired outcome is that the system determines auto release availability and sets automated processing flags.
💻 Technical Criteria
Given A cargo record with status information and release criteria
When The system evaluates automatic release eligibility conditions
Then The system determines auto release availability and sets automated processing flags
R-GCX016E-cbl-03019 In-Bond Entry?
Definitional Rules
📊 Business Logic Narrative
When the process 'In-Bond Entry?' is invoked, and assuming that a cargo record with entry type and customs information, when the system evaluates entry types 61, 62, 63, or 69 for in-bond classification, the desired outcome is that the system sets in-bond processing flags and enables customs movement tracking.
💻 Technical Criteria
Given A cargo record with entry type and customs information
When The system evaluates entry types 61, 62, 63, or 69 for in-bond classification
Then The system sets in-bond processing flags and enables customs movement tracking
R-GCX016E-cbl-03020 Arrival Status Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Arrival Status Valid?' is invoked, and assuming that a cargo record with arrival information and location data, when the system validates arrival status against business rules and location constraints, the desired outcome is that the system confirms arrival status validity and enables arrival processing workflows.
💻 Technical Criteria
Given A cargo record with arrival information and location data
When The system validates arrival status against business rules and location constraints
Then The system confirms arrival status validity and enables arrival processing workflows
R-GCX016E-cbl-03021 Export Status Valid?
Policy Rules
📊 Business Logic Narrative
When the process 'Export Status Valid?' is invoked, and assuming that a cargo record with export information and regulatory compliance data, when the system validates export status against customs regulations and business rules, the desired outcome is that the system confirms export status validity and enables export processing workflows.
💻 Technical Criteria
Given A cargo record with export information and regulatory compliance data
When The system validates export status against customs regulations and business rules
Then The system confirms export status validity and enables export processing workflows
R-GCX016E-cbl-03022 Hold Takes Precedence?
Process Rules
📊 Business Logic Narrative
When the process 'Hold Takes Precedence?' is invoked, and assuming that a cargo record with multiple conflicting status conditions including holds, releases, and proceed codes, when the system evaluates status priority hierarchy with holds having highest precedence, the desired outcome is that the system determines final status based on hold precedence rules and sets appropriate processing flags.
💻 Technical Criteria
Given A cargo record with multiple conflicting status conditions including holds, releases, and proceed codes
When The system evaluates status priority hierarchy with holds having highest precedence
Then The system determines final status based on hold precedence rules and sets appropriate processing flags
R-GCX016E-cbl-03023 Set Final Status: HOLD
Action Rules
📊 Business Logic Narrative
When the process 'Set Final Status: HOLD' is invoked, and assuming that a cargo record where hold conditions have been determined to take precedence, when the system applies final status assignment logic, the desired outcome is that the system sets cargo status to hold and updates all related processing flags and notifications.
💻 Technical Criteria
Given A cargo record where hold conditions have been determined to take precedence
When The system applies final status assignment logic
Then The system sets cargo status to HOLD and updates all related processing flags and notifications
R-GCX016E-cbl-03024 Set Final Status: RELEASE
Action Rules
📊 Business Logic Narrative
When the process 'Set Final Status: RELEASE' is invoked, and assuming that a cargo record where release conditions take precedence and no overriding holds exist, when the system applies final status assignment logic, the desired outcome is that the system sets cargo status to release and enables cargo movement and delivery processing.
💻 Technical Criteria
Given A cargo record where release conditions take precedence and no overriding holds exist
When The system applies final status assignment logic
Then The system sets cargo status to RELEASE and enables cargo movement and delivery processing
R-GCX016E-cbl-03025 Set Final Status: PROCEED
Action Rules
📊 Business Logic Narrative
When the process 'Set Final Status: PROCEED' is invoked, and assuming that a cargo record where proceed authorization takes precedence and no blocking conditions exist, when the system applies final status assignment logic, the desired outcome is that the system sets cargo status to proceed and enables next stage processing workflows.
💻 Technical Criteria
Given A cargo record where proceed authorization takes precedence and no blocking conditions exist
When The system applies final status assignment logic
Then The system sets cargo status to PROCEED and enables next stage processing workflows
R-GCX016E-cbl-03026 Set Final Status: ARRIVED
Action Rules
📊 Business Logic Narrative
When the process 'Set Final Status: ARRIVED' is invoked, and assuming that a cargo record where arrival status takes precedence and arrival validation is successful, when the system applies final status assignment logic, the desired outcome is that the system sets cargo status to arrived and triggers arrival notification and processing workflows.
💻 Technical Criteria
Given A cargo record where arrival status takes precedence and arrival validation is successful
When The system applies final status assignment logic
Then The system sets cargo status to ARRIVED and triggers arrival notification and processing workflows
R-GCX016E-cbl-03027 Set Final Status: EXPORTED
Action Rules
📊 Business Logic Narrative
When the process 'Set Final Status: EXPORTED' is invoked, and assuming that a cargo record where export status takes precedence and export validation is successful, when the system applies final status assignment logic, the desired outcome is that the system sets cargo status to exported and triggers export documentation and compliance workflows.
💻 Technical Criteria
Given A cargo record where export status takes precedence and export validation is successful
When The system applies final status assignment logic
Then The system sets cargo status to EXPORTED and triggers export documentation and compliance workflows
R-GCX016E-cbl-03252 Retrieve Complete S09A Status Array
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Complete S09A Status Array' is invoked, and assuming that a cargo record exists with associated status segments, when the system needs to determine final cargo status, the desired outcome is that the complete s09a status array containing all disposition codes and status information is retrieved and made available for processing.
💻 Technical Criteria
Given A cargo record exists with associated status segments
When The system needs to determine final cargo status
Then The complete S09A status array containing all disposition codes and status information is retrieved and made available for processing
R-GCX016E-cbl-03253 Initialize Priority Flags
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Priority Flags' is invoked, and assuming that the system is about to evaluate cargo status priorities, when priority evaluation process begins, the desired outcome is that all priority flags for hold, release, proceed, arrival, and export conditions are set to initial false state.
💻 Technical Criteria
Given The system is about to evaluate cargo status priorities
When Priority evaluation process begins
Then All priority flags for hold, release, proceed, arrival, and export conditions are set to initial false state
R-GCX016E-cbl-03254 Hold Conditions Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Hold Conditions Present?' is invoked, and assuming that a cargo status array contains disposition codes, when the system checks for hold conditions including border holds, destination holds, or fda holds, the desired outcome is that the system identifies if any hold disposition codes are present and sets hold priority flag accordingly.
💻 Technical Criteria
Given A cargo status array contains disposition codes
When The system checks for hold conditions including border holds, destination holds, or FDA holds
Then The system identifies if any hold disposition codes are present and sets hold priority flag accordingly
R-GCX016E-cbl-03255 Set Hold Priority Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Hold Priority Flag' is invoked, and assuming that hold conditions have been detected in the cargo status array, when the system processes the hold condition detection result, the desired outcome is that the hold priority flag is set to true to indicate hold conditions take precedence in status determination.
💻 Technical Criteria
Given Hold conditions have been detected in the cargo status array
When The system processes the hold condition detection result
Then The hold priority flag is set to true to indicate hold conditions take precedence in status determination
R-GCX016E-cbl-03256 Release Conditions Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Release Conditions Present?' is invoked, and assuming that a cargo status array contains disposition codes, when the system checks for release conditions including manual release or automatic release codes, the desired outcome is that the system identifies if any release disposition codes are present and sets release priority flag accordingly.
💻 Technical Criteria
Given A cargo status array contains disposition codes
When The system checks for release conditions including manual release or automatic release codes
Then The system identifies if any release disposition codes are present and sets release priority flag accordingly
R-GCX016E-cbl-03257 Set Release Priority Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Release Priority Flag' is invoked, and assuming that release conditions have been detected in the cargo status array, when the system processes the release condition detection result, the desired outcome is that the release priority flag is set to true to indicate release conditions are present for priority evaluation.
💻 Technical Criteria
Given Release conditions have been detected in the cargo status array
When The system processes the release condition detection result
Then The release priority flag is set to true to indicate release conditions are present for priority evaluation
R-GCX016E-cbl-03258 Proceed Conditions Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Proceed Conditions Present?' is invoked, and assuming that a cargo status array contains disposition codes, when the system checks for proceed disposition codes that allow cargo movement, the desired outcome is that the system identifies if any proceed disposition codes are present and sets proceed priority flag accordingly.
💻 Technical Criteria
Given A cargo status array contains disposition codes
When The system checks for proceed disposition codes that allow cargo movement
Then The system identifies if any proceed disposition codes are present and sets proceed priority flag accordingly
R-GCX016E-cbl-03259 Set Proceed Priority Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Proceed Priority Flag' is invoked, and assuming that proceed conditions have been detected in the cargo status array, when the system processes the proceed condition detection result, the desired outcome is that the proceed priority flag is set to true to indicate proceed conditions are present for priority evaluation.
💻 Technical Criteria
Given Proceed conditions have been detected in the cargo status array
When The system processes the proceed condition detection result
Then The proceed priority flag is set to true to indicate proceed conditions are present for priority evaluation
R-GCX016E-cbl-03260 Arrival Conditions Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Arrival Conditions Present?' is invoked, and assuming that a cargo status array contains disposition codes, when the system checks for arrival disposition codes indicating cargo has arrived at destination, the desired outcome is that the system identifies if any arrival disposition codes are present and sets arrival priority flag accordingly.
💻 Technical Criteria
Given A cargo status array contains disposition codes
When The system checks for arrival disposition codes indicating cargo has arrived at destination
Then The system identifies if any arrival disposition codes are present and sets arrival priority flag accordingly
R-GCX016E-cbl-03261 Set Arrival Priority Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Arrival Priority Flag' is invoked, and assuming that arrival conditions have been detected in the cargo status array, when the system processes the arrival condition detection result, the desired outcome is that the arrival priority flag is set to true to indicate arrival conditions are present for priority evaluation.
💻 Technical Criteria
Given Arrival conditions have been detected in the cargo status array
When The system processes the arrival condition detection result
Then The arrival priority flag is set to true to indicate arrival conditions are present for priority evaluation
R-GCX016E-cbl-03262 Export Conditions Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Export Conditions Present?' is invoked, and assuming that a cargo status array contains disposition codes, when the system checks for export disposition codes indicating cargo is being exported, the desired outcome is that the system identifies if any export disposition codes are present and sets export priority flag accordingly.
💻 Technical Criteria
Given A cargo status array contains disposition codes
When The system checks for export disposition codes indicating cargo is being exported
Then The system identifies if any export disposition codes are present and sets export priority flag accordingly
R-GCX016E-cbl-03263 Set Export Priority Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Export Priority Flag' is invoked, and assuming that export conditions have been detected in the cargo status array, when the system processes the export condition detection result, the desired outcome is that the export priority flag is set to true to indicate export conditions are present for priority evaluation.
💻 Technical Criteria
Given Export conditions have been detected in the cargo status array
When The system processes the export condition detection result
Then The export priority flag is set to true to indicate export conditions are present for priority evaluation
R-GCX016E-cbl-03264 Apply Regulatory Hierarchy Rules
Policy Rules
📊 Business Logic Narrative
When the process 'Apply Regulatory Hierarchy Rules' is invoked, and assuming that multiple status condition flags are set for a cargo, when the system needs to determine the final authoritative status, the desired outcome is that regulatory hierarchy rules are applied to establish precedence order among competing status conditions.
💻 Technical Criteria
Given Multiple status condition flags are set for a cargo
When The system needs to determine the final authoritative status
Then Regulatory hierarchy rules are applied to establish precedence order among competing status conditions
R-GCX016E-cbl-03266 Final Status: HELD
Action Rules
📊 Business Logic Narrative
When the process 'Final Status: HELD' is invoked, and assuming that hold conditions have been determined to take precedence, when the system assigns the final cargo status, the desired outcome is that the cargo status is set to held and all other competing status conditions are overridden.
💻 Technical Criteria
Given Hold conditions have been determined to take precedence
When The system assigns the final cargo status
Then The cargo status is set to HELD and all other competing status conditions are overridden
R-GCX016E-cbl-03268 Final Status: RELEASED
Action Rules
📊 Business Logic Narrative
When the process 'Final Status: RELEASED' is invoked, and assuming that release conditions have been determined to override hold conditions, when the system assigns the final cargo status, the desired outcome is that the cargo status is set to released and hold conditions are overridden by authorized release.
💻 Technical Criteria
Given Release conditions have been determined to override hold conditions
When The system assigns the final cargo status
Then The cargo status is set to RELEASED and hold conditions are overridden by authorized release
R-GCX016E-cbl-03270 Final Status: PROCEED
Action Rules
📊 Business Logic Narrative
When the process 'Final Status: PROCEED' is invoked, and assuming that proceed conditions have been validated as legitimate and applicable, when the system assigns the final cargo status, the desired outcome is that the cargo status is set to proceed allowing cargo movement according to disposition instructions.
💻 Technical Criteria
Given Proceed conditions have been validated as legitimate and applicable
When The system assigns the final cargo status
Then The cargo status is set to PROCEED allowing cargo movement according to disposition instructions
R-GCX016E-cbl-03272 Final Status: ARRIVED
Action Rules
📊 Business Logic Narrative
When the process 'Final Status: ARRIVED' is invoked, and assuming that arrival conditions have been validated as legitimate and applicable, when the system assigns the final cargo status, the desired outcome is that the cargo status is set to arrived indicating successful cargo arrival at destination.
💻 Technical Criteria
Given Arrival conditions have been validated as legitimate and applicable
When The system assigns the final cargo status
Then The cargo status is set to ARRIVED indicating successful cargo arrival at destination
R-GCX016E-cbl-03274 Final Status: EXPORTED
Action Rules
📊 Business Logic Narrative
When the process 'Final Status: EXPORTED' is invoked, and assuming that export conditions have been validated as legitimate and applicable, when the system assigns the final cargo status, the desired outcome is that the cargo status is set to exported indicating cargo has been processed for export.
💻 Technical Criteria
Given Export conditions have been validated as legitimate and applicable
When The system assigns the final cargo status
Then The cargo status is set to EXPORTED indicating cargo has been processed for export
R-GCX016E-cbl-03275 Final Status: DEFAULT
Action Rules
📊 Business Logic Narrative
When the process 'Final Status: DEFAULT' is invoked, and assuming that no specific status conditions (hold, release, proceed, arrival, export) are valid or applicable, when the system assigns the final cargo status, the desired outcome is that the cargo status is set to a default value indicating standard processing state.
💻 Technical Criteria
Given No specific status conditions (hold, release, proceed, arrival, export) are valid or applicable
When The system assigns the final cargo status
Then The cargo status is set to a default value indicating standard processing state
R-GCX016E-cbl-03276 Return Final Cargo Status
Process Rules
📊 Business Logic Narrative
When the process 'Return Final Cargo Status' is invoked, and assuming that a final cargo status has been determined through priority rule application, when the status determination process completes, the desired outcome is that the final cargo status is returned to the calling process for further business operations.
💻 Technical Criteria
Given A final cargo status has been determined through priority rule application
When The status determination process completes
Then The final cargo status is returned to the calling process for further business operations
R-GCX016E-cbl-03397 Retrieve Current Status Array
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Status Array' is invoked, and assuming that a cargo record exists with status information, when regulatory hierarchy processing is initiated, the desired outcome is that the system retrieves the current s09 status array containing all existing disposition codes and their details.
💻 Technical Criteria
Given A cargo record exists with status information
When Regulatory hierarchy processing is initiated
Then The system retrieves the current S09 status array containing all existing disposition codes and their details
R-GCX016E-cbl-03403 Apply Status Info Code Hierarchy
Policy Rules
📊 Business Logic Narrative
When the process 'Apply Status Info Code Hierarchy' is invoked, and assuming that a disposition code is classified as status info type, when regulatory hierarchy processing is applied, the desired outcome is that the system applies informational code precedence rules that do not affect cargo release status but provide tracking information.
💻 Technical Criteria
Given A disposition code is classified as Status Info type
When Regulatory hierarchy processing is applied
Then The system applies informational code precedence rules that do not affect cargo release status but provide tracking information
R-GCX016E-cbl-03516 Retrieve Current Status Array
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Status Array' is invoked, and assuming that a cargo record exists with disposition codes in the status array, when the system needs to apply regulatory precedence rules for a new disposition code, the desired outcome is that the system retrieves all current disposition codes from the s09 status segments.
💻 Technical Criteria
Given A cargo record exists with disposition codes in the status array
When The system needs to apply regulatory precedence rules for a new disposition code
Then The system retrieves all current disposition codes from the S09 status segments
R-GCX016E-cbl-03517 Identify New Disposition Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Identify New Disposition Code' is invoked, and assuming that a new disposition code is being added to a cargo's status array, when the system processes the disposition code, the desired outcome is that the system identifies the specific disposition code and its regulatory classification.
💻 Technical Criteria
Given A new disposition code is being added to a cargo's status array
When The system processes the disposition code
Then The system identifies the specific disposition code and its regulatory classification
R-GCX016E-cbl-03519 Apply Customs Regulatory Hierarchy
Policy Rules
📊 Business Logic Narrative
When the process 'Apply Customs Regulatory Hierarchy' is invoked, and assuming that conflicting disposition codes exist in the cargo status array, when the system applies customs regulatory hierarchy rules, the desired outcome is that the system determines the precedence order based on regulatory requirements and customs policies.
💻 Technical Criteria
Given Conflicting disposition codes exist in the cargo status array
When The system applies customs regulatory hierarchy rules
Then The system determines the precedence order based on regulatory requirements and customs policies
R-GCX016E-cbl-03525 Update Status Array
Action Rules
📊 Business Logic Narrative
When the process 'Update Status Array' is invoked, and assuming that precedence rules have been successfully applied and validated, when the system updates the status array, the desired outcome is that the system commits the precedence-adjusted disposition codes to the cargo's s09 status segments.
💻 Technical Criteria
Given Precedence rules have been successfully applied and validated
When The system updates the status array
Then The system commits the precedence-adjusted disposition codes to the cargo's S09 status segments
R-GCX016E-cbl-00854 Extract Equipment ID from US Cargo
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment ID from US Cargo' is invoked, and assuming that a us cargo record exists with equipment information, when canadian manifest processing is initiated, the desired outcome is that equipment id is extracted and formatted for canadian cargo database search.
💻 Technical Criteria
Given A US cargo record exists with equipment information
When Canadian manifest processing is initiated
Then Equipment ID is extracted and formatted for Canadian cargo database search
R-GCX016E-cbl-00855 Search Canadian Cargo Database
Action Rules
📊 Business Logic Narrative
When the process 'Search Canadian Cargo Database' is invoked, and assuming that equipment id has been extracted from us cargo, when canadian cargo database search is performed, the desired outcome is that system searches gccc-cargo-root database for matching canadian cargo records by equipment id.
💻 Technical Criteria
Given Equipment ID has been extracted from US cargo
When Canadian cargo database search is performed
Then System searches GCCC-CARGO-ROOT database for matching Canadian cargo records by equipment ID
R-GCX016E-cbl-00856 Canadian Cargo Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Canadian Cargo Found?' is invoked, and assuming that canadian cargo database search has been performed, when search results are evaluated, the desired outcome is that system determines if canadian cargo record exists and routes processing accordingly.
💻 Technical Criteria
Given Canadian cargo database search has been performed
When Search results are evaluated
Then System determines if Canadian cargo record exists and routes processing accordingly
R-GCX016E-cbl-00857 Validate Canadian Cargo Status
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Canadian Cargo Status' is invoked, and assuming that canadian cargo record has been found, when cargo status is evaluated, the desired outcome is that system reads and validates the canadian cargo status from gccc database.
💻 Technical Criteria
Given Canadian cargo record has been found
When Cargo status is evaluated
Then System reads and validates the Canadian cargo status from GCCC database
R-GCX016E-cbl-00858 Status Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Status Valid?' is invoked, and assuming that canadian cargo status has been retrieved, when status validity is checked, the desired outcome is that system excludes cargos with deleted status or new bond created status and allows valid statuses to proceed.
💻 Technical Criteria
Given Canadian cargo status has been retrieved
When Status validity is checked
Then System excludes cargos with deleted status or new bond created status and allows valid statuses to proceed
R-GCX016E-cbl-00859 Create Cross-Border Audit Trail
Policy Rules
📊 Business Logic Narrative
When the process 'Create Cross-Border Audit Trail' is invoked, and assuming that canadian cargo has valid status for processing, when cross-border audit trail creation is initiated, the desired outcome is that system creates audit record linking us and canadian manifest information.
💻 Technical Criteria
Given Canadian cargo has valid status for processing
When Cross-border audit trail creation is initiated
Then System creates audit record linking US and Canadian manifest information
R-GCX016E-cbl-00860 Match Equipment IDs Between Systems
Process Rules
📊 Business Logic Narrative
When the process 'Match Equipment IDs Between Systems' is invoked, and assuming that valid canadian cargo has been found and audit trail created, when equipment id matching is performed, the desired outcome is that system matches car id number index between us and canadian cargo records.
💻 Technical Criteria
Given Valid Canadian cargo has been found and audit trail created
When Equipment ID matching is performed
Then System matches car ID number index between US and Canadian cargo records
R-GCX016E-cbl-00861 Update Cargo Processing Status
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo Processing Status' is invoked, and assuming that equipment ids have been successfully matched between systems, when status update is performed, the desired outcome is that system updates cargo processing status to indicate canadian manifest match completion.
💻 Technical Criteria
Given Equipment IDs have been successfully matched between systems
When Status update is performed
Then System updates cargo processing status to indicate Canadian manifest match completion
R-GCX016E-cbl-00863 No Canadian Match Found
Process Rules
📊 Business Logic Narrative
When the process 'No Canadian Match Found' is invoked, and assuming that canadian cargo database search has been performed, when no matching canadian cargo is found, the desired outcome is that system processes the no match condition and continues with standard processing.
💻 Technical Criteria
Given Canadian cargo database search has been performed
When No matching Canadian cargo is found
Then System processes the no match condition and continues with standard processing
R-GCX016E-cbl-00864 Log No Match Status
Process Rules
📊 Business Logic Narrative
When the process 'Log No Match Status' is invoked, and assuming that either no canadian cargo was found or canadian cargo has invalid status, when no match logging is performed, the desired outcome is that system logs the no match status with appropriate reason code.
💻 Technical Criteria
Given Either no Canadian cargo was found or Canadian cargo has invalid status
When No match logging is performed
Then System logs the no match status with appropriate reason code
R-GCX016E-cbl-00865 Save Current Cargo Status
Process Rules
📊 Business Logic Narrative
When the process 'Save Current Cargo Status' is invoked, and assuming that a cargo record exists with current status information, when the system initiates cargo status processing, the desired outcome is that the current cargo status is saved to a backup location for potential restoration.
💻 Technical Criteria
Given A cargo record exists with current status information
When The system initiates cargo status processing
Then The current cargo status is saved to a backup location for potential restoration
R-GCX016E-cbl-00866 Store Previous Status Information
Process Rules
📊 Business Logic Narrative
When the process 'Store Previous Status Information' is invoked, and assuming that cargo status information exists in the system, when status preservation process is executed, the desired outcome is that previous status information including codes, quantities, and dates is stored in designated storage areas.
💻 Technical Criteria
Given Cargo status information exists in the system
When Status preservation process is executed
Then Previous status information including codes, quantities, and dates is stored in designated storage areas
R-GCX016E-cbl-00867 Create Audit Trail Entry
Policy Rules
📊 Business Logic Narrative
When the process 'Create Audit Trail Entry' is invoked, and assuming that cargo status is being modified, when an audit trail entry is required, the desired outcome is that a complete audit record is created with timestamp, user information, and status change details.
💻 Technical Criteria
Given Cargo status is being modified
When An audit trail entry is required
Then A complete audit record is created with timestamp, user information, and status change details
R-GCX016E-cbl-00868 Process Status Updates
Process Rules
📊 Business Logic Narrative
When the process 'Process Status Updates' is invoked, and assuming that cargo status updates are pending, when status processing is initiated, the desired outcome is that all status updates are processed according to disposition code rules and status hierarchy.
💻 Technical Criteria
Given Cargo status updates are pending
When Status processing is initiated
Then All status updates are processed according to disposition code rules and status hierarchy
R-GCX016E-cbl-00869 Update Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Update Successful?' is invoked, and assuming that cargo status updates have been processed, when the system evaluates update completion, the desired outcome is that the system determines if updates were successful based on validation criteria and error conditions.
💻 Technical Criteria
Given Cargo status updates have been processed
When The system evaluates update completion
Then The system determines if updates were successful based on validation criteria and error conditions
R-GCX016E-cbl-00870 Commit New Status
Process Rules
📊 Business Logic Narrative
When the process 'Commit New Status' is invoked, and assuming that cargo status updates have been validated as successful, when the commit process is executed, the desired outcome is that the new cargo status is permanently saved and becomes the current active status.
💻 Technical Criteria
Given Cargo status updates have been validated as successful
When The commit process is executed
Then The new cargo status is permanently saved and becomes the current active status
R-GCX016E-cbl-00871 Restore Previous Status
Process Rules
📊 Business Logic Narrative
When the process 'Restore Previous Status' is invoked, and assuming that cargo status updates have failed validation, when status restoration is required, the desired outcome is that the cargo status is restored to its previous state using saved backup information.
💻 Technical Criteria
Given Cargo status updates have failed validation
When Status restoration is required
Then The cargo status is restored to its previous state using saved backup information
R-GCX016E-cbl-00872 Log Restoration Action
Policy Rules
📊 Business Logic Narrative
When the process 'Log Restoration Action' is invoked, and assuming that a cargo status restoration has occurred, when logging is performed, the desired outcome is that the restoration action is logged with details about the reason and previous status information.
💻 Technical Criteria
Given A cargo status restoration has occurred
When Logging is performed
Then The restoration action is logged with details about the reason and previous status information
R-GCX016E-cbl-00873 Enable Status Comparison
Process Rules
📊 Business Logic Narrative
When the process 'Enable Status Comparison' is invoked, and assuming that cargo status has been successfully updated, when status comparison is requested, the desired outcome is that the system provides capability to compare current status with previous status information.
💻 Technical Criteria
Given Cargo status has been successfully updated
When Status comparison is requested
Then The system provides capability to compare current status with previous status information
R-GCX016E-cbl-00874 Maintain Data Integrity
Validation Rules
📊 Business Logic Narrative
When the process 'Maintain Data Integrity' is invoked, and assuming that cargo status preservation process is active, when data integrity checks are performed, the desired outcome is that all cargo data remains consistent and valid throughout the preservation process.
💻 Technical Criteria
Given Cargo status preservation process is active
When Data integrity checks are performed
Then All cargo data remains consistent and valid throughout the preservation process
R-GCX016E-cbl-00875 Cancel Release Processing Triggered
Action Rules
📊 Business Logic Narrative
When the process 'Cancel Release Processing Triggered' is invoked, and assuming that a cargo disposition code indicates release cancellation, when the system processes the cancellation disposition code, the desired outcome is that cancel release processing workflow is initiated.
💻 Technical Criteria
Given A cargo disposition code indicates release cancellation
When The system processes the cancellation disposition code
Then Cancel release processing workflow is initiated
R-GCX016E-cbl-00876 Analyze Current Cargo Status
Process Rules
📊 Business Logic Narrative
When the process 'Analyze Current Cargo Status' is invoked, and assuming that a cargo record exists with status information in s09a arrays, when cancel release processing begins, the desired outcome is that the system reads and analyzes current cargo status from status arrays.
💻 Technical Criteria
Given A cargo record exists with status information in S09A arrays
When Cancel release processing begins
Then The system reads and analyzes current cargo status from status arrays
R-GCX016E-cbl-00877 Compare Previous Release Status
Decision Rules
📊 Business Logic Narrative
When the process 'Compare Previous Release Status' is invoked, and assuming that current cargo status is available and previous status exists in audit records, when status comparison is performed, the desired outcome is that the system identifies differences between current and previous release status.
💻 Technical Criteria
Given Current cargo status is available and previous status exists in audit records
When Status comparison is performed
Then The system identifies differences between current and previous release status
R-GCX016E-cbl-00878 Was Cargo Previously Released?
Validation Rules
📊 Business Logic Narrative
When the process 'Was Cargo Previously Released?' is invoked, and assuming that cargo status history is available for comparison, when the system checks previous release status, the desired outcome is that if cargo was previously released, proceed with cancellation processing, otherwise skip processing.
💻 Technical Criteria
Given Cargo status history is available for comparison
When The system checks previous release status
Then If cargo was previously released, proceed with cancellation processing, otherwise skip processing
R-GCX016E-cbl-00879 Detect Release Cancellation
Decision Rules
📊 Business Logic Narrative
When the process 'Detect Release Cancellation' is invoked, and assuming that cargo was previously in released status, when current status indicates release cancellation, the desired outcome is that the system detects and confirms release cancellation event.
💻 Technical Criteria
Given Cargo was previously in released status
When Current status indicates release cancellation
Then The system detects and confirms release cancellation event
R-GCX016E-cbl-00884 Add Disposition Code Information
Process Rules
📊 Business Logic Narrative
When the process 'Add Disposition Code Information' is invoked, and assuming that notification message contains cargo details, when disposition code information is added, the desired outcome is that the system includes disposition code, entry number, and related processing information in the message.
💻 Technical Criteria
Given Notification message contains cargo details
When Disposition code information is added
Then The system includes disposition code, entry number, and related processing information in the message
R-GCX016E-cbl-00885 Set Notification Type as UNRLSE
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Notification Type as UNRLSE' is invoked, and assuming that cancel release notification message is formatted with cargo and disposition details, when message type classification is performed, the desired outcome is that the system sets notification type as unrlse for cancel release processing.
💻 Technical Criteria
Given Cancel release notification message is formatted with cargo and disposition details
When Message type classification is performed
Then The system sets notification type as UNRLSE for cancel release processing
R-GCX016E-cbl-00889 Update Cargo Status Arrays
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status Arrays' is invoked, and assuming that cancel release processing is complete and action is logged, when status array update is performed, the desired outcome is that the system updates s09a status arrays to reflect cancel release status and removes previous release indicators.
💻 Technical Criteria
Given Cancel release processing is complete and action is logged
When Status array update is performed
Then The system updates S09A status arrays to reflect cancel release status and removes previous release indicators
R-GCX016E-cbl-00890 Clear Bond Start Dates
Process Rules
📊 Business Logic Narrative
When the process 'Clear Bond Start Dates' is invoked, and assuming that a cargo is being processed for arrival at its destination, when the arrival processing is initiated, the desired outcome is that all bond start dates are cleared from the cargo record.
💻 Technical Criteria
Given A cargo is being processed for arrival at its destination
When The arrival processing is initiated
Then All bond start dates are cleared from the cargo record
R-GCX016E-cbl-00891 Set Arrival Index
Action Rules
📊 Business Logic Narrative
When the process 'Set Arrival Index' is invoked, and assuming that a cargo is arriving at a destination location, when the arrival index needs to be established, the desired outcome is that the destination index is set to the current arrival location.
💻 Technical Criteria
Given A cargo is arriving at a destination location
When The arrival index needs to be established
Then The destination index is set to the current arrival location
R-GCX016E-cbl-00892 Calculate Cargo Age from Arrival Date
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Cargo Age from Arrival Date' is invoked, and assuming that a cargo has an established arrival date, when cargo age calculation is required, the desired outcome is that the system calculates the number of days between arrival date and current date.
💻 Technical Criteria
Given A cargo has an established arrival date
When Cargo age calculation is required
Then The system calculates the number of days between arrival date and current date
R-GCX016E-cbl-00893 Update Arrival Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Update Arrival Status Flags' is invoked, and assuming that a cargo has successfully arrived at its destination, when arrival processing is being completed, the desired outcome is that all relevant arrival status flags are updated to indicate completed arrival.
💻 Technical Criteria
Given A cargo has successfully arrived at its destination
When Arrival processing is being completed
Then All relevant arrival status flags are updated to indicate completed arrival
R-GCX016E-cbl-00894 Record Arrival Timestamp
Action Rules
📊 Business Logic Narrative
When the process 'Record Arrival Timestamp' is invoked, and assuming that a cargo arrival process is being finalized, when the arrival timestamp needs to be recorded, the desired outcome is that the current date and time is stored as the official arrival timestamp.
💻 Technical Criteria
Given A cargo arrival process is being finalized
When The arrival timestamp needs to be recorded
Then The current date and time is stored as the official arrival timestamp
R-GCX016E-cbl-00895 Clear Destination Index
Process Rules
📊 Business Logic Narrative
When the process 'Clear Destination Index' is invoked, and assuming that a cargo is being processed for export, when export processing is initiated, the desired outcome is that the destination index is cleared from the cargo record.
💻 Technical Criteria
Given A cargo is being processed for export
When Export processing is initiated
Then The destination index is cleared from the cargo record
R-GCX016E-cbl-00896 Reset Export Processing Flags
Action Rules
📊 Business Logic Narrative
When the process 'Reset Export Processing Flags' is invoked, and assuming that a cargo is undergoing export processing, when export flags need to be reset, the desired outcome is that all export processing flags are reset to their initial state.
💻 Technical Criteria
Given A cargo is undergoing export processing
When Export flags need to be reset
Then All export processing flags are reset to their initial state
R-GCX016E-cbl-00897 Update Export Status
Action Rules
📊 Business Logic Narrative
When the process 'Update Export Status' is invoked, and assuming that a cargo is being exported, when export status update is required, the desired outcome is that the cargo status is updated to indicate export processing.
💻 Technical Criteria
Given A cargo is being exported
When Export status update is required
Then The cargo status is updated to indicate export processing
R-GCX016E-cbl-00898 Clear Export-Related Dates
Process Rules
📊 Business Logic Narrative
When the process 'Clear Export-Related Dates' is invoked, and assuming that a cargo export process is being reset or completed, when export-related dates need to be cleared, the desired outcome is that all export-related date fields are cleared from the cargo record.
💻 Technical Criteria
Given A cargo export process is being reset or completed
When Export-related dates need to be cleared
Then All export-related date fields are cleared from the cargo record
R-GCX016E-cbl-00899 Restore Bond Information
Action Rules
📊 Business Logic Narrative
When the process 'Restore Bond Information' is invoked, and assuming that a cargo requires bond information restoration, when bond restoration process is initiated, the desired outcome is that all previously saved bond information is restored to the cargo record.
💻 Technical Criteria
Given A cargo requires bond information restoration
When Bond restoration process is initiated
Then All previously saved bond information is restored to the cargo record
R-GCX016E-cbl-00900 Recalculate Cargo Age
Computation Rules
📊 Business Logic Narrative
When the process 'Recalculate Cargo Age' is invoked, and assuming that bond information has been restored for a cargo, when cargo age recalculation is required, the desired outcome is that the system recalculates cargo age using the restored bond start dates.
💻 Technical Criteria
Given Bond information has been restored for a cargo
When Cargo age recalculation is required
Then The system recalculates cargo age using the restored bond start dates
R-GCX016E-cbl-00901 Reset Bond Start Dates
Action Rules
📊 Business Logic Narrative
When the process 'Reset Bond Start Dates' is invoked, and assuming that a cargo is undergoing bond restoration, when bond start dates need to be reset, the desired outcome is that all bond start dates are reset to their previously saved values.
💻 Technical Criteria
Given A cargo is undergoing bond restoration
When Bond start dates need to be reset
Then All bond start dates are reset to their previously saved values
R-GCX016E-cbl-00902 Update Bond Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Update Bond Status Flags' is invoked, and assuming that bond information has been restored for a cargo, when bond status flags need updating, the desired outcome is that all bond status flags are updated to reflect the restored bond state.
💻 Technical Criteria
Given Bond information has been restored for a cargo
When Bond status flags need updating
Then All bond status flags are updated to reflect the restored bond state
R-GCX016E-cbl-00903 Restore Previous Bond State
Process Rules
📊 Business Logic Narrative
When the process 'Restore Previous Bond State' is invoked, and assuming that a cargo requires complete bond state restoration, when previous bond state restoration is initiated, the desired outcome is that the cargo is restored to its complete previous bonded state with all associated attributes.
💻 Technical Criteria
Given A cargo requires complete bond state restoration
When Previous bond state restoration is initiated
Then The cargo is restored to its complete previous bonded state with all associated attributes
R-GCX016E-cbl-00904 Update Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Record' is invoked, and assuming that destination index management processing has been completed, when cargo record update is required, the desired outcome is that all index management changes are saved to the cargo record.
💻 Technical Criteria
Given Destination index management processing has been completed
When Cargo record update is required
Then All index management changes are saved to the cargo record
R-GCX016E-cbl-00906 Retrieve Current Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Cargo Record' is invoked, and assuming that a cargo needs status update processing, when the system initiates cargo record replacement process, the desired outcome is that the current cargo record is retrieved from the us cargo root segments database.
💻 Technical Criteria
Given A cargo needs status update processing
When The system initiates cargo record replacement process
Then The current cargo record is retrieved from the US Cargo Root Segments database
R-GCX016E-cbl-00907 Update Cargo Status Changes
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status Changes' is invoked, and assuming that cargo record has been retrieved and disposition codes have been processed, when status changes need to be applied to the cargo record, the desired outcome is that the cargo status fields are updated with new status information including hold flags, release quantities, and arrival dates.
💻 Technical Criteria
Given Cargo record has been retrieved and disposition codes have been processed
When Status changes need to be applied to the cargo record
Then The cargo status fields are updated with new status information including hold flags, release quantities, and arrival dates
R-GCX016E-cbl-00908 Format Car ID Information
Computation Rules
📊 Business Logic Narrative
When the process 'Format Car ID Information' is invoked, and assuming that n7 equipment segment data is available with car initial and number, when car id information needs to be formatted for cargo record, the desired outcome is that the car initial and number are combined and formatted into a standardized car id format.
💻 Technical Criteria
Given N7 equipment segment data is available with car initial and number
When Car ID information needs to be formatted for cargo record
Then The car initial and number are combined and formatted into a standardized car ID format
R-GCX016E-cbl-00909 CPRS Cargo?
Decision Rules
📊 Business Logic Narrative
When the process 'CPRS Cargo?' is invoked, and assuming that a cargo record is being processed for car id updates, when the system checks if the cargo is cprs type, the desired outcome is that if cargo is cprs type, car id updates are skipped; if non-cprs, car id is updated with equipment information.
💻 Technical Criteria
Given A cargo record is being processed for car ID updates
When The system checks if the cargo is CPRS type
Then If cargo is CPRS type, car ID updates are skipped; if non-CPRS, car ID is updated with equipment information
R-GCX016E-cbl-00910 Update Car ID for Non-CPRS
Process Rules
📊 Business Logic Narrative
When the process 'Update Car ID for Non-CPRS' is invoked, and assuming that cargo is determined to be non-cprs type and car id information is formatted, when car id update is required for the cargo record, the desired outcome is that the cargo record car id fields are updated with the formatted car identification information.
💻 Technical Criteria
Given Cargo is determined to be non-CPRS type and car ID information is formatted
When Car ID update is required for the cargo record
Then The cargo record car ID fields are updated with the formatted car identification information
R-GCX016E-cbl-00911 Skip Car ID Update for CPRS
Process Rules
📊 Business Logic Narrative
When the process 'Skip Car ID Update for CPRS' is invoked, and assuming that cargo is determined to be cprs type, when car id update processing is initiated, the desired outcome is that the car id update is bypassed and existing car id information remains unchanged.
💻 Technical Criteria
Given Cargo is determined to be CPRS type
When Car ID update processing is initiated
Then The car ID update is bypassed and existing car ID information remains unchanged
R-GCX016E-cbl-00912 Replace Cargo Record in Database
Action Rules
📊 Business Logic Narrative
When the process 'Replace Cargo Record in Database' is invoked, and assuming that cargo record has been updated with new status and car id information, when database update is required to persist changes, the desired outcome is that the existing cargo record in us cargo root segments database is replaced with the updated record.
💻 Technical Criteria
Given Cargo record has been updated with new status and car ID information
When Database update is required to persist changes
Then The existing cargo record in US Cargo Root Segments database is replaced with the updated record
R-GCX016E-cbl-00913 Validate Equipment Type
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Equipment Type' is invoked, and assuming that cargo record has been updated in the database, when gcciis integration is being considered, the desired outcome is that the system checks if the equipment type is valid for gcciis processing (containers, trailers, chassis, etc.).
💻 Technical Criteria
Given Cargo record has been updated in the database
When GCCIIS integration is being considered
Then The system checks if the equipment type is valid for GCCIIS processing (containers, trailers, chassis, etc.)
R-GCX016E-cbl-00914 Valid Equipment Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Valid Equipment Type?' is invoked, and assuming that equipment type validation has been performed, when decision is needed for gcciis integration, the desired outcome is that if equipment type is valid, proceed with status mapping; if invalid, skip gcciis update.
💻 Technical Criteria
Given Equipment type validation has been performed
When Decision is needed for GCCIIS integration
Then If equipment type is valid, proceed with status mapping; if invalid, skip GCCIIS update
R-GCX016E-cbl-00915 Map Internal Status to GCCIIS Status
Computation Rules
📊 Business Logic Narrative
When the process 'Map Internal Status to GCCIIS Status' is invoked, and assuming that equipment type is valid for gcciis and cargo has internal status, when status mapping is required for gcciis integration, the desired outcome is that internal status codes (hold, release, ptt, ptt-ex) are mapped to corresponding gcciis status descriptions.
💻 Technical Criteria
Given Equipment type is valid for GCCIIS and cargo has internal status
When Status mapping is required for GCCIIS integration
Then Internal status codes (HOLD, RELEASE, PTT, PTT-EX) are mapped to corresponding GCCIIS status descriptions
R-GCX016E-cbl-00916 Release Quantity Check
Decision Rules
📊 Business Logic Narrative
When the process 'Release Quantity Check' is invoked, and assuming that status has been mapped for gcciis and cargo has release quantity information, when release status determination is needed for gcciis, the desired outcome is that if released quantity equals total quantity, send full release; if released quantity is less than total, send hold status.
💻 Technical Criteria
Given Status has been mapped for GCCIIS and cargo has release quantity information
When Release status determination is needed for GCCIIS
Then If released quantity equals total quantity, send full release; if released quantity is less than total, send hold status
R-GCX016E-cbl-00917 Send Full Release to GCCIIS
Action Rules
📊 Business Logic Narrative
When the process 'Send Full Release to GCCIIS' is invoked, and assuming that release quantity equals total quantity and status is mapped, when gcciis notification is required for full release, the desired outcome is that a full release status is sent to gcciis equipment tracking system with cargo and equipment details.
💻 Technical Criteria
Given Release quantity equals total quantity and status is mapped
When GCCIIS notification is required for full release
Then A full release status is sent to GCCIIS equipment tracking system with cargo and equipment details
R-GCX016E-cbl-00918 Send Hold Status to GCCIIS
Action Rules
📊 Business Logic Narrative
When the process 'Send Hold Status to GCCIIS' is invoked, and assuming that released quantity is less than total quantity or cargo is held, when gcciis notification is required for hold status, the desired outcome is that a hold status is sent to gcciis equipment tracking system with cargo and equipment details.
💻 Technical Criteria
Given Released quantity is less than total quantity or cargo is held
When GCCIIS notification is required for hold status
Then A hold status is sent to GCCIIS equipment tracking system with cargo and equipment details
R-GCX016E-cbl-00919 Skip GCCIIS Update
Process Rules
📊 Business Logic Narrative
When the process 'Skip GCCIIS Update' is invoked, and assuming that equipment type is invalid for gcciis or status conditions exclude gcciis processing, when gcciis integration decision is made, the desired outcome is that gcciis update is skipped and processing continues without equipment tracking system notification.
💻 Technical Criteria
Given Equipment type is invalid for GCCIIS or status conditions exclude GCCIIS processing
When GCCIIS integration decision is made
Then GCCIIS update is skipped and processing continues without equipment tracking system notification
R-GCX016E-cbl-00920 Log Status Update Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Status Update Action' is invoked, and assuming that cargo status updates and gcciis notifications have been processed, when action logging is required for audit trail, the desired outcome is that the status update actions are logged with cargo details, status changes, and processing results.
💻 Technical Criteria
Given Cargo status updates and GCCIIS notifications have been processed
When Action logging is required for audit trail
Then The status update actions are logged with cargo details, status changes, and processing results
R-GCX016E-cbl-00925 Process Individual Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Process Individual Cargo Record' is invoked, and assuming that a valid cargo record exists for processing, when individual cargo processing is initiated, the desired outcome is that cargo record is processed according to disposition codes and status rules.
💻 Technical Criteria
Given A valid cargo record exists for processing
When Individual cargo processing is initiated
Then Cargo record is processed according to disposition codes and status rules
R-GCX016E-cbl-00926 Analyze Cargo Hold Status
Decision Rules
📊 Business Logic Narrative
When the process 'Analyze Cargo Hold Status' is invoked, and assuming that a cargo record is being processed, when system evaluates cargo hold status, the desired outcome is that hold status is analyzed to determine next processing steps.
💻 Technical Criteria
Given A cargo record is being processed
When System evaluates cargo hold status
Then Hold status is analyzed to determine next processing steps
R-GCX016E-cbl-00927 Manual Release Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Manual Release Present?' is invoked, and assuming that cargo record contains disposition codes, when system evaluates disposition codes for manual release, the desired outcome is that if manual release present, cargo bypasses hold checks; otherwise continue hold evaluation.
💻 Technical Criteria
Given Cargo record contains disposition codes
When System evaluates disposition codes for manual release
Then If manual release present, cargo bypasses hold checks; otherwise continue hold evaluation
R-GCX016E-cbl-00928 Check Various Hold Types
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Check Various Hold Types', assuming that cargo does not have manual release status, when system checks for various hold types in cargo status, the desired outcome is that hold types are identified and classified for appropriate processing.
💻 Technical Criteria
EXCLUDING Cargo does not have manual release status
When System checks for various hold types in cargo status
Then Hold types are identified and classified for appropriate processing
R-GCX016E-cbl-00929 Border Hold?
Decision Rules
📊 Business Logic Narrative
When the process 'Border Hold?' is invoked, and assuming that cargo status is being evaluated for holds, when system checks for border hold indicators, the desired outcome is that if border hold exists, processing continues to release verification; otherwise check next hold type.
💻 Technical Criteria
Given Cargo status is being evaluated for holds
When System checks for border hold indicators
Then If border hold exists, processing continues to release verification; otherwise check next hold type
R-GCX016E-cbl-00930 Destination Hold?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Destination Hold?', assuming that cargo does not have border hold and status is being evaluated, when system checks for destination hold indicators, the desired outcome is that if destination hold exists, processing continues to release verification; otherwise check next hold type.
💻 Technical Criteria
EXCLUDING Cargo does not have border hold and status is being evaluated
When System checks for destination hold indicators
Then If destination hold exists, processing continues to release verification; otherwise check next hold type
R-GCX016E-cbl-00931 FDA Hold?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'FDA Hold?', assuming that cargo does not have border or destination hold and status is being evaluated, when system checks for fda hold indicators, the desired outcome is that if fda hold exists, processing continues to release verification; otherwise check piece count hold.
💻 Technical Criteria
EXCLUDING Cargo does not have border or destination hold and status is being evaluated
When System checks for FDA hold indicators
Then If FDA hold exists, processing continues to release verification; otherwise check piece count hold
R-GCX016E-cbl-00932 Piece Count Hold?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Piece Count Hold?', assuming that cargo does not have border, destination, or fda hold and status is being evaluated, when system checks for piece count hold indicators, the desired outcome is that if piece count hold exists, processing continues to release verification; otherwise retrieve next cargo record.
💻 Technical Criteria
EXCLUDING Cargo does not have border, destination, or FDA hold and status is being evaluated
When System checks for piece count hold indicators
Then If piece count hold exists, processing continues to release verification; otherwise retrieve next cargo record
R-GCX016E-cbl-00936 All Records Released?
Decision Rules
📊 Business Logic Narrative
When the process 'All Records Released?' is invoked, and assuming that release status has been verified across all related cargo records, when system evaluates if all records are in released status, the desired outcome is that if all records released, generate comprehensive notification; otherwise generate status change notification.
💻 Technical Criteria
Given Release status has been verified across all related cargo records
When System evaluates if all records are in released status
Then If all records released, generate comprehensive notification; otherwise generate status change notification
R-GCX016E-cbl-00938 Create Merlin Notification for Status Changes
Action Rules
📊 Business Logic Narrative
When the process 'Create Merlin Notification for Status Changes' is invoked, and assuming that cargo status changes have occurred during processing, when merlin notification creation is triggered, the desired outcome is that status change notifications are created and routed to appropriate recipients.
💻 Technical Criteria
Given Cargo status changes have occurred during processing
When Merlin notification creation is triggered
Then Status change notifications are created and routed to appropriate recipients
R-GCX016E-cbl-00939 Update Cargo Status in Database
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status in Database' is invoked, and assuming that cargo status changes and notifications have been processed, when database update is initiated, the desired outcome is that all cargo status changes are committed to the database.
💻 Technical Criteria
Given Cargo status changes and notifications have been processed
When Database update is initiated
Then All cargo status changes are committed to the database
R-GCX016E-cbl-00941 Check Cargo Deletion Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check Cargo Deletion Status' is invoked, and assuming that a cargo record exists in the system, when the system checks the cargo deletion status flag, the desired outcome is that the cargo is identified as either deleted or active based on the deletion status indicator.
💻 Technical Criteria
Given A cargo record exists in the system
When The system checks the cargo deletion status flag
Then The cargo is identified as either deleted or active based on the deletion status indicator
R-GCX016E-cbl-00942 Mark as Deleted Cargo
Action Rules
📊 Business Logic Narrative
When the process 'Mark as Deleted Cargo' is invoked, and assuming that a cargo record has been verified as deleted, when the deletion status check confirms the cargo is deleted, the desired outcome is that the cargo is marked with deleted status and processing terminates for this cargo.
💻 Technical Criteria
Given A cargo record has been verified as deleted
When The deletion status check confirms the cargo is deleted
Then The cargo is marked with deleted status and processing terminates for this cargo
R-GCX016E-cbl-00943 Check Manual Release Status
Decision Rules
📊 Business Logic Narrative
When the process 'Check Manual Release Status' is invoked, and assuming that an active cargo record exists in the system, when the system analyzes the cargo's release status indicators, the desired outcome is that the cargo is classified as either having manual release or no manual release based on release status flags.
💻 Technical Criteria
Given An active cargo record exists in the system
When The system analyzes the cargo's release status indicators
Then The cargo is classified as either having manual release or no manual release based on release status flags
R-GCX016E-cbl-00944 Identify Manual Release
Definitional Rules
📊 Business Logic Narrative
When the process 'Identify Manual Release' is invoked, and assuming that a cargo record shows manual release indicators, when manual release status is confirmed through status analysis, the desired outcome is that the cargo is flagged as manually released for subsequent processing.
💻 Technical Criteria
Given A cargo record shows manual release indicators
When Manual release status is confirmed through status analysis
Then The cargo is flagged as manually released for subsequent processing
R-GCX016E-cbl-00945 Analyze Hold Status Types
Decision Rules
📊 Business Logic Narrative
When the process 'Analyze Hold Status Types' is invoked, and assuming that a cargo record exists with potential hold conditions, when the system evaluates all hold status indicators, the desired outcome is that the system identifies and categorizes each type of hold (border, destination, fda, piece count, custom) applied to the cargo.
💻 Technical Criteria
Given A cargo record exists with potential hold conditions
When The system evaluates all hold status indicators
Then The system identifies and categorizes each type of hold (border, destination, FDA, piece count, custom) applied to the cargo
R-GCX016E-cbl-00946 Border Hold Analysis
Validation Rules
📊 Business Logic Narrative
When the process 'Border Hold Analysis' is invoked, and assuming that a cargo record requires hold status analysis, when the system examines border hold indicators and related status codes, the desired outcome is that the cargo is classified as either having border hold conditions or being clear of border holds.
💻 Technical Criteria
Given A cargo record requires hold status analysis
When The system examines border hold indicators and related status codes
Then The cargo is classified as either having border hold conditions or being clear of border holds
R-GCX016E-cbl-00947 Destination Hold Analysis
Validation Rules
📊 Business Logic Narrative
When the process 'Destination Hold Analysis' is invoked, and assuming that a cargo record requires hold status analysis, when the system examines destination hold indicators and location-specific restrictions, the desired outcome is that the cargo is classified as either having destination hold conditions or being clear for destination processing.
💻 Technical Criteria
Given A cargo record requires hold status analysis
When The system examines destination hold indicators and location-specific restrictions
Then The cargo is classified as either having destination hold conditions or being clear for destination processing
R-GCX016E-cbl-00948 FDA Hold Analysis
Policy Rules
📊 Business Logic Narrative
When the process 'FDA Hold Analysis' is invoked, and assuming that a cargo record requires hold status analysis, when the system examines fda hold indicators and regulatory compliance status, the desired outcome is that the cargo is classified as either having fda hold conditions or being compliant for fda processing.
💻 Technical Criteria
Given A cargo record requires hold status analysis
When The system examines FDA hold indicators and regulatory compliance status
Then The cargo is classified as either having FDA hold conditions or being compliant for FDA processing
R-GCX016E-cbl-00949 Piece Count Hold Analysis
Validation Rules
📊 Business Logic Narrative
When the process 'Piece Count Hold Analysis' is invoked, and assuming that a cargo record requires hold status analysis, when the system examines piece count hold indicators and quantity validation results, the desired outcome is that the cargo is classified as either having piece count hold conditions or having accurate piece counts.
💻 Technical Criteria
Given A cargo record requires hold status analysis
When The system examines piece count hold indicators and quantity validation results
Then The cargo is classified as either having piece count hold conditions or having accurate piece counts
R-GCX016E-cbl-00950 Custom Hold Analysis
Policy Rules
📊 Business Logic Narrative
When the process 'Custom Hold Analysis' is invoked, and assuming that a cargo record requires hold status analysis, when the system examines custom hold indicators and customs processing status, the desired outcome is that the cargo is classified as either having custom hold conditions or being clear for customs processing.
💻 Technical Criteria
Given A cargo record requires hold status analysis
When The system examines custom hold indicators and customs processing status
Then The cargo is classified as either having custom hold conditions or being clear for customs processing
R-GCX016E-cbl-00951 Evaluate Release Eligibility
Decision Rules
📊 Business Logic Narrative
When the process 'Evaluate Release Eligibility' is invoked, and assuming that a cargo record has been analyzed for all hold types, when the system evaluates the combined impact of all hold conditions and release requirements, the desired outcome is that the cargo is determined to be either eligible for release or requiring continued hold status.
💻 Technical Criteria
Given A cargo record has been analyzed for all hold types
When The system evaluates the combined impact of all hold conditions and release requirements
Then The cargo is determined to be either eligible for release or requiring continued hold status
R-GCX016E-cbl-00952 Set Release Eligible Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Release Eligible Flag' is invoked, and assuming that a cargo record has been determined eligible for release, when all hold conditions have been cleared and release requirements are met, the desired outcome is that the system sets the release eligible flag and prepares the cargo for release processing.
💻 Technical Criteria
Given A cargo record has been determined eligible for release
When All hold conditions have been cleared and release requirements are met
Then The system sets the release eligible flag and prepares the cargo for release processing
R-GCX016E-cbl-00953 Set Hold Required Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Hold Required Flag' is invoked, and assuming that a cargo record has been determined to require continued hold status, when one or more hold conditions remain unresolved or new hold requirements are identified, the desired outcome is that the system sets the hold required flag and maintains the cargo in hold status.
💻 Technical Criteria
Given A cargo record has been determined to require continued hold status
When One or more hold conditions remain unresolved or new hold requirements are identified
Then The system sets the hold required flag and maintains the cargo in hold status
R-GCX016E-cbl-00956 Determine Overall Status
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Overall Status' is invoked, and assuming that individual cargo analysis is complete or all related records have been analyzed, when the system evaluates all status indicators, hold conditions, and release eligibility, the desired outcome is that the system determines the overall status for the cargo or shipment based on the most restrictive conditions.
💻 Technical Criteria
Given Individual cargo analysis is complete or all related records have been analyzed
When The system evaluates all status indicators, hold conditions, and release eligibility
Then The system determines the overall status for the cargo or shipment based on the most restrictive conditions
R-GCX016E-cbl-00957 Generate Status Summary
Action Rules
📊 Business Logic Narrative
When the process 'Generate Status Summary' is invoked, and assuming that the overall status has been determined for the cargo or shipment, when the system compiles all analysis results including hold types, release eligibility, and final status, the desired outcome is that a complete status summary is generated containing all relevant cargo analysis information.
💻 Technical Criteria
Given The overall status has been determined for the cargo or shipment
When The system compiles all analysis results including hold types, release eligibility, and final status
Then A complete status summary is generated containing all relevant cargo analysis information
R-GCX016E-cbl-00958 Update Cargo Analysis Results
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Analysis Results' is invoked, and assuming that a status summary has been generated for the cargo analysis, when the system processes the final analysis results, the desired outcome is that the cargo records are updated with the new status information, hold flags, and release eligibility indicators.
💻 Technical Criteria
Given A status summary has been generated for the cargo analysis
When The system processes the final analysis results
Then The cargo records are updated with the new status information, hold flags, and release eligibility indicators
R-GCX016E-cbl-00959 Verify Cargo Release Status
Validation Rules
📊 Business Logic Narrative
When the process 'Verify Cargo Release Status' is invoked, and assuming that a cargo release notification process is initiated, when the system checks the cargo release status, the desired outcome is that the system confirms cargo records are available and accessible for processing.
💻 Technical Criteria
Given A cargo release notification process is initiated
When The system checks the cargo release status
Then The system confirms cargo records are available and accessible for processing
R-GCX016E-cbl-00961 Calculate Release Quantities
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Release Quantities' is invoked, and assuming that cargo records are confirmed as released, when the system prepares release notification details, the desired outcome is that the system calculates and formats the total released quantities for inclusion in the notification message.
💻 Technical Criteria
Given Cargo records are confirmed as released
When The system prepares release notification details
Then The system calculates and formats the total released quantities for inclusion in the notification message
R-GCX016E-cbl-00962 Format Equipment Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment Information' is invoked, and assuming that equipment information exists in n7 segments, when the system prepares release notification content, the desired outcome is that the system formats car id, equipment initial, and equipment number into standardized format for the notification message.
💻 Technical Criteria
Given Equipment information exists in N7 segments
When The system prepares release notification content
Then The system formats car ID, equipment initial, and equipment number into standardized format for the notification message
R-GCX016E-cbl-00963 Format Disposition Code Details
Process Rules
📊 Business Logic Narrative
When the process 'Format Disposition Code Details' is invoked, and assuming that disposition code information exists in x4 segments, when the system prepares release notification content, the desired outcome is that the system formats disposition codes, entry numbers, and related cargo details for inclusion in the notification message.
💻 Technical Criteria
Given Disposition code information exists in X4 segments
When The system prepares release notification content
Then The system formats disposition codes, entry numbers, and related cargo details for inclusion in the notification message
R-GCX016E-cbl-00967 Include K1 Comment Messages
Process Rules
📊 Business Logic Narrative
When the process 'Include K1 Comment Messages' is invoked, and assuming that k1 comment segments exist for the cargo, when the system prepares comprehensive notification content, the desired outcome is that the system includes up to 4 lines of k1 segment comments in the notification message if available.
💻 Technical Criteria
Given K1 comment segments exist for the cargo
When The system prepares comprehensive notification content
Then The system includes up to 4 lines of K1 segment comments in the notification message if available
R-GCX016E-cbl-00968 Add Special Processing Comments
Process Rules
📊 Business Logic Narrative
When the process 'Add Special Processing Comments' is invoked, and assuming that special processing comments are available for the cargo, when the system prepares detailed notification content, the desired outcome is that the system includes up to 3 lines of special processing comments in the notification message if present.
💻 Technical Criteria
Given Special processing comments are available for the cargo
When The system prepares detailed notification content
Then The system includes up to 3 lines of special processing comments in the notification message if present
R-GCX016E-cbl-00969 Format Comprehensive Release Message
Process Rules
📊 Business Logic Narrative
When the process 'Format Comprehensive Release Message' is invoked, and assuming that all message components have been prepared including equipment info, disposition codes, quantities, and comments, when the system creates the final notification message, the desired outcome is that the system formats all components into a comprehensive release message with proper structure and formatting.
💻 Technical Criteria
Given All message components have been prepared including equipment info, disposition codes, quantities, and comments
When The system creates the final notification message
Then The system formats all components into a comprehensive release message with proper structure and formatting
R-GCX016E-cbl-00972 Cargo Export Status?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Export Status?' is invoked, and assuming that a cargo record with current status and disposition codes, when the system evaluates if export notification processing is required, the desired outcome is that the system determines if cargo has export status and requires export notification processing.
💻 Technical Criteria
Given A cargo record with current status and disposition codes
When The system evaluates if export notification processing is required
Then The system determines if cargo has export status and requires export notification processing
R-GCX016E-cbl-00973 Export Port Validated?
Validation Rules
📊 Business Logic Narrative
When the process 'Export Port Validated?' is invoked, and assuming that a cargo marked for export processing with associated port and routing information, when the system validates export conditions and port information, the desired outcome is that the system confirms if export port is valid and cargo meets export processing requirements.
💻 Technical Criteria
Given A cargo marked for export processing with associated port and routing information
When The system validates export conditions and port information
Then The system confirms if export port is valid and cargo meets export processing requirements
R-GCX016E-cbl-00974 Clear Destination Index
Action Rules
📊 Business Logic Narrative
When the process 'Clear Destination Index' is invoked, and assuming that a cargo record with valid export conditions and existing destination index, when the cargo is being processed for export, the desired outcome is that the system clears the destination index to remove domestic routing information.
💻 Technical Criteria
Given A cargo record with valid export conditions and existing destination index
When The cargo is being processed for export
Then The system clears the destination index to remove domestic routing information
R-GCX016E-cbl-00975 Set Export Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Export Status Flag' is invoked, and assuming that a cargo record that has passed export validation with cleared destination index, when the system processes the cargo for export, the desired outcome is that the system sets the export status flag to indicate export processing status.
💻 Technical Criteria
Given A cargo record that has passed export validation with cleared destination index
When The system processes the cargo for export
Then The system sets the export status flag to indicate export processing status
R-GCX016E-cbl-00976 Calculate Export Date/Time
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Export Date/Time' is invoked, and assuming that a cargo with export status flag set and current system date/time available, when the system calculates export timing information, the desired outcome is that the system assigns appropriate export date and time to the cargo record.
💻 Technical Criteria
Given A cargo with export status flag set and current system date/time available
When The system calculates export timing information
Then The system assigns appropriate export date and time to the cargo record
R-GCX016E-cbl-00977 Prepare Export Notification Message
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Export Notification Message' is invoked, and assuming that a cargo with export status, date/time, and validated export conditions, when the system prepares export notification message, the desired outcome is that the system creates message structure with header information for export notification.
💻 Technical Criteria
Given A cargo with export status, date/time, and validated export conditions
When The system prepares export notification message
Then The system creates message structure with header information for export notification
R-GCX016E-cbl-00978 Format Equipment Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment Information' is invoked, and assuming that an export notification message structure and cargo with associated equipment information, when the system formats equipment details for the export message, the desired outcome is that the system includes formatted car id, equipment type, and equipment details in the export notification.
💻 Technical Criteria
Given An export notification message structure and cargo with associated equipment information
When The system formats equipment details for the export message
Then The system includes formatted car ID, equipment type, and equipment details in the export notification
R-GCX016E-cbl-00980 Format Disposition Code Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Disposition Code Information' is invoked, and assuming that an export notification message with cargo details and disposition code information from x4 segment, when the system formats disposition code information for the export message, the desired outcome is that the system includes formatted disposition code, entry numbers, and related processing information in the export notification.
💻 Technical Criteria
Given An export notification message with cargo details and disposition code information from X4 segment
When The system formats disposition code information for the export message
Then The system includes formatted disposition code, entry numbers, and related processing information in the export notification
R-GCX016E-cbl-00981 Add Release Quantity Information
Process Rules
📊 Business Logic Narrative
When the process 'Add Release Quantity Information' is invoked, and assuming that an export notification message with disposition code information and cargo with release quantity data, when the system adds release quantity information to the export message, the desired outcome is that the system includes release quantities and quantity impact details in the export notification.
💻 Technical Criteria
Given An export notification message with disposition code information and cargo with release quantity data
When The system adds release quantity information to the export message
Then The system includes release quantities and quantity impact details in the export notification
R-GCX016E-cbl-00982 Create Merlin Export Message
Action Rules
📊 Business Logic Narrative
When the process 'Create Merlin Export Message' is invoked, and assuming that a complete export notification with all formatted information including equipment, cargo, disposition, and quantity details, when the system creates the merlin export message, the desired outcome is that the system generates a complete merlin export message with proper formatting and routing information.
💻 Technical Criteria
Given A complete export notification with all formatted information including equipment, cargo, disposition, and quantity details
When The system creates the Merlin export message
Then The system generates a complete Merlin export message with proper formatting and routing information
R-GCX016E-cbl-00983 Route to Export Message Recipients
Action Rules
📊 Business Logic Narrative
When the process 'Route to Export Message Recipients' is invoked, and assuming that a complete merlin export message and equipment type information, when the system determines export message recipients, the desired outcome is that the system routes the export notification to appropriate recipients based on equipment type and routing rules.
💻 Technical Criteria
Given A complete Merlin export message and equipment type information
When The system determines export message recipients
Then The system routes the export notification to appropriate recipients based on equipment type and routing rules
R-GCX016E-cbl-00989 Arrival Disposition Code?
Decision Rules
📊 Business Logic Narrative
When the process 'Arrival Disposition Code?' is invoked, and assuming that a cargo has a disposition code in the message, when the system processes the disposition code, the desired outcome is that the system identifies if it is pod (proof of delivery), aad (actual arrival date), or other arrival-related codes and proceeds with arrival processing.
💻 Technical Criteria
Given A cargo has a disposition code in the message
When The system processes the disposition code
Then The system identifies if it is POD (Proof of Delivery), AAD (Actual Arrival Date), or other arrival-related codes and proceeds with arrival processing
R-GCX016E-cbl-00990 Validate Arrival Location
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Arrival Location' is invoked, and assuming that a cargo has an arrival disposition code and location information, when the system validates the arrival location, the desired outcome is that the system confirms the location is valid for arrival processing and matches cargo routing requirements.
💻 Technical Criteria
Given A cargo has an arrival disposition code and location information
When The system validates the arrival location
Then The system confirms the location is valid for arrival processing and matches cargo routing requirements
R-GCX016E-cbl-00991 Set Arrival Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Set Arrival Status Flags' is invoked, and assuming that a cargo has a validated arrival disposition code, when the system processes the arrival event, the desired outcome is that the system sets arrival status flags including arrival date, arrival location, and arrival type indicators.
💻 Technical Criteria
Given A cargo has a validated arrival disposition code
When The system processes the arrival event
Then The system sets arrival status flags including arrival date, arrival location, and arrival type indicators
R-GCX016E-cbl-00992 Clear Bond Start Dates
Process Rules
📊 Business Logic Narrative
When the process 'Clear Bond Start Dates' is invoked, and assuming that a cargo has arrived at its destination and has active bond start dates, when the system processes the arrival event, the desired outcome is that the system clears the bond start dates to stop bond timing calculations.
💻 Technical Criteria
Given A cargo has arrived at its destination and has active bond start dates
When The system processes the arrival event
Then The system clears the bond start dates to stop bond timing calculations
R-GCX016E-cbl-00993 Set Arrival Index
Action Rules
📊 Business Logic Narrative
When the process 'Set Arrival Index' is invoked, and assuming that a cargo has successfully arrived at a validated location, when the system processes the arrival event, the desired outcome is that the system sets the arrival index to reference the arrival location for future processing.
💻 Technical Criteria
Given A cargo has successfully arrived at a validated location
When The system processes the arrival event
Then The system sets the arrival index to reference the arrival location for future processing
R-GCX016E-cbl-00994 Calculate Cargo Age
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Cargo Age' is invoked, and assuming that a cargo has arrival date and time information, when the system processes the arrival event, the desired outcome is that the system calculates the cargo age from entry date to arrival date for reporting and compliance purposes.
💻 Technical Criteria
Given A cargo has arrival date and time information
When The system processes the arrival event
Then The system calculates the cargo age from entry date to arrival date for reporting and compliance purposes
R-GCX016E-cbl-00998 Verify Arrival Status Across Records
Validation Rules
📊 Business Logic Narrative
When the process 'Verify Arrival Status Across Records' is invoked, and assuming that multiple related cargo records have been processed for arrival, when the system verifies arrival status consistency, the desired outcome is that the system ensures all related records have consistent arrival status and flags any discrepancies.
💻 Technical Criteria
Given Multiple related cargo records have been processed for arrival
When The system verifies arrival status consistency
Then The system ensures all related records have consistent arrival status and flags any discrepancies
R-GCX016E-cbl-00999 Create Arrival Notification Message
Action Rules
📊 Business Logic Narrative
When the process 'Create Arrival Notification Message' is invoked, and assuming that a cargo has successfully arrived and all validations are complete, when the system creates arrival notification, the desired outcome is that the system generates a structured arrival notification message with all relevant cargo and arrival details.
💻 Technical Criteria
Given A cargo has successfully arrived and all validations are complete
When The system creates arrival notification
Then The system generates a structured arrival notification message with all relevant cargo and arrival details
R-GCX016E-cbl-01000 Format Arrival Details
Process Rules
📊 Business Logic Narrative
When the process 'Format Arrival Details' is invoked, and assuming that an arrival notification message is being created, when the system formats arrival details, the desired outcome is that the system formats cargo identification, arrival date/time, and status information into the standard notification format.
💻 Technical Criteria
Given An arrival notification message is being created
When The system formats arrival details
Then The system formats cargo identification, arrival date/time, and status information into the standard notification format
R-GCX016E-cbl-01001 Include Equipment Information
Process Rules
📊 Business Logic Narrative
When the process 'Include Equipment Information' is invoked, and assuming that an arrival notification is being formatted, when the system includes equipment information, the desired outcome is that the system adds car id, equipment type, and equipment identification details to the notification message.
💻 Technical Criteria
Given An arrival notification is being formatted
When The system includes equipment information
Then The system adds car ID, equipment type, and equipment identification details to the notification message
R-GCX016E-cbl-01011 Check if Foreign Bill?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Check if Foreign Bill?', assuming that cprs traffic is not found in the system, when the system checks cargo characteristics to determine if it is a foreign bill, the desired outcome is that the system should identify foreign bill status and route to appropriate processing path.
💻 Technical Criteria
EXCLUDING CPRS traffic is not found in the system
When the system checks cargo characteristics to determine if it is a foreign bill
Then the system should identify foreign bill status and route to appropriate processing path
R-GCX016E-cbl-01012 Initialize New Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Initialize New Cargo Record' is invoked, and assuming that a foreign bill has been identified for cprs traffic, when the system needs to create a new cargo record, the desired outcome is that the system should initialize a new cargo record structure with default values.
💻 Technical Criteria
Given a foreign bill has been identified for CPRS traffic
When the system needs to create a new cargo record
Then the system should initialize a new cargo record structure with default values
R-GCX016E-cbl-01013 Set Cargo Record Fields from X4 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Set Cargo Record Fields from X4 Segment' is invoked, and assuming that a new cargo record has been initialized and x4 segment data is available, when the system processes x4 segment information, the desired outcome is that the system should populate cargo record fields including disposition code, entry number, quantity, and related cargo details from the x4 segment.
💻 Technical Criteria
Given a new cargo record has been initialized and X4 segment data is available
When the system processes X4 segment information
Then the system should populate cargo record fields including disposition code, entry number, quantity, and related cargo details from the X4 segment
R-GCX016E-cbl-01014 Set Equipment Information from N7 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Set Equipment Information from N7 Segment' is invoked, and assuming that cargo record fields have been set from x4 segment and n7 segment data is available, when the system processes n7 equipment information, the desired outcome is that the system should assign equipment initial, equipment number, and formatted car id to the cargo record from n7 segment data.
💻 Technical Criteria
Given cargo record fields have been set from X4 segment and N7 segment data is available
When the system processes N7 equipment information
Then the system should assign equipment initial, equipment number, and formatted car ID to the cargo record from N7 segment data
R-GCX016E-cbl-01015 Build Foreign Manifest from M10 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Build Foreign Manifest from M10 Segment' is invoked, and assuming that equipment information has been set and m10 segment data is available, when the system processes m10 manifest information, the desired outcome is that the system should build foreign manifest details including vessel information, transport mode, and manifest identifiers from m10 segment data.
💻 Technical Criteria
Given equipment information has been set and M10 segment data is available
When the system processes M10 manifest information
Then the system should build foreign manifest details including vessel information, transport mode, and manifest identifiers from M10 segment data
R-GCX016E-cbl-01016 Set SCAC Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Set SCAC Code' is invoked, and assuming that foreign manifest has been built from m10 segment, when the system determines carrier information, the desired outcome is that the system should assign the appropriate scac code to identify the carrier for the cargo record.
💻 Technical Criteria
Given foreign manifest has been built from M10 segment
When the system determines carrier information
Then the system should assign the appropriate SCAC code to identify the carrier for the cargo record
R-GCX016E-cbl-01017 Set Transport Type
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Transport Type' is invoked, and assuming that scac code has been assigned and transport characteristics are available, when the system evaluates transport mode and vessel type, the desired outcome is that the system should classify and assign the appropriate transport type (rail, truck, vessel, etc.) to the cargo record.
💻 Technical Criteria
Given SCAC code has been assigned and transport characteristics are available
When the system evaluates transport mode and vessel type
Then the system should classify and assign the appropriate transport type (rail, truck, vessel, etc.) to the cargo record
R-GCX016E-cbl-01018 Set Country Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Country Code' is invoked, and assuming that transport type has been set and routing information is available, when the system determines country information from cargo routing, the desired outcome is that the system should assign the appropriate country code for origin or destination to the cargo record.
💻 Technical Criteria
Given transport type has been set and routing information is available
When the system determines country information from cargo routing
Then the system should assign the appropriate country code for origin or destination to the cargo record
R-GCX016E-cbl-01019 Set Vessel Details
Process Rules
📊 Business Logic Narrative
When the process 'Set Vessel Details' is invoked, and assuming that country code has been assigned and vessel information is available, when the system processes vessel-specific data, the desired outcome is that the system should configure vessel details including vessel name, voyage number, and related transport information in the cargo record.
💻 Technical Criteria
Given country code has been assigned and vessel information is available
When the system processes vessel-specific data
Then the system should configure vessel details including vessel name, voyage number, and related transport information in the cargo record
R-GCX016E-cbl-01020 Format Car ID
Computation Rules
📊 Business Logic Narrative
When the process 'Format Car ID' is invoked, and assuming that vessel details have been set and equipment initial and number are available, when the system formats car identification, the desired outcome is that the system should format car id by combining equipment initial and equipment number according to standard formatting rules.
💻 Technical Criteria
Given vessel details have been set and equipment initial and number are available
When the system formats car identification
Then the system should format car ID by combining equipment initial and equipment number according to standard formatting rules
R-GCX016E-cbl-01021 Validate Cargo Record Data
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Cargo Record Data' is invoked, and assuming that car id has been formatted and all cargo record fields are populated, when the system validates cargo record data, the desired outcome is that the system should verify that all required fields are present, data formats are correct, and business rules are satisfied before allowing database insertion.
💻 Technical Criteria
Given car ID has been formatted and all cargo record fields are populated
When the system validates cargo record data
Then the system should verify that all required fields are present, data formats are correct, and business rules are satisfied before allowing database insertion
R-GCX016E-cbl-01022 Insert New Cargo Record into Database
Action Rules
📊 Business Logic Narrative
When the process 'Insert New Cargo Record into Database' is invoked, and assuming that cargo record data has been validated successfully, when the system performs database insertion, the desired outcome is that the system should insert the new cargo record into the gcsusrt (us cargo root) database table.
💻 Technical Criteria
Given cargo record data has been validated successfully
When the system performs database insertion
Then the system should insert the new cargo record into the GCSUSRT (US Cargo Root) database table
R-GCX016E-cbl-01023 Log Cargo Creation Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Cargo Creation Action' is invoked, and assuming that new cargo record has been successfully inserted into database, when the system logs the creation activity, the desired outcome is that the system should record cargo creation action with timestamp, user information, and cargo details for audit trail purposes.
💻 Technical Criteria
Given new cargo record has been successfully inserted into database
When the system logs the creation activity
Then the system should record cargo creation action with timestamp, user information, and cargo details for audit trail purposes
R-GCX016E-cbl-01024 Update CPRS Processing Flag
Process Rules
📊 Business Logic Narrative
When the process 'Update CPRS Processing Flag' is invoked, and assuming that cargo creation action has been logged successfully, when the system updates processing status, the desired outcome is that the system should set cprs processing flag to indicate that cargo record creation has been completed successfully.
💻 Technical Criteria
Given cargo creation action has been logged successfully
When the system updates processing status
Then the system should set CPRS processing flag to indicate that cargo record creation has been completed successfully
R-GCX016E-cbl-01043 Initialize New Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Initialize New Cargo Record' is invoked, and assuming that a new cargo insertion process is initiated, when the system begins creating a new cargo record, the desired outcome is that a new cargo record structure is initialized with default values and prepared for data population.
💻 Technical Criteria
Given A new cargo insertion process is initiated
When The system begins creating a new cargo record
Then A new cargo record structure is initialized with default values and prepared for data population
R-GCX016E-cbl-01044 Set Cargo Record with X4 Segment Data
Action Rules
📊 Business Logic Narrative
When the process 'Set Cargo Record with X4 Segment Data' is invoked, and assuming that an x4 segment contains disposition code, entry number, and quantity information, when the system processes the x4 segment for new cargo creation, the desired outcome is that the cargo record is populated with disposition code, entry number, quantity, and related x4 segment data.
💻 Technical Criteria
Given An X4 segment contains disposition code, entry number, and quantity information
When The system processes the X4 segment for new cargo creation
Then The cargo record is populated with disposition code, entry number, quantity, and related X4 segment data
R-GCX016E-cbl-01045 Set Cargo Record with N7 Segment Data
Action Rules
📊 Business Logic Narrative
When the process 'Set Cargo Record with N7 Segment Data' is invoked, and assuming that an n7 segment contains equipment initial, equipment number, and other equipment details, when the system processes the n7 segment for new cargo creation, the desired outcome is that the cargo record is populated with equipment initial, equipment number, and other n7 segment equipment data.
💻 Technical Criteria
Given An N7 segment contains equipment initial, equipment number, and other equipment details
When The system processes the N7 segment for new cargo creation
Then The cargo record is populated with equipment initial, equipment number, and other N7 segment equipment data
R-GCX016E-cbl-01046 Format Car ID for Database
Computation Rules
📊 Business Logic Narrative
When the process 'Format Car ID for Database' is invoked, and assuming that equipment initial and equipment number are available from n7 segment, when the system needs to create a car id for database storage, the desired outcome is that the car id is formatted by combining equipment initial and equipment number in the required database format.
💻 Technical Criteria
Given Equipment initial and equipment number are available from N7 segment
When The system needs to create a car ID for database storage
Then The car ID is formatted by combining equipment initial and equipment number in the required database format
R-GCX016E-cbl-01047 Apply CPRS Special Formatting
Decision Rules
📊 Business Logic Narrative
When the process 'Apply CPRS Special Formatting' is invoked, and assuming that a cargo is identified as cprs type, when the system processes cprs cargo for database insertion, the desired outcome is that special cprs formatting is applied including clearing the car id field and applying cprs-specific data formatting.
💻 Technical Criteria
Given A cargo is identified as CPRS type
When The system processes CPRS cargo for database insertion
Then Special CPRS formatting is applied including clearing the car ID field and applying CPRS-specific data formatting
R-GCX016E-cbl-01048 CPRS Cargo?
Decision Rules
📊 Business Logic Narrative
When the process 'CPRS Cargo?' is invoked, and assuming that a cargo record is being processed for insertion, when the system evaluates cargo type classification, the desired outcome is that the cargo is classified as either cprs or non-cprs based on predefined cargo type criteria.
💻 Technical Criteria
Given A cargo record is being processed for insertion
When The system evaluates cargo type classification
Then The cargo is classified as either CPRS or non-CPRS based on predefined cargo type criteria
R-GCX016E-cbl-01049 Build Foreign Manifest Information from M10 Segments
Action Rules
📊 Business Logic Narrative
When the process 'Build Foreign Manifest Information from M10 Segments' is invoked, and assuming that m10 segments contain vessel name, voyage number, and transportation details, when the system builds foreign manifest information for new cargo, the desired outcome is that foreign manifest information is constructed using vessel details, voyage information, and transportation data from m10 segments.
💻 Technical Criteria
Given M10 segments contain vessel name, voyage number, and transportation details
When The system builds foreign manifest information for new cargo
Then Foreign manifest information is constructed using vessel details, voyage information, and transportation data from M10 segments
R-GCX016E-cbl-01050 Set SCAC Code
Action Rules
📊 Business Logic Narrative
When the process 'Set SCAC Code' is invoked, and assuming that carrier information is available from manifest or segment data, when the system processes carrier identification for new cargo, the desired outcome is that the appropriate scac code is assigned to identify the transportation carrier.
💻 Technical Criteria
Given Carrier information is available from manifest or segment data
When The system processes carrier identification for new cargo
Then The appropriate SCAC code is assigned to identify the transportation carrier
R-GCX016E-cbl-01051 Set Transport Type
Decision Rules
📊 Business Logic Narrative
When the process 'Set Transport Type' is invoked, and assuming that transportation mode information is available from manifest segments, when the system classifies the transportation type for new cargo, the desired outcome is that the transport type is set based on the transportation mode indicated in the manifest data.
💻 Technical Criteria
Given Transportation mode information is available from manifest segments
When The system classifies the transportation type for new cargo
Then The transport type is set based on the transportation mode indicated in the manifest data
R-GCX016E-cbl-01052 Set Country Code
Action Rules
📊 Business Logic Narrative
When the process 'Set Country Code' is invoked, and assuming that country information is available from manifest or routing data, when the system processes country classification for new cargo, the desired outcome is that the appropriate country code is assigned based on origin, destination, or routing country information.
💻 Technical Criteria
Given Country information is available from manifest or routing data
When The system processes country classification for new cargo
Then The appropriate country code is assigned based on origin, destination, or routing country information
R-GCX016E-cbl-01053 Set Vessel Details
Action Rules
📊 Business Logic Narrative
When the process 'Set Vessel Details' is invoked, and assuming that vessel information is available from m10 segments or manifest data, when the system processes vessel details for new cargo, the desired outcome is that vessel name, voyage number, and related vessel transportation details are populated in the cargo record.
💻 Technical Criteria
Given Vessel information is available from M10 segments or manifest data
When The system processes vessel details for new cargo
Then Vessel name, voyage number, and related vessel transportation details are populated in the cargo record
R-GCX016E-cbl-01054 Validate Cargo Record Completeness
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Cargo Record Completeness' is invoked, and assuming that a cargo record has been populated with segment data, when the system validates the cargo record before database insertion, the desired outcome is that all required fields are verified as populated and meeting business validation requirements.
💻 Technical Criteria
Given A cargo record has been populated with segment data
When The system validates the cargo record before database insertion
Then All required fields are verified as populated and meeting business validation requirements
R-GCX016E-cbl-01055 Call GCCUSIO Database Insert
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCUSIO Database Insert' is invoked, and assuming that a validated cargo record is ready for database insertion, when the system calls the database insert function, the desired outcome is that the gccusio database insert operation is executed to create the new cargo record.
💻 Technical Criteria
Given A validated cargo record is ready for database insertion
When The system calls the database insert function
Then The GCCUSIO database insert operation is executed to create the new cargo record
R-GCX016E-cbl-01057 Log Successful Cargo Creation
Process Rules
📊 Business Logic Narrative
When the process 'Log Successful Cargo Creation' is invoked, and assuming that a cargo record has been successfully inserted into the database, when the system processes the successful insert result, the desired outcome is that a log entry is created documenting the successful cargo creation with relevant cargo identifiers.
💻 Technical Criteria
Given A cargo record has been successfully inserted into the database
When The system processes the successful insert result
Then A log entry is created documenting the successful cargo creation with relevant cargo identifiers
R-GCX016E-cbl-01058 Update Cargo Counters
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo Counters' is invoked, and assuming that a cargo record has been successfully created, when the system updates processing statistics, the desired outcome is that cargo processing counters are incremented to reflect the successful cargo creation.
💻 Technical Criteria
Given A cargo record has been successfully created
When The system updates processing statistics
Then Cargo processing counters are incremented to reflect the successful cargo creation
R-GCX016E-cbl-01059 Generate Success Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Success Notification' is invoked, and assuming that a cargo record has been successfully created and logged, when the system generates success notifications, the desired outcome is that appropriate notification messages are created and sent to relevant parties or systems.
💻 Technical Criteria
Given A cargo record has been successfully created and logged
When The system generates success notifications
Then Appropriate notification messages are created and sent to relevant parties or systems
R-GCX016E-cbl-01060 Log Insert Error
Process Rules
📊 Business Logic Narrative
When the process 'Log Insert Error' is invoked, and assuming that a database insert operation has failed, when the system processes the failed insert result, the desired outcome is that an error log entry is created documenting the insert failure with error details and cargo information.
💻 Technical Criteria
Given A database insert operation has failed
When The system processes the failed insert result
Then An error log entry is created documenting the insert failure with error details and cargo information
R-GCX016E-cbl-01061 Generate Error Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Error Message' is invoked, and assuming that a cargo record insert operation has failed and been logged, when the system generates error notifications, the desired outcome is that appropriate error messages are created and sent to relevant parties or systems with failure details.
💻 Technical Criteria
Given A cargo record insert operation has failed and been logged
When The system generates error notifications
Then Appropriate error messages are created and sent to relevant parties or systems with failure details
R-GCX016E-cbl-01075 Extract Location Identifier from X4 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Location Identifier from X4 Segment' is invoked, and assuming that an x4 segment is being processed for cargo disposition, when the system needs to identify the destination station, the desired outcome is that the location identifier is extracted from the x4 segment data.
💻 Technical Criteria
Given An X4 segment is being processed for cargo disposition
When The system needs to identify the destination station
Then The location identifier is extracted from the X4 segment data
R-GCX016E-cbl-01084 Set Station Data in Working Storage
Process Rules
📊 Business Logic Narrative
When the process 'Set Station Data in Working Storage' is invoked, and assuming that station information is valid for routing operations, when the system needs to store station data for processing, the desired outcome is that the station data is set in working storage for cargo processing use.
💻 Technical Criteria
Given Station information is valid for routing operations
When The system needs to store station data for processing
Then The station data is set in working storage for cargo processing use
R-GCX016E-cbl-01086 Generate Station Not Found Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Station Not Found Error', assuming that either no location identifier is present or station record is not found, when the station lookup operation fails, the desired outcome is that a station not found error is generated for the cargo processing.
💻 Technical Criteria
EXCLUDING Either no location identifier is present or station record is not found
When The station lookup operation fails
Then A station not found error is generated for the cargo processing
R-GCX016E-cbl-01110 Format Equipment Details
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment Details' is invoked, and assuming that cargo equipment information is available including car id and equipment type, when the system formats equipment details for merlin message content, the desired outcome is that the system includes formatted equipment id, car identification, and equipment type information in the message structure.
💻 Technical Criteria
Given Cargo equipment information is available including car ID and equipment type
When The system formats equipment details for Merlin message content
Then The system includes formatted equipment ID, car identification, and equipment type information in the message structure
R-GCX016E-cbl-01111 Add Disposition Code Information
Process Rules
📊 Business Logic Narrative
When the process 'Add Disposition Code Information' is invoked, and assuming that a disposition code has been processed for a cargo with valid code description available, when the system adds disposition code information to the merlin message, the desired outcome is that the system includes the disposition code, its description, and related processing information in the message content.
💻 Technical Criteria
Given A disposition code has been processed for a cargo with valid code description available
When The system adds disposition code information to the Merlin message
Then The system includes the disposition code, its description, and related processing information in the message content
R-GCX016E-cbl-01112 Calculate Quantity Impact
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Quantity Impact' is invoked, and assuming that a disposition code affects cargo release quantities with current and target quantity values available, when the system calculates quantity impact for merlin message formatting, the desired outcome is that the system determines whether quantities will increase, decrease, or remain unchanged and formats the impact information for the message.
💻 Technical Criteria
Given A disposition code affects cargo release quantities with current and target quantity values available
When The system calculates quantity impact for Merlin message formatting
Then The system determines whether quantities will increase, decrease, or remain unchanged and formats the impact information for the message
R-GCX016E-cbl-01113 Include K1 Free-Form Text
Decision Rules
📊 Business Logic Narrative
When the process 'Include K1 Free-Form Text' is invoked, and assuming that k1 segment comments are available for the cargo being processed, when the system checks for k1 comments during merlin message formatting, the desired outcome is that the system includes up to 4 lines of k1 free-form text comments in the merlin message content.
💻 Technical Criteria
Given K1 segment comments are available for the cargo being processed
When The system checks for K1 comments during Merlin message formatting
Then The system includes up to 4 lines of K1 free-form text comments in the Merlin message content
R-GCX016E-cbl-01114 Add Special Processing Comments
Process Rules
📊 Business Logic Narrative
When the process 'Add Special Processing Comments' is invoked, and assuming that special processing comments are available for the cargo disposition processing, when the system adds special processing information to the merlin message, the desired outcome is that the system includes up to 3 lines of special comments, processing timestamps, and station/location data in the message.
💻 Technical Criteria
Given Special processing comments are available for the cargo disposition processing
When The system adds special processing information to the Merlin message
Then The system includes up to 3 lines of special comments, processing timestamps, and station/location data in the message
R-GCX016E-cbl-01117 Create Before/After Quantity Comparison
Process Rules
📊 Business Logic Narrative
When the process 'Create Before/After Quantity Comparison' is invoked, and assuming that cargo quantities exist both before and after disposition code processing, when the system creates quantity comparison information for the merlin message, the desired outcome is that the system formats before and after quantity values to show the impact of disposition code processing on cargo release quantities.
💻 Technical Criteria
Given Cargo quantities exist both before and after disposition code processing
When The system creates quantity comparison information for the Merlin message
Then The system formats before and after quantity values to show the impact of disposition code processing on cargo release quantities
R-GCX016E-cbl-01118 Format Release Quantity Impact Details
Process Rules
📊 Business Logic Narrative
When the process 'Format Release Quantity Impact Details' is invoked, and assuming that disposition code processing has resulted in changes to cargo release quantities, when the system formats release quantity impact details, the desired outcome is that the system creates detailed quantity impact information showing specific changes to released, held, or processed quantities.
💻 Technical Criteria
Given Disposition code processing has resulted in changes to cargo release quantities
When The system formats release quantity impact details
Then The system creates detailed quantity impact information showing specific changes to released, held, or processed quantities
R-GCX016E-cbl-01119 Compile Complete Message Content
Process Rules
📊 Business Logic Narrative
When the process 'Compile Complete Message Content' is invoked, and assuming that all message components including cargo details, disposition information, comments, and quantity impacts are available, when the system compiles the complete message content, the desired outcome is that the system assembles all components into a structured merlin message with proper formatting, sequencing, and content organization.
💻 Technical Criteria
Given All message components including cargo details, disposition information, comments, and quantity impacts are available
When The system compiles the complete message content
Then The system assembles all components into a structured Merlin message with proper formatting, sequencing, and content organization
R-GCX016E-cbl-01120 Set Message Type and Priority
Decision Rules
📊 Business Logic Narrative
When the process 'Set Message Type and Priority' is invoked, and assuming that a complete merlin message has been compiled with disposition code and cargo information, when the system sets message type and priority, the desired outcome is that the system assigns appropriate message type classification and priority level based on disposition code type, cargo status, and business impact.
💻 Technical Criteria
Given A complete Merlin message has been compiled with disposition code and cargo information
When The system sets message type and priority
Then The system assigns appropriate message type classification and priority level based on disposition code type, cargo status, and business impact
R-GCX016E-cbl-03028 Retrieve Equipment Details
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Equipment Details' is invoked, and assuming that a cargo record exists with equipment information, when the system processes merlin message assembly, the desired outcome is that equipment details are retrieved and made available for message formatting.
💻 Technical Criteria
Given A cargo record exists with equipment information
When The system processes Merlin message assembly
Then Equipment details are retrieved and made available for message formatting
R-GCX016E-cbl-03031 Retrieve Disposition Code Information
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Disposition Code Information' is invoked, and assuming that a disposition code exists for the cargo, when the system processes merlin message assembly, the desired outcome is that disposition code information is retrieved from the dc table.
💻 Technical Criteria
Given A disposition code exists for the cargo
When The system processes Merlin message assembly
Then Disposition code information is retrieved from the DC table
R-GCX016E-cbl-03038 Include K1 Comment Processing
Process Rules
📊 Business Logic Narrative
When the process 'Include K1 Comment Processing' is invoked, and assuming that k1 segment comments exist for the cargo, when the system processes message content assembly, the desired outcome is that k1 comments are included in the merlin message up to the maximum allowed lines.
💻 Technical Criteria
Given K1 segment comments exist for the cargo
When The system processes message content assembly
Then K1 comments are included in the Merlin message up to the maximum allowed lines
R-GCX016E-cbl-03040 Include Special Comments
Process Rules
📊 Business Logic Narrative
When the process 'Include Special Comments' is invoked, and assuming that special comments exist for the cargo processing, when the system processes message content, the desired outcome is that special comments are included in the merlin message up to the maximum allowed lines.
💻 Technical Criteria
Given Special comments exist for the cargo processing
When The system processes message content
Then Special comments are included in the Merlin message up to the maximum allowed lines
R-GCX016E-cbl-03283 Train or Cargo Context?
Decision Rules
📊 Business Logic Narrative
When the process 'Train or Cargo Context?' is invoked, and assuming that a k1 comment is ready for integration with disposition notifications, when the system evaluates the current processing context, the desired outcome is that the comment is routed to either train disposition notification or cargo disposition notification based on the current processing context.
💻 Technical Criteria
Given A K1 comment is ready for integration with disposition notifications
When The system evaluates the current processing context
Then The comment is routed to either train disposition notification or cargo disposition notification based on the current processing context
R-GCX016E-cbl-03284 Add to Merlin Message Content
Process Rules
📊 Business Logic Narrative
When the process 'Add to Merlin Message Content' is invoked, and assuming that k1 comments are available for integration and merlin messages are being generated, when the system formats merlin message content including disposition code information, the desired outcome is that k1 comments are included in the merlin message content along with cargo information, disposition codes, and other relevant details.
💻 Technical Criteria
Given K1 comments are available for integration and Merlin messages are being generated
When The system formats Merlin message content including disposition code information
Then K1 comments are included in the Merlin message content along with cargo information, disposition codes, and other relevant details
R-GCX016E-cbl-03532 Cargo Disposition Comment Pattern
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Disposition Comment Pattern' is invoked, and assuming that k1 segment comment text content is available for analysis, when the comment contains cargo-related disposition information, the desired outcome is that the system identifies this as a cargo disposition comment pattern and sets the cargo comment processing flag.
💻 Technical Criteria
Given K1 segment comment text content is available for analysis
When The comment contains cargo-related disposition information
Then The system identifies this as a cargo disposition comment pattern and sets the cargo comment processing flag
R-GCX016E-cbl-03533 General Comment Pattern
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'General Comment Pattern', assuming that k1 segment comment text content is available for analysis, when the comment does not match canadian pacific railway, train disposition, or cargo disposition patterns, the desired outcome is that the system classifies this as a general comment pattern and sets the general comment processing flag.
💻 Technical Criteria
EXCLUDING K1 segment comment text content is available for analysis
When The comment does not match Canadian Pacific Railway, train disposition, or cargo disposition patterns
Then The system classifies this as a general comment pattern and sets the general comment processing flag
R-GCX016E-cbl-03536 Set Cargo Comment Processing Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Cargo Comment Processing Flag' is invoked, and assuming that cargo disposition comment pattern has been detected in the comment, when the system processes the pattern detection result, the desired outcome is that the cargo comment processing flag is set to indicate special cargo processing is required.
💻 Technical Criteria
Given Cargo disposition comment pattern has been detected in the comment
When The system processes the pattern detection result
Then The cargo comment processing flag is set to indicate special cargo processing is required
R-GCX016E-cbl-03538 Determine Processing Requirements
Process Rules
📊 Business Logic Narrative
When the process 'Determine Processing Requirements' is invoked, and assuming that a comment processing flag has been set (bond creation, train, cargo, or general), when the system evaluates the processing requirements, the desired outcome is that the specific processing requirements are determined based on the comment pattern type.
💻 Technical Criteria
Given A comment processing flag has been set (bond creation, train, cargo, or general)
When The system evaluates the processing requirements
Then The specific processing requirements are determined based on the comment pattern type
R-GCX016E-cbl-03540 Mark for Special Processing
Process Rules
📊 Business Logic Narrative
When the process 'Mark for Special Processing' is invoked, and assuming that comment has been stored for merlin integration, when the comment requires special processing (bond creation, train disposition, or cargo disposition), the desired outcome is that the comment is marked for special processing to ensure appropriate downstream handling.
💻 Technical Criteria
Given Comment has been stored for Merlin integration
When The comment requires special processing (bond creation, train disposition, or cargo disposition)
Then The comment is marked for special processing to ensure appropriate downstream handling
R-GCX016E-cbl-01125 Format Bond Creation Notification
Process Rules
📊 Business Logic Narrative
When the process 'Format Bond Creation Notification' is invoked, and assuming that a validated cp rail bond creation request with extracted k1 text content, when the system formats the bond creation notification message including cargo information, processing details, and special comments, the desired outcome is that a properly formatted merlin message is created containing all necessary bond creation notification information.
💻 Technical Criteria
Given A validated CP Rail bond creation request with extracted K1 text content
When The system formats the bond creation notification message including cargo information, processing details, and special comments
Then A properly formatted Merlin message is created containing all necessary bond creation notification information
R-GCX016E-cbl-01126 Add Special Comments to Message
Process Rules
📊 Business Logic Narrative
When the process 'Add Special Comments to Message' is invoked, and assuming that a bond creation notification message is being formatted and special comments exist for the cargo, when the system processes special comments associated with the cargo record, the desired outcome is that up to 3 lines of special comments are included in the bond creation notification message.
💻 Technical Criteria
Given A bond creation notification message is being formatted and special comments exist for the cargo
When The system processes special comments associated with the cargo record
Then Up to 3 lines of special comments are included in the bond creation notification message
R-GCX016E-cbl-01132 Retrieve Current Cargo Release Quantity
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Cargo Release Quantity' is invoked, and assuming that a cargo record exists with release quantity information, when release quantity impact messaging is initiated, the desired outcome is that the current cargo release quantity is retrieved and stored for impact calculation.
💻 Technical Criteria
Given A cargo record exists with release quantity information
When Release quantity impact messaging is initiated
Then The current cargo release quantity is retrieved and stored for impact calculation
R-GCX016E-cbl-01135 Calculate Quantity Impact
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Quantity Impact' is invoked, and assuming that a disposition code that affects release quantities and current cargo quantity information, when quantity impact calculation is performed, the desired outcome is that the system calculates the specific quantity change amount based on disposition code parameters.
💻 Technical Criteria
Given A disposition code that affects release quantities and current cargo quantity information
When Quantity impact calculation is performed
Then The system calculates the specific quantity change amount based on disposition code parameters
R-GCX016E-cbl-01147 Equipment Type Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Equipment Type Valid?' is invoked, and assuming that a cargo record with equipment information is being processed for gcciis integration, when the system checks the equipment type against valid categories, the desired outcome is that only containers, trailers, and chassis equipment types are allowed to proceed with gcciis integration, all other equipment types are excluded.
💻 Technical Criteria
Given A cargo record with equipment information is being processed for GCCIIS integration
When The system checks the equipment type against valid categories
Then Only containers, trailers, and chassis equipment types are allowed to proceed with GCCIIS integration, all other equipment types are excluded
R-GCX016E-cbl-01148 Cargo Status Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Cargo Status Available?' is invoked, and assuming that a cargo record with valid equipment type is ready for gcciis processing, when the system checks for the presence of cargo status information, the desired outcome is that integration proceeds only when cargo status data is available, otherwise the integration is skipped.
💻 Technical Criteria
Given A cargo record with valid equipment type is ready for GCCIIS processing
When The system checks for the presence of cargo status information
Then Integration proceeds only when cargo status data is available, otherwise the integration is skipped
R-GCX016E-cbl-01149 Map Internal Status to GCCIIS Format
Computation Rules
📊 Business Logic Narrative
When the process 'Map Internal Status to GCCIIS Format' is invoked, and assuming that a cargo record with available status information, when the system processes the internal status code for gcciis transmission, the desired outcome is that the internal status is mapped to the corresponding gcciis status format according to predefined conversion rules.
💻 Technical Criteria
Given A cargo record with available status information
When The system processes the internal status code for GCCIIS transmission
Then The internal status is mapped to the corresponding GCCIIS status format according to predefined conversion rules
R-GCX016E-cbl-01150 Status Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Status Type?' is invoked, and assuming that a cargo status has been mapped to gcciis format, when the system evaluates the status type for routing to appropriate processing logic, the desired outcome is that status is classified as hold, release, ptt (proceed to transit), or ptt-ex (proceed to export) based on cargo disposition.
💻 Technical Criteria
Given A cargo status has been mapped to GCCIIS format
When The system evaluates the status type for routing to appropriate processing logic
Then Status is classified as HOLD, RELEASE, PTT (Proceed to Transit), or PTT-EX (Proceed to Export) based on cargo disposition
R-GCX016E-cbl-01151 Map to HOLD Status
Process Rules
📊 Business Logic Narrative
When the process 'Map to HOLD Status' is invoked, and assuming that a cargo status is classified as a hold type, when the system processes the hold status for gcciis integration, the desired outcome is that the status is mapped to hold format with appropriate hold reason codes and location information.
💻 Technical Criteria
Given A cargo status is classified as a hold type
When The system processes the hold status for GCCIIS integration
Then The status is mapped to HOLD format with appropriate hold reason codes and location information
R-GCX016E-cbl-01152 Map to RELEASE Status
Process Rules
📊 Business Logic Narrative
When the process 'Map to RELEASE Status' is invoked, and assuming that a cargo status is classified as a release type, when the system processes the release status for gcciis integration, the desired outcome is that the status is mapped to release format with release authorization and quantity information.
💻 Technical Criteria
Given A cargo status is classified as a release type
When The system processes the release status for GCCIIS integration
Then The status is mapped to RELEASE format with release authorization and quantity information
R-GCX016E-cbl-01153 Map to PTT Status
Process Rules
📊 Business Logic Narrative
When the process 'Map to PTT Status' is invoked, and assuming that a cargo status is classified as proceed to transit, when the system processes the ptt status for gcciis integration, the desired outcome is that the status is mapped to ptt format with transit authorization and destination information.
💻 Technical Criteria
Given A cargo status is classified as Proceed to Transit
When The system processes the PTT status for GCCIIS integration
Then The status is mapped to PTT format with transit authorization and destination information
R-GCX016E-cbl-01154 Map to PTT-EX Status
Process Rules
📊 Business Logic Narrative
When the process 'Map to PTT-EX Status' is invoked, and assuming that a cargo status is classified as proceed to export, when the system processes the ptt-ex status for gcciis integration, the desired outcome is that the status is mapped to ptt-ex format with export authorization and port information.
💻 Technical Criteria
Given A cargo status is classified as Proceed to Export
When The system processes the PTT-EX status for GCCIIS integration
Then The status is mapped to PTT-EX format with export authorization and port information
R-GCX016E-cbl-01155 Release Quantity Check
Decision Rules
📊 Business Logic Narrative
When the process 'Release Quantity Check' is invoked, and assuming that a cargo status has been processed and mapped for gcciis, when the system evaluates whether quantity validation is required, the desired outcome is that release status types require quantity verification while other status types proceed directly to status update.
💻 Technical Criteria
Given A cargo status has been processed and mapped for GCCIIS
When The system evaluates whether quantity validation is required
Then Release status types require quantity verification while other status types proceed directly to status update
R-GCX016E-cbl-01156 Verify Released Quantity = Total Quantity
Validation Rules
📊 Business Logic Narrative
When the process 'Verify Released Quantity = Total Quantity' is invoked, and assuming that a cargo with release status requires quantity verification, when the system compares released quantity against total cargo quantity, the desired outcome is that full release notification is sent only when released quantity equals total quantity, otherwise partial release status is maintained.
💻 Technical Criteria
Given A cargo with release status requires quantity verification
When The system compares released quantity against total cargo quantity
Then Full release notification is sent only when released quantity equals total quantity, otherwise partial release status is maintained
R-GCX016E-cbl-01157 Send Full Release Notification to GCCIIS
Action Rules
📊 Business Logic Narrative
When the process 'Send Full Release Notification to GCCIIS' is invoked, and assuming that a cargo has been verified as fully released with matching quantities, when the system sends notification to gcciis, the desired outcome is that a full release notification is transmitted with complete cargo and quantity details.
💻 Technical Criteria
Given A cargo has been verified as fully released with matching quantities
When The system sends notification to GCCIIS
Then A full release notification is transmitted with complete cargo and quantity details
R-GCX016E-cbl-01158 Send Status Update to GCCIIS
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Send Status Update to GCCIIS', assuming that a cargo status has been processed and does not require full release verification or quantities do not match, when the system sends status information to gcciis, the desired outcome is that a status update notification is transmitted with current cargo status and relevant details.
💻 Technical Criteria
EXCLUDING A cargo status has been processed and does not require full release verification or quantities do not match
When The system sends status information to GCCIIS
Then A status update notification is transmitted with current cargo status and relevant details
R-GCX016E-cbl-01159 Update Equipment Tracking Status
Process Rules
📊 Business Logic Narrative
When the process 'Update Equipment Tracking Status' is invoked, and assuming that gcciis notification has been successfully transmitted, when the system updates internal tracking records, the desired outcome is that equipment tracking status is updated to reflect the gcciis integration completion and timestamp.
💻 Technical Criteria
Given GCCIIS notification has been successfully transmitted
When The system updates internal tracking records
Then Equipment tracking status is updated to reflect the GCCIIS integration completion and timestamp
R-GCX016E-cbl-01162 Retrieve Freight Forwarder Information
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Freight Forwarder Information' is invoked, and assuming that a disposition code has been identified as a freight forwarder code in the broker database, when the system accesses gcsuss03 and gcsuss07 cargo segments to retrieve freight forwarder data, the desired outcome is that the system obtains the complete freight forwarder information for further validation.
💻 Technical Criteria
Given A disposition code has been identified as a freight forwarder code in the broker database
When The system accesses GCSUSS03 and GCSUSS07 cargo segments to retrieve freight forwarder data
Then The system obtains the complete freight forwarder information for further validation
R-GCX016E-cbl-01163 Is Valid Freight Forwarder Code?
Validation Rules
📊 Business Logic Narrative
When the process 'Is Valid Freight Forwarder Code?' is invoked, and assuming that freight forwarder information has been retrieved from cargo segments, when the system validates the code against freight forwarder records in the broker database, the desired outcome is that the system determines if the code represents a valid freight forwarder disposition or should be processed as a standard code.
💻 Technical Criteria
Given Freight forwarder information has been retrieved from cargo segments
When The system validates the code against freight forwarder records in the broker database
Then The system determines if the code represents a valid freight forwarder disposition or should be processed as a standard code
R-GCX016E-cbl-01166 Retrieve Cargo Segment Data from GCSUSS03
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Cargo Segment Data from GCSUSS03' is invoked, and assuming that a cargo requires freight forwarder analysis, when the system initiates cargo segment retrieval from gcsuss03, the desired outcome is that the primary cargo segment data is retrieved from gcsuss03 for further processing.
💻 Technical Criteria
Given A cargo requires freight forwarder analysis
When The system initiates cargo segment retrieval from GCSUSS03
Then The primary cargo segment data is retrieved from GCSUSS03 for further processing
R-GCX016E-cbl-01167 GCSUSS03 Segment Found?
Validation Rules
📊 Business Logic Narrative
When the process 'GCSUSS03 Segment Found?' is invoked, and assuming that a cargo segment retrieval attempt has been made from gcsuss03, when the system checks if gcsuss03 segment data was found, the desired outcome is that the system determines if gcsuss03 segment exists and routes processing accordingly.
💻 Technical Criteria
Given A cargo segment retrieval attempt has been made from GCSUSS03
When The system checks if GCSUSS03 segment data was found
Then The system determines if GCSUSS03 segment exists and routes processing accordingly
R-GCX016E-cbl-01168 Extract Freight Forwarder Information from GCSUSS03
Process Rules
📊 Business Logic Narrative
When the process 'Extract Freight Forwarder Information from GCSUSS03' is invoked, and assuming that gcsuss03 cargo segment data is available, when the system processes the gcsuss03 segment, the desired outcome is that freight forwarder information is extracted from the gcsuss03 segment data.
💻 Technical Criteria
Given GCSUSS03 cargo segment data is available
When The system processes the GCSUSS03 segment
Then Freight forwarder information is extracted from the GCSUSS03 segment data
R-GCX016E-cbl-01169 Retrieve Additional Cargo Data from GCSUSS07
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Retrieve Additional Cargo Data from GCSUSS07', assuming that primary cargo segment processing is complete or gcsuss03 segment was not found, when the system initiates extended cargo data retrieval from gcsuss07, the desired outcome is that additional cargo segment data is retrieved from gcsuss07 for enhanced freight forwarder analysis.
💻 Technical Criteria
EXCLUDING Primary cargo segment processing is complete or GCSUSS03 segment was not found
When The system initiates extended cargo data retrieval from GCSUSS07
Then Additional cargo segment data is retrieved from GCSUSS07 for enhanced freight forwarder analysis
R-GCX016E-cbl-01170 GCSUSS07 Segment Found?
Validation Rules
📊 Business Logic Narrative
When the process 'GCSUSS07 Segment Found?' is invoked, and assuming that an extended cargo segment retrieval attempt has been made from gcsuss07, when the system checks if gcsuss07 segment data was found, the desired outcome is that the system determines if gcsuss07 segment exists and routes processing accordingly.
💻 Technical Criteria
Given An extended cargo segment retrieval attempt has been made from GCSUSS07
When The system checks if GCSUSS07 segment data was found
Then The system determines if GCSUSS07 segment exists and routes processing accordingly
R-GCX016E-cbl-01171 Extract Extended Freight Forwarder Details from GCSUSS07
Process Rules
📊 Business Logic Narrative
When the process 'Extract Extended Freight Forwarder Details from GCSUSS07' is invoked, and assuming that gcsuss07 extended cargo segment data is available, when the system processes the gcsuss07 segment, the desired outcome is that extended freight forwarder details are extracted from the gcsuss07 segment data.
💻 Technical Criteria
Given GCSUSS07 extended cargo segment data is available
When The system processes the GCSUSS07 segment
Then Extended freight forwarder details are extracted from the GCSUSS07 segment data
R-GCX016E-cbl-01172 Consolidate Freight Forwarder Information
Process Rules
📊 Business Logic Narrative
When the process 'Consolidate Freight Forwarder Information' is invoked, and assuming that freight forwarder information has been extracted from available cargo segments, when the system consolidates the extracted freight forwarder data, the desired outcome is that all available freight forwarder information is combined into a unified dataset for validation.
💻 Technical Criteria
Given Freight forwarder information has been extracted from available cargo segments
When The system consolidates the extracted freight forwarder data
Then All available freight forwarder information is combined into a unified dataset for validation
R-GCX016E-cbl-01173 Validate Freight Forwarder Data Completeness
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Freight Forwarder Data Completeness' is invoked, and assuming that freight forwarder information has been consolidated from available cargo segments, when the system validates the completeness of freight forwarder data, the desired outcome is that the system determines if sufficient freight forwarder information exists for further processing.
💻 Technical Criteria
Given Freight forwarder information has been consolidated from available cargo segments
When The system validates the completeness of freight forwarder data
Then The system determines if sufficient freight forwarder information exists for further processing
R-GCX016E-cbl-01175 Set Freight Forwarder Found Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Freight Forwarder Found Flag' is invoked, and assuming that a valid freight forwarder has been successfully identified from cargo segment analysis, when the system processes the successful freight forwarder identification, the desired outcome is that the freight forwarder found flag is set to indicate successful identification.
💻 Technical Criteria
Given A valid freight forwarder has been successfully identified from cargo segment analysis
When The system processes the successful freight forwarder identification
Then The freight forwarder found flag is set to indicate successful identification
R-GCX016E-cbl-01177 Log Freight Forwarder Not Found
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Freight Forwarder Not Found', assuming that cargo segment analysis has been completed but no valid freight forwarder was identified, when the system processes the freight forwarder not found condition, the desired outcome is that a freight forwarder not found event is logged for audit and tracking purposes.
💻 Technical Criteria
EXCLUDING Cargo segment analysis has been completed but no valid freight forwarder was identified
When The system processes the freight forwarder not found condition
Then A freight forwarder not found event is logged for audit and tracking purposes
R-GCX016E-cbl-01178 Search Broker Database for Freight Forwarder Disposition Codes
Validation Rules
📊 Business Logic Narrative
When the process 'Search Broker Database for Freight Forwarder Disposition Codes' is invoked, and assuming that a disposition code is being processed for cargo, when the system searches the broker table segments for freight forwarder disposition codes, the desired outcome is that the system identifies whether the disposition code is associated with a freight forwarder.
💻 Technical Criteria
Given A disposition code is being processed for cargo
When The system searches the broker table segments for freight forwarder disposition codes
Then The system identifies whether the disposition code is associated with a freight forwarder
R-GCX016E-cbl-01180 Retrieve Cargo Segment Data from GCSUSS03
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Cargo Segment Data from GCSUSS03' is invoked, and assuming that a freight forwarder code has been found in the broker table, when the system needs cargo segment information for freight forwarder processing, the desired outcome is that the system retrieves cargo segment data from gcsuss03 database.
💻 Technical Criteria
Given A freight forwarder code has been found in the broker table
When The system needs cargo segment information for freight forwarder processing
Then The system retrieves cargo segment data from GCSUSS03 database
R-GCX016E-cbl-01181 Retrieve Additional Cargo Data from GCSUSS07
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Additional Cargo Data from GCSUSS07' is invoked, and assuming that primary cargo segment data has been retrieved from gcsuss03, when the system requires additional cargo information for freight forwarder processing, the desired outcome is that the system retrieves additional cargo data from gcsuss07 database.
💻 Technical Criteria
Given Primary cargo segment data has been retrieved from GCSUSS03
When The system requires additional cargo information for freight forwarder processing
Then The system retrieves additional cargo data from GCSUSS07 database
R-GCX016E-cbl-01182 Extract Freight Forwarder Information from Cargo Segments
Process Rules
📊 Business Logic Narrative
When the process 'Extract Freight Forwarder Information from Cargo Segments' is invoked, and assuming that cargo segment data has been retrieved from both gcsuss03 and gcsuss07, when the system processes the cargo segment data, the desired outcome is that the system extracts freight forwarder identification and related information from the cargo segments.
💻 Technical Criteria
Given Cargo segment data has been retrieved from both GCSUSS03 and GCSUSS07
When The system processes the cargo segment data
Then The system extracts freight forwarder identification and related information from the cargo segments
R-GCX016E-cbl-01183 Lookup Freight Forwarder Name in Broker Tables
Action Rules
📊 Business Logic Narrative
When the process 'Lookup Freight Forwarder Name in Broker Tables' is invoked, and assuming that freight forwarder information has been extracted from cargo segments, when the system needs to resolve the freight forwarder name, the desired outcome is that the system looks up the freight forwarder name in the gcst2rt broker name segments table.
💻 Technical Criteria
Given Freight forwarder information has been extracted from cargo segments
When The system needs to resolve the freight forwarder name
Then The system looks up the freight forwarder name in the GCST2RT broker name segments table
R-GCX016E-cbl-01187 Return Freight Forwarder Information
Process Rules
📊 Business Logic Narrative
When the process 'Return Freight Forwarder Information' is invoked, and assuming that a complete freight forwarder profile has been compiled, when the freight forwarder information retrieval process is complete, the desired outcome is that the system returns the complete freight forwarder information for use in cargo processing and notifications.
💻 Technical Criteria
Given A complete freight forwarder profile has been compiled
When The freight forwarder information retrieval process is complete
Then The system returns the complete freight forwarder information for use in cargo processing and notifications
R-GCX016E-cbl-01189 Retrieve Freight Forwarder Information from Cargo Segments
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Freight Forwarder Information from Cargo Segments' is invoked, and assuming that a cargo record exists with segment data, when the system processes freight forwarder contact information retrieval, the desired outcome is that the freight forwarder code is extracted from the cargo segments for further processing.
💻 Technical Criteria
Given A cargo record exists with segment data
When The system processes freight forwarder contact information retrieval
Then The freight forwarder code is extracted from the cargo segments for further processing
R-GCX016E-cbl-01190 Freight Forwarder Code Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Freight Forwarder Code Found?' is invoked, and assuming that cargo segment data has been retrieved, when the system checks for freight forwarder code presence, the desired outcome is that if freight forwarder code exists, proceed to name lookup; otherwise log no code found and end process.
💻 Technical Criteria
Given Cargo segment data has been retrieved
When The system checks for freight forwarder code presence
Then If freight forwarder code exists, proceed to name lookup; otherwise log no code found and end process
R-GCX016E-cbl-01200 Log: No Freight Forwarder Code Found
Process Rules
📊 Business Logic Narrative
When the process 'Log: No Freight Forwarder Code Found' is invoked, and assuming that cargo segment data has been processed, when no freight forwarder code is found in the data, the desired outcome is that a log entry is created indicating no freight forwarder code was found.
💻 Technical Criteria
Given Cargo segment data has been processed
When No freight forwarder code is found in the data
Then A log entry is created indicating no freight forwarder code was found
R-GCX016E-cbl-01205 Is Disposition Code CIH?
Decision Rules
📊 Business Logic Narrative
When the process 'Is Disposition Code CIH?' is invoked, and assuming that a disposition code is being processed for cargo, when the system checks the disposition code value, the desired outcome is that if the disposition code equals 'cih', proceed with email notification processing, otherwise skip email notification.
💻 Technical Criteria
Given A disposition code is being processed for cargo
When The system checks the disposition code value
Then If the disposition code equals 'CIH', proceed with email notification processing, otherwise skip email notification
R-GCX016E-cbl-01206 Search Broker Database for Freight Forwarder
Action Rules
📊 Business Logic Narrative
When the process 'Search Broker Database for Freight Forwarder' is invoked, and assuming that a cih disposition code has been identified for cargo, when the system searches the broker name table for freight forwarder disposition codes, the desired outcome is that the system retrieves freight forwarder information from the broker database if available.
💻 Technical Criteria
Given A CIH disposition code has been identified for cargo
When The system searches the broker name table for freight forwarder disposition codes
Then The system retrieves freight forwarder information from the broker database if available
R-GCX016E-cbl-01207 Freight Forwarder Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Freight Forwarder Found?' is invoked, and assuming that the system has searched the broker database for freight forwarder information, when the search results are evaluated, the desired outcome is that if a freight forwarder is found, continue with cargo data retrieval, otherwise complete email notification process without sending email.
💻 Technical Criteria
Given The system has searched the broker database for freight forwarder information
When The search results are evaluated
Then If a freight forwarder is found, continue with cargo data retrieval, otherwise complete email notification process without sending email
R-GCX016E-cbl-01208 Retrieve Cargo Segment Data
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Cargo Segment Data' is invoked, and assuming that a freight forwarder has been found for the cargo, when the system accesses cargo secondary data segments, the desired outcome is that the system retrieves forwarder and consignee information from cargo segments gcsuss03 and gcsuss07.
💻 Technical Criteria
Given A freight forwarder has been found for the cargo
When The system accesses cargo secondary data segments
Then The system retrieves forwarder and consignee information from cargo segments GCSUSS03 and GCSUSS07
R-GCX016E-cbl-01209 Extract Freight Forwarder Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Freight Forwarder Information' is invoked, and assuming that cargo segment data has been successfully retrieved, when the system processes the cargo segment information, the desired outcome is that the system extracts freight forwarder identification and contact details from the cargo segments.
💻 Technical Criteria
Given Cargo segment data has been successfully retrieved
When The system processes the cargo segment information
Then The system extracts freight forwarder identification and contact details from the cargo segments
R-GCX016E-cbl-01210 Lookup Freight Forwarder Name and Broker Info
Action Rules
📊 Business Logic Narrative
When the process 'Lookup Freight Forwarder Name and Broker Info' is invoked, and assuming that freight forwarder information has been extracted from cargo segments, when the system performs a lookup in the broker name segments table (gcst2rt), the desired outcome is that the system retrieves the freight forwarder name and associated broker information.
💻 Technical Criteria
Given Freight forwarder information has been extracted from cargo segments
When The system performs a lookup in the broker name segments table (GCST2RT)
Then The system retrieves the freight forwarder name and associated broker information
R-GCX016E-cbl-01215 Include Equipment Information
Process Rules
📊 Business Logic Narrative
When the process 'Include Equipment Information' is invoked, and assuming that email content building has started for cih notification, when the system processes equipment data for the email, the desired outcome is that the system includes equipment type, identification, and related details in the email content.
💻 Technical Criteria
Given Email content building has started for CIH notification
When The system processes equipment data for the email
Then The system includes equipment type, identification, and related details in the email content
R-GCX016E-cbl-01228 Skip Email - No CIH Code
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Skip Email - No CIH Code', assuming that a disposition code is being processed for cargo, when the disposition code is not equal to 'cih', the desired outcome is that the system skips all email notification processing and completes the notification process.
💻 Technical Criteria
EXCLUDING A disposition code is being processed for cargo
When The disposition code is not equal to 'CIH'
Then The system skips all email notification processing and completes the notification process
R-GCX016E-cbl-03051 Search Broker Database for Freight Forwarder Disposition Codes
Decision Rules
📊 Business Logic Narrative
When the process 'Search Broker Database for Freight Forwarder Disposition Codes' is invoked, and assuming that a disposition code is being processed for cargo, when the system searches the broker database for freight forwarder disposition codes, the desired outcome is that the system identifies whether the disposition code is associated with freight forwarder processing.
💻 Technical Criteria
Given A disposition code is being processed for cargo
When The system searches the broker database for freight forwarder disposition codes
Then The system identifies whether the disposition code is associated with freight forwarder processing
R-GCX016E-cbl-03052 Freight Forwarder Code Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Freight Forwarder Code Found?' is invoked, and assuming that the broker database has been searched for freight forwarder disposition codes, when the search results are evaluated, the desired outcome is that if a freight forwarder code is found, proceed to retrieve cargo segment data, otherwise log freight forwarder not found.
💻 Technical Criteria
Given The broker database has been searched for freight forwarder disposition codes
When The search results are evaluated
Then If a freight forwarder code is found, proceed to retrieve cargo segment data, otherwise log freight forwarder not found
R-GCX016E-cbl-03053 Retrieve Cargo Segment Data from GCSUSS03
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Cargo Segment Data from GCSUSS03' is invoked, and assuming that a freight forwarder disposition code has been identified, when the system needs cargo segment information for processing, the desired outcome is that the system retrieves cargo segment data from the gcsuss03 database.
💻 Technical Criteria
Given A freight forwarder disposition code has been identified
When The system needs cargo segment information for processing
Then The system retrieves cargo segment data from the GCSUSS03 database
R-GCX016E-cbl-03054 Retrieve Additional Cargo Data from GCSUSS07
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Additional Cargo Data from GCSUSS07' is invoked, and assuming that primary cargo segment data has been retrieved from gcsuss03, when additional cargo information is needed for freight forwarder processing, the desired outcome is that the system retrieves additional cargo data from the gcsuss07 database.
💻 Technical Criteria
Given Primary cargo segment data has been retrieved from GCSUSS03
When Additional cargo information is needed for freight forwarder processing
Then The system retrieves additional cargo data from the GCSUSS07 database
R-GCX016E-cbl-03055 Extract Freight Forwarder Information from Cargo Segments
Process Rules
📊 Business Logic Narrative
When the process 'Extract Freight Forwarder Information from Cargo Segments' is invoked, and assuming that cargo segment data has been retrieved from both gcsuss03 and gcsuss07, when the system processes the cargo segment information, the desired outcome is that the system extracts freight forwarder identification details from the cargo segments.
💻 Technical Criteria
Given Cargo segment data has been retrieved from both GCSUSS03 and GCSUSS07
When The system processes the cargo segment information
Then The system extracts freight forwarder identification details from the cargo segments
R-GCX016E-cbl-03056 Lookup Freight Forwarder Name in Broker Table GCST2RT
Action Rules
📊 Business Logic Narrative
When the process 'Lookup Freight Forwarder Name in Broker Table GCST2RT' is invoked, and assuming that freight forwarder identification has been extracted from cargo segments, when the system needs to validate and retrieve complete freight forwarder information, the desired outcome is that the system looks up the freight forwarder name in the gcst2rt broker name table.
💻 Technical Criteria
Given Freight forwarder identification has been extracted from cargo segments
When The system needs to validate and retrieve complete freight forwarder information
Then The system looks up the freight forwarder name in the GCST2RT broker name table
R-GCX016E-cbl-03287 Retrieve GCSUSS03 Cargo Segment Data
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve GCSUSS03 Cargo Segment Data' is invoked, and assuming that a cargo record exists and requires freight forwarder analysis, when the system initiates cargo segment data analysis, the desired outcome is that the system retrieves gcsuss03 cargo segment data for processing.
💻 Technical Criteria
Given A cargo record exists and requires freight forwarder analysis
When The system initiates cargo segment data analysis
Then The system retrieves GCSUSS03 cargo segment data for processing
R-GCX016E-cbl-03288 Retrieve GCSUSS07 Cargo Segment Data
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve GCSUSS07 Cargo Segment Data' is invoked, and assuming that primary cargo segment data has been retrieved from gcsuss03, when the system continues cargo segment data analysis, the desired outcome is that the system retrieves gcsuss07 cargo segment data for additional processing.
💻 Technical Criteria
Given Primary cargo segment data has been retrieved from GCSUSS03
When The system continues cargo segment data analysis
Then The system retrieves GCSUSS07 cargo segment data for additional processing
R-GCX016E-cbl-03289 Extract Freight Forwarder Identifiers
Process Rules
📊 Business Logic Narrative
When the process 'Extract Freight Forwarder Identifiers' is invoked, and assuming that gcsuss03 and gcsuss07 cargo segment data have been retrieved, when the system processes the cargo segment data, the desired outcome is that the system extracts freight forwarder identifiers from the segment data.
💻 Technical Criteria
Given GCSUSS03 and GCSUSS07 cargo segment data have been retrieved
When The system processes the cargo segment data
Then The system extracts freight forwarder identifiers from the segment data
R-GCX016E-cbl-03291 Search Broker Database for Freight Forwarder
Action Rules
📊 Business Logic Narrative
When the process 'Search Broker Database for Freight Forwarder' is invoked, and assuming that a valid freight forwarder id has been found in cargo segments, when the system needs to validate the freight forwarder, the desired outcome is that the system searches the broker database for matching freight forwarder information.
💻 Technical Criteria
Given A valid freight forwarder ID has been found in cargo segments
When The system needs to validate the freight forwarder
Then The system searches the broker database for matching freight forwarder information
R-GCX016E-cbl-03296 Determine Notification Requirements
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Notification Requirements' is invoked, and assuming that freight forwarder contact information has been retrieved, when the system evaluates notification requirements, the desired outcome is that the system determines the appropriate notification method and requirements based on freight forwarder setup and cargo status.
💻 Technical Criteria
Given Freight forwarder contact information has been retrieved
When The system evaluates notification requirements
Then The system determines the appropriate notification method and requirements based on freight forwarder setup and cargo status
R-GCX016E-cbl-03297 CIH Hold Scenario?
Decision Rules
📊 Business Logic Narrative
When the process 'CIH Hold Scenario?' is invoked, and assuming that notification requirements have been determined for the freight forwarder, when the system evaluates the cargo hold status, the desired outcome is that the system determines if the scenario qualifies as a cih hold requiring email notification.
💻 Technical Criteria
Given Notification requirements have been determined for the freight forwarder
When The system evaluates the cargo hold status
Then The system determines if the scenario qualifies as a CIH hold requiring email notification
R-GCX016E-cbl-03298 Set Email Notification Required Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Email Notification Required Flag' is invoked, and assuming that the cargo situation has been identified as a cih hold scenario, when the system processes the hold scenario determination, the desired outcome is that the system sets the email notification required flag to trigger email delivery.
💻 Technical Criteria
Given The cargo situation has been identified as a CIH hold scenario
When The system processes the hold scenario determination
Then The system sets the email notification required flag to trigger email delivery
R-GCX016E-cbl-03300 Complete Analysis
Process Rules
📊 Business Logic Narrative
When the process 'Complete Analysis' is invoked, and assuming that either email notification required flag or no notification required flag has been set, when the system finalizes the cargo segment data analysis, the desired outcome is that the system completes the analysis process with all notification requirements determined.
💻 Technical Criteria
Given Either email notification required flag or no notification required flag has been set
When The system finalizes the cargo segment data analysis
Then The system completes the analysis process with all notification requirements determined
R-GCX016E-cbl-03542 Disposition Code Found in Broker Database?
Decision Rules
📊 Business Logic Narrative
When the process 'Disposition Code Found in Broker Database?' is invoked, and assuming that the broker database has been searched for the disposition code, when the disposition code is found in the broker database, the desired outcome is that the system proceeds to retrieve cargo segment data for freight forwarder processing.
💻 Technical Criteria
Given The broker database has been searched for the disposition code
When The disposition code is found in the broker database
Then The system proceeds to retrieve cargo segment data for freight forwarder processing
R-GCX016E-cbl-03543 Extract Freight Forwarder Information from Cargo Segments
Process Rules
📊 Business Logic Narrative
When the process 'Extract Freight Forwarder Information from Cargo Segments' is invoked, and assuming that cargo segment data has been retrieved from gcsuss03 and gcsuss07 segments, when the system processes the cargo segments to extract freight forwarder information, the desired outcome is that the system identifies the freight forwarder code and related business information for validation.
💻 Technical Criteria
Given Cargo segment data has been retrieved from GCSUSS03 and GCSUSS07 segments
When The system processes the cargo segments to extract freight forwarder information
Then The system identifies the freight forwarder code and related business information for validation
R-GCX016E-cbl-03544 Valid Broker-Freight Forwarder Relationship?
Authorization Rules
📊 Business Logic Narrative
When the process 'Valid Broker-Freight Forwarder Relationship?' is invoked, and assuming that freight forwarder information has been extracted from cargo segments, when the system looks up the freight forwarder in the gcst2rt broker name table, the desired outcome is that the system validates whether a valid business relationship exists between the broker and freight forwarder.
💻 Technical Criteria
Given Freight forwarder information has been extracted from cargo segments
When The system looks up the freight forwarder in the GCST2RT broker name table
Then The system validates whether a valid business relationship exists between the broker and freight forwarder
R-GCX016E-cbl-03064 Retrieve Equipment Information
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Equipment Information' is invoked, and assuming that a cargo record exists with equipment information, when the system processes email content creation, the desired outcome is that equipment details are retrieved from the cargo segment data.
💻 Technical Criteria
Given A cargo record exists with equipment information
When The system processes email content creation
Then Equipment details are retrieved from the cargo segment data
R-GCX016E-cbl-03065 Format Car ID and Equipment Type
Process Rules
📊 Business Logic Narrative
When the process 'Format Car ID and Equipment Type' is invoked, and assuming that equipment information has been retrieved from cargo data, when the system formats the equipment details, the desired outcome is that car id and equipment type are formatted according to business display standards.
💻 Technical Criteria
Given Equipment information has been retrieved from cargo data
When The system formats the equipment details
Then Car ID and equipment type are formatted according to business display standards
R-GCX016E-cbl-03068 Retrieve Content Description
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Content Description' is invoked, and assuming that a cargo record contains content description information, when the system processes cargo details for email content, the desired outcome is that content description is retrieved from the cargo record.
💻 Technical Criteria
Given A cargo record contains content description information
When The system processes cargo details for email content
Then Content description is retrieved from the cargo record
R-GCX016E-cbl-03069 Get Origin Station Information
Action Rules
📊 Business Logic Narrative
When the process 'Get Origin Station Information' is invoked, and assuming that a cargo record contains origin station reference, when the system processes station information for email content, the desired outcome is that origin station details are retrieved from station information tables.
💻 Technical Criteria
Given A cargo record contains origin station reference
When The system processes station information for email content
Then Origin station details are retrieved from station information tables
R-GCX016E-cbl-03070 Get Destination Station Information
Action Rules
📊 Business Logic Narrative
When the process 'Get Destination Station Information' is invoked, and assuming that a cargo record contains destination station reference, when the system processes station information for email content, the desired outcome is that destination station details are retrieved from station information tables.
💻 Technical Criteria
Given A cargo record contains destination station reference
When The system processes station information for email content
Then Destination station details are retrieved from station information tables
R-GCX016E-cbl-03072 Retrieve Disposition Code Details
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Disposition Code Details' is invoked, and assuming that a cargo record contains disposition code reference, when the system processes disposition information for email content, the desired outcome is that disposition code details are retrieved from disposition code tables.
💻 Technical Criteria
Given A cargo record contains disposition code reference
When The system processes disposition information for email content
Then Disposition code details are retrieved from disposition code tables
R-GCX016E-cbl-03075 Build Email Subject Line
Computation Rules
📊 Business Logic Narrative
When the process 'Build Email Subject Line' is invoked, and assuming that all cargo and disposition information has been retrieved and formatted, when the system builds the email subject line, the desired outcome is that email subject line is constructed with relevant cargo and disposition details.
💻 Technical Criteria
Given All cargo and disposition information has been retrieved and formatted
When The system builds the email subject line
Then Email subject line is constructed with relevant cargo and disposition details
R-GCX016E-cbl-03077 Add Equipment Details Section
Process Rules
📊 Business Logic Narrative
When the process 'Add Equipment Details Section' is invoked, and assuming that email header section has been created and equipment information is formatted, when the system adds equipment details to email content, the desired outcome is that equipment details section is added with car id and equipment type information.
💻 Technical Criteria
Given Email header section has been created and equipment information is formatted
When The system adds equipment details to email content
Then Equipment details section is added with car ID and equipment type information
R-GCX016E-cbl-03079 Add Station Information Section
Process Rules
📊 Business Logic Narrative
When the process 'Add Station Information Section' is invoked, and assuming that cargo information section has been added and station information is formatted, when the system adds station information to email content, the desired outcome is that station information section is added with origin and destination station details.
💻 Technical Criteria
Given Cargo information section has been added and station information is formatted
When The system adds station information to email content
Then Station information section is added with origin and destination station details
R-GCX016E-cbl-01238 Capture Current Cargo Status
Process Rules
📊 Business Logic Narrative
When the process 'Capture Current Cargo Status' is invoked, and assuming that a cargo record exists with status information, when debug logging is requested for status array processing, the desired outcome is that the system captures the current cargo status including rt10 and rt11 status codes.
💻 Technical Criteria
Given A cargo record exists with status information
When Debug logging is requested for status array processing
Then The system captures the current cargo status including RT10 and RT11 status codes
R-GCX016E-cbl-01239 Record RT10/RT11 Status Information
Process Rules
📊 Business Logic Narrative
When the process 'Record RT10/RT11 Status Information' is invoked, and assuming that cargo status information is available in rt10 and rt11 fields, when creating debug log entries for cargo status, the desired outcome is that the system records rt10 and rt11 status information for inclusion in debug output.
💻 Technical Criteria
Given Cargo status information is available in RT10 and RT11 fields
When Creating debug log entries for cargo status
Then The system records RT10 and RT11 status information for inclusion in debug output
R-GCX016E-cbl-01240 Log Cargo Quantities and Totals
Process Rules
📊 Business Logic Narrative
When the process 'Log Cargo Quantities and Totals' is invoked, and assuming that cargo record contains quantity information, when debug logging is performed for cargo status changes, the desired outcome is that the system logs cargo quantities and totals including released quantities.
💻 Technical Criteria
Given Cargo record contains quantity information
When Debug logging is performed for cargo status changes
Then The system logs cargo quantities and totals including released quantities
R-GCX016E-cbl-01242 Record All Disposition Codes
Process Rules
📊 Business Logic Narrative
When the process 'Record All Disposition Codes' is invoked, and assuming that cargo status array contains disposition codes, when creating debug log for status processing, the desired outcome is that the system records all disposition codes with their associated details.
💻 Technical Criteria
Given Cargo status array contains disposition codes
When Creating debug log for status processing
Then The system records all disposition codes with their associated details
R-GCX016E-cbl-01243 Create Before Processing Snapshot
Process Rules
📊 Business Logic Narrative
When the process 'Create Before Processing Snapshot' is invoked, and assuming that cargo status information exists before processing, when debug logging is enabled for status array changes, the desired outcome is that the system creates a before processing snapshot of all cargo status information.
💻 Technical Criteria
Given Cargo status information exists before processing
When Debug logging is enabled for status array changes
Then The system creates a before processing snapshot of all cargo status information
R-GCX016E-cbl-01244 Create After Processing Snapshot
Process Rules
📊 Business Logic Narrative
When the process 'Create After Processing Snapshot' is invoked, and assuming that cargo status processing has been completed, when debug logging is enabled for status array changes, the desired outcome is that the system creates an after processing snapshot of all cargo status information.
💻 Technical Criteria
Given Cargo status processing has been completed
When Debug logging is enabled for status array changes
Then The system creates an after processing snapshot of all cargo status information
R-GCX016E-cbl-01247 Include Equipment Information
Process Rules
📊 Business Logic Narrative
When the process 'Include Equipment Information' is invoked, and assuming that equipment information is available for the cargo, when formatting debug message content, the desired outcome is that the system includes equipment information such as car id and equipment details in the debug output.
💻 Technical Criteria
Given Equipment information is available for the cargo
When Formatting debug message content
Then The system includes equipment information such as car ID and equipment details in the debug output
R-GCX016E-cbl-01255 Route EXPORT Message
Decision Rules
📊 Business Logic Narrative
When the process 'Route EXPORT Message' is invoked, and assuming that a merlin message has been generated for an export transaction with equipment information, when the message type is export, the desired outcome is that the message should be routed based on equipment type routing rules.
💻 Technical Criteria
Given A Merlin message has been generated for an export transaction with equipment information
When The message type is EXPORT
Then The message should be routed based on equipment type routing rules
R-GCX016E-cbl-01270 Route EXPORT Messages
Decision Rules
📊 Business Logic Narrative
When the process 'Route EXPORT Messages' is invoked, and assuming that a message has been classified as export type, when the routing process evaluates the equipment type, the desired outcome is that the message is routed to destinations specific to the equipment type.
💻 Technical Criteria
Given A message has been classified as EXPORT type
When The routing process evaluates the equipment type
Then The message is routed to destinations specific to the equipment type
R-GCX016E-cbl-01299 Message Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Message Type?' is invoked, and assuming that a message needs to be processed for array initialization, when the system evaluates the message type, the desired outcome is that the system routes to cargo message array initialization for cargo messages or train message array initialization for train messages.
💻 Technical Criteria
Given A message needs to be processed for array initialization
When The system evaluates the message type
Then The system routes to cargo message array initialization for cargo messages or train message array initialization for train messages
R-GCX016E-cbl-01300 Initialize Cargo Message Arrays
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Cargo Message Arrays' is invoked, and assuming that a cargo message type has been identified, when the system initializes cargo message arrays, the desired outcome is that the system creates empty array structures ready to receive x4 and n7 segment information.
💻 Technical Criteria
Given A cargo message type has been identified
When The system initializes cargo message arrays
Then The system creates empty array structures ready to receive X4 and N7 segment information
R-GCX016E-cbl-01301 Create X4 Segment Structure
Definitional Rules
📊 Business Logic Narrative
When the process 'Create X4 Segment Structure' is invoked, and assuming that cargo message arrays are being initialized, when the system creates x4 segment structure, the desired outcome is that the system defines fields for disposition codes, entry numbers, quantities, and processing instructions.
💻 Technical Criteria
Given Cargo message arrays are being initialized
When The system creates X4 segment structure
Then The system defines fields for disposition codes, entry numbers, quantities, and processing instructions
R-GCX016E-cbl-01302 Set Equipment Information
Process Rules
📊 Business Logic Narrative
When the process 'Set Equipment Information' is invoked, and assuming that x4 segment structure has been created, when the system sets equipment information, the desired outcome is that the system assigns equipment type, equipment number, and related identification data to the x4 segment.
💻 Technical Criteria
Given X4 segment structure has been created
When The system sets equipment information
Then The system assigns equipment type, equipment number, and related identification data to the X4 segment
R-GCX016E-cbl-01303 Set Disposition Code Data
Process Rules
📊 Business Logic Narrative
When the process 'Set Disposition Code Data' is invoked, and assuming that equipment information has been set in the x4 segment, when the system sets disposition code data, the desired outcome is that the system populates disposition code, associated quantities, entry numbers, and processing flags.
💻 Technical Criteria
Given Equipment information has been set in the X4 segment
When The system sets disposition code data
Then The system populates disposition code, associated quantities, entry numbers, and processing flags
R-GCX016E-cbl-01305 Create N7 Segment Structure
Definitional Rules
📊 Business Logic Narrative
When the process 'Create N7 Segment Structure' is invoked, and assuming that x4 segment has been completed with date/time information, when the system creates n7 segment structure, the desired outcome is that the system defines fields for equipment details, cargo identification, and quantity information.
💻 Technical Criteria
Given X4 segment has been completed with date/time information
When The system creates N7 segment structure
Then The system defines fields for equipment details, cargo identification, and quantity information
R-GCX016E-cbl-01306 Set Equipment Details
Process Rules
📊 Business Logic Narrative
When the process 'Set Equipment Details' is invoked, and assuming that n7 segment structure has been created, when the system sets equipment details, the desired outcome is that the system assigns equipment initial, equipment number, equipment type, and equipment specifications to the n7 segment.
💻 Technical Criteria
Given N7 segment structure has been created
When The system sets equipment details
Then The system assigns equipment initial, equipment number, equipment type, and equipment specifications to the N7 segment
R-GCX016E-cbl-01307 Set Quantity Information
Process Rules
📊 Business Logic Narrative
When the process 'Set Quantity Information' is invoked, and assuming that equipment details have been set in the n7 segment, when the system sets quantity information, the desired outcome is that the system populates quantity values, unit of measure, and weight information in the n7 segment.
💻 Technical Criteria
Given Equipment details have been set in the N7 segment
When The system sets quantity information
Then The system populates quantity values, unit of measure, and weight information in the N7 segment
R-GCX016E-cbl-01309 Initialize Train Message Arrays
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Train Message Arrays' is invoked, and assuming that a train message type has been identified, when the system initializes train message arrays, the desired outcome is that the system creates empty array structures ready to receive m10 and v9 segment information.
💻 Technical Criteria
Given A train message type has been identified
When The system initializes train message arrays
Then The system creates empty array structures ready to receive M10 and V9 segment information
R-GCX016E-cbl-01322 Cargo Processing Action Occurs
Process Rules
📊 Business Logic Narrative
When the process 'Cargo Processing Action Occurs' is invoked, and assuming that a cargo processing action has been initiated, when the system detects a cargo processing event, the desired outcome is that the system should trigger the audit logging process.
💻 Technical Criteria
Given A cargo processing action has been initiated
When The system detects a cargo processing event
Then The system should trigger the audit logging process
R-GCX016E-cbl-01323 Prepare Audit Log Entry
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Audit Log Entry' is invoked, and assuming that a cargo processing action needs to be logged, when the audit logging process is initiated, the desired outcome is that the system should prepare the audit log entry structure with all required fields.
💻 Technical Criteria
Given A cargo processing action needs to be logged
When The audit logging process is initiated
Then The system should prepare the audit log entry structure with all required fields
R-GCX016E-cbl-01324 Set LOG-USE-INPUT-MESSAGE Action Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Set LOG-USE-INPUT-MESSAGE Action Code' is invoked, and assuming that an audit log entry is being prepared for cargo processing, when the system sets up the log entry parameters, the desired outcome is that the action code should be set to log-use-input-message.
💻 Technical Criteria
Given An audit log entry is being prepared for cargo processing
When The system sets up the log entry parameters
Then The action code should be set to LOG-USE-INPUT-MESSAGE
R-GCX016E-cbl-01327 Capture Cargo Processing Details
Validation Rules
📊 Business Logic Narrative
When the process 'Capture Cargo Processing Details' is invoked, and assuming that an audit log entry is being created for a cargo processing action, when the system captures audit information, the desired outcome is that the specific cargo processing details should be recorded in the log entry.
💻 Technical Criteria
Given An audit log entry is being created for a cargo processing action
When The system captures audit information
Then The specific cargo processing details should be recorded in the log entry
R-GCX016E-cbl-01331 Handle Logging Error
Process Rules
📊 Business Logic Narrative
When the process 'Handle Logging Error' is invoked, and assuming that the gct1051e transaction spawn failed, when the system processes the failed spawn result, the desired outcome is that the system should handle the logging error without interrupting cargo processing.
💻 Technical Criteria
Given The GCT1051E transaction spawn failed
When The system processes the failed spawn result
Then The system should handle the logging error without interrupting cargo processing
R-GCX016E-cbl-01332 Continue Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue Processing' is invoked, and assuming that the audit logging attempt has been completed (successfully or with error), when the logging process finishes, the desired outcome is that the system should continue with the main cargo processing workflow.
💻 Technical Criteria
Given The audit logging attempt has been completed (successfully or with error)
When The logging process finishes
Then The system should continue with the main cargo processing workflow
R-GCX016E-cbl-01333 Format Equipment Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment Information' is invoked, and assuming that a cargo record exists with equipment information, when the system processes merlin report formatting, the desired outcome is that equipment information is extracted and formatted for the report.
💻 Technical Criteria
Given A cargo record exists with equipment information
When The system processes Merlin report formatting
Then Equipment information is extracted and formatted for the report
R-GCX016E-cbl-01334 Extract Car ID
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Car ID' is invoked, and assuming that cargo data contains car identification information, when car id extraction is performed, the desired outcome is that the car id is retrieved and made available for report formatting.
💻 Technical Criteria
Given Cargo data contains car identification information
When Car ID extraction is performed
Then The car ID is retrieved and made available for report formatting
R-GCX016E-cbl-01349 Retrieve Current Cargo Release Quantity
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Cargo Release Quantity' is invoked, and assuming that a cargo record exists in the system, when the system needs to process disposition code quantity impacts, the desired outcome is that the current cargo release quantity is retrieved and made available for processing.
💻 Technical Criteria
Given A cargo record exists in the system
When The system needs to process disposition code quantity impacts
Then The current cargo release quantity is retrieved and made available for processing
R-GCX016E-cbl-01350 Get Disposition Code from Status Array
Action Rules
📊 Business Logic Narrative
When the process 'Get Disposition Code from Status Array' is invoked, and assuming that a cargo status array contains disposition codes, when the system processes quantity impacts for disposition codes, the desired outcome is that each disposition code is extracted from the status array for evaluation.
💻 Technical Criteria
Given A cargo status array contains disposition codes
When The system processes quantity impacts for disposition codes
Then Each disposition code is extracted from the status array for evaluation
R-GCX016E-cbl-01358 Validate Quantity Against Total Cargo
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Quantity Against Total Cargo' is invoked, and assuming that a release quantity has been calculated from disposition code processing, when the system validates the calculated quantity, the desired outcome is that the quantity must be between zero and the total cargo quantity inclusive.
💻 Technical Criteria
Given A release quantity has been calculated from disposition code processing
When The system validates the calculated quantity
Then The quantity must be between zero and the total cargo quantity inclusive
R-GCX016E-cbl-01360 Update Release Quantity
Action Rules
📊 Business Logic Narrative
When the process 'Update Release Quantity' is invoked, and assuming that a valid release quantity has been calculated, when the system updates the cargo release quantity, the desired outcome is that the cargo record is updated with the new release quantity value.
💻 Technical Criteria
Given A valid release quantity has been calculated
When The system updates the cargo release quantity
Then The cargo record is updated with the new release quantity value
R-GCX016E-cbl-01361 Generate Quantity Impact Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Quantity Impact Message' is invoked, and assuming that a cargo release quantity has been updated, when the system generates impact messaging, the desired outcome is that a message is created showing the before and after quantity values and the disposition code causing the change.
💻 Technical Criteria
Given A cargo release quantity has been updated
When The system generates impact messaging
Then A message is created showing the before and after quantity values and the disposition code causing the change
R-GCX016E-cbl-01365 Validate Input Date Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Input Date Format' is invoked, and assuming that a date input is required for cargo age calculation, when the system receives a date value for processing, the desired outcome is that the system validates the date format is correct and numeric before proceeding with conversion.
💻 Technical Criteria
Given A date input is required for cargo age calculation
When The system receives a date value for processing
Then The system validates the date format is correct and numeric before proceeding with conversion
R-GCX016E-cbl-01369 Calculate Days Since Base Date
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Days Since Base Date' is invoked, and assuming that a date has been successfully converted to julian format, when the system needs to determine cargo age, the desired outcome is that the system calculates the difference in days between the julian date and the established base date.
💻 Technical Criteria
Given A date has been successfully converted to Julian format
When The system needs to determine cargo age
Then The system calculates the difference in days between the Julian date and the established base date
R-GCX016E-cbl-01371 Cargo Age Calculation Required
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Age Calculation Required' is invoked, and assuming that cargo processing is being performed, when the system needs to determine cargo age for business rules, the desired outcome is that the system initiates date input processing for age calculation.
💻 Technical Criteria
Given Cargo processing is being performed
When The system needs to determine cargo age for business rules
Then The system initiates date input processing for age calculation
R-GCX016E-cbl-01401 Update Cargo Record with Station Info
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Record with Station Info' is invoked, and assuming that destination station data has been set, when the system updates the cargo record, the desired outcome is that the cargo record is updated with the destination station information.
💻 Technical Criteria
Given Destination station data has been set
When The system updates the cargo record
Then The cargo record is updated with the destination station information
R-GCX016E-cbl-01402 Log Station Processing Success
Process Rules
📊 Business Logic Narrative
When the process 'Log Station Processing Success' is invoked, and assuming that cargo record has been updated with station information, when the system completes station processing, the desired outcome is that a success log entry is created for station processing.
💻 Technical Criteria
Given Cargo record has been updated with station information
When The system completes station processing
Then A success log entry is created for station processing
R-GCX016E-cbl-01408 Extract Location Identifier from X4 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Location Identifier from X4 Segment' is invoked, and assuming that an x4 segment contains cargo disposition data with location information, when the system processes the x4 segment for key station lookup, the desired outcome is that the location identifier is extracted from the x4 segment data.
💻 Technical Criteria
Given An X4 segment contains cargo disposition data with location information
When The system processes the X4 segment for key station lookup
Then The location identifier is extracted from the X4 segment data
R-GCX016E-cbl-01421 Start N9 Reference Information Retrieval
Process Rules
📊 Business Logic Narrative
When the process 'Start N9 Reference Information Retrieval' is invoked, and assuming that a cargo processing request is received, when the system begins n9 reference information retrieval, the desired outcome is that the n9 reference retrieval process is initiated.
💻 Technical Criteria
Given A cargo processing request is received
When The system begins N9 reference information retrieval
Then The N9 reference retrieval process is initiated
R-GCX016E-cbl-01422 Identify Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Identify Cargo Record' is invoked, and assuming that n9 reference retrieval process has been initiated, when the system needs to locate the target cargo record, the desired outcome is that the cargo record is identified using the cargo key information.
💻 Technical Criteria
Given N9 reference retrieval process has been initiated
When The system needs to locate the target cargo record
Then The cargo record is identified using the cargo key information
R-GCX016E-cbl-01423 Access Cargo Segments Database
Action Rules
📊 Business Logic Narrative
When the process 'Access Cargo Segments Database' is invoked, and assuming that the cargo record has been identified, when the system needs to access n9 reference segments, the desired outcome is that the gcsuss02 cargo segments database is accessed.
💻 Technical Criteria
Given The cargo record has been identified
When The system needs to access N9 reference segments
Then The GCSUSS02 cargo segments database is accessed
R-GCX016E-cbl-01424 N9 Segments Available?
Decision Rules
📊 Business Logic Narrative
When the process 'N9 Segments Available?' is invoked, and assuming that the cargo segments database has been accessed, when the system searches for n9 segments for the cargo, the desired outcome is that the system determines if n9 segments are available or not available.
💻 Technical Criteria
Given The cargo segments database has been accessed
When The system searches for N9 segments for the cargo
Then The system determines if N9 segments are available or not available
R-GCX016E-cbl-01425 Retrieve N9 Reference Numbers
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve N9 Reference Numbers' is invoked, and assuming that n9 segments are available for the cargo, when the system processes the available n9 segments, the desired outcome is that all n9 reference numbers are retrieved from the segments.
💻 Technical Criteria
Given N9 segments are available for the cargo
When The system processes the available N9 segments
Then All N9 reference numbers are retrieved from the segments
R-GCX016E-cbl-01432 Update Cargo Record with References
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo Record with References' is invoked, and assuming that reference data has been stored in working storage, when the system updates the cargo record, the desired outcome is that the cargo record is updated with all processed n9 reference information.
💻 Technical Criteria
Given Reference data has been stored in working storage
When The system updates the cargo record
Then The cargo record is updated with all processed N9 reference information
R-GCX016E-cbl-01434 Extract Equipment ID from US Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment ID from US Cargo Record' is invoked, and assuming that a us cargo record exists with equipment information, when the system processes the cargo for cross-border tracking, the desired outcome is that the equipment id is extracted from the cargo record for canadian cargo lookup.
💻 Technical Criteria
Given A US cargo record exists with equipment information
When The system processes the cargo for cross-border tracking
Then The equipment ID is extracted from the cargo record for Canadian cargo lookup
R-GCX016E-cbl-01435 Search Canadian Cargo Database GCCC-CARGO-ROOT
Action Rules
📊 Business Logic Narrative
When the process 'Search Canadian Cargo Database GCCC-CARGO-ROOT' is invoked, and assuming that an equipment id has been extracted from the us cargo record, when the system searches the canadian cargo database gccc-cargo-root, the desired outcome is that the system retrieves any canadian cargo records that match the equipment id.
💻 Technical Criteria
Given An equipment ID has been extracted from the US cargo record
When The system searches the Canadian cargo database GCCC-CARGO-ROOT
Then The system retrieves any Canadian cargo records that match the equipment ID
R-GCX016E-cbl-01436 Canadian Cargo Record Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Canadian Cargo Record Found?' is invoked, and assuming that a search has been performed in the canadian cargo database, when the system evaluates the search results, the desired outcome is that if a canadian cargo record is found, proceed to status validation; otherwise, log no canadian cargo found and continue processing.
💻 Technical Criteria
Given A search has been performed in the Canadian cargo database
When The system evaluates the search results
Then If a Canadian cargo record is found, proceed to status validation; otherwise, log no Canadian cargo found and continue processing
R-GCX016E-cbl-01437 Validate Canadian Cargo Status
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Canadian Cargo Status' is invoked, and assuming that a canadian cargo record has been found, when the system validates the cargo status, the desired outcome is that the cargo status is checked to ensure it is valid for processing and not in an excluded state.
💻 Technical Criteria
Given A Canadian cargo record has been found
When The system validates the cargo status
Then The cargo status is checked to ensure it is valid for processing and not in an excluded state
R-GCX016E-cbl-01438 Status Valid for Processing?
Decision Rules
📊 Business Logic Narrative
When the process 'Status Valid for Processing?' is invoked, and assuming that a canadian cargo record status has been validated, when the system evaluates processing eligibility, the desired outcome is that if status is valid, proceed to equipment id matching; if status is deleted or new bond created, skip the record and continue processing.
💻 Technical Criteria
Given A Canadian cargo record status has been validated
When The system evaluates processing eligibility
Then If status is valid, proceed to equipment ID matching; if status is deleted or new bond created, skip the record and continue processing
R-GCX016E-cbl-01439 Match Equipment IDs Between Systems
Process Rules
📊 Business Logic Narrative
When the process 'Match Equipment IDs Between Systems' is invoked, and assuming that a valid canadian cargo record exists for processing, when the system matches equipment ids between us and canadian systems, the desired outcome is that equipment ids are compared and validated for creating cross-border tracking links.
💻 Technical Criteria
Given A valid Canadian cargo record exists for processing
When The system matches equipment IDs between US and Canadian systems
Then Equipment IDs are compared and validated for creating cross-border tracking links
R-GCX016E-cbl-01440 Create Cross-Border Tracking Link
Process Rules
📊 Business Logic Narrative
When the process 'Create Cross-Border Tracking Link' is invoked, and assuming that equipment ids have been successfully matched between systems, when the system creates cross-border tracking links, the desired outcome is that a tracking relationship is established between the us and canadian cargo records.
💻 Technical Criteria
Given Equipment IDs have been successfully matched between systems
When The system creates cross-border tracking links
Then A tracking relationship is established between the US and Canadian cargo records
R-GCX016E-cbl-01441 Update Cargo with Canadian Reference
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo with Canadian Reference' is invoked, and assuming that a cross-border tracking link has been created, when the system updates the us cargo record, the desired outcome is that the us cargo record is updated with canadian cargo reference information for cross-border tracking.
💻 Technical Criteria
Given A cross-border tracking link has been created
When The system updates the US cargo record
Then The US cargo record is updated with Canadian cargo reference information for cross-border tracking
R-GCX016E-cbl-01442 Log Canadian Cargo Match Found
Process Rules
📊 Business Logic Narrative
When the process 'Log Canadian Cargo Match Found' is invoked, and assuming that a canadian cargo record has been successfully matched and linked, when the system completes the cross-border linking process, the desired outcome is that a log entry is created documenting the successful canadian cargo match.
💻 Technical Criteria
Given A Canadian cargo record has been successfully matched and linked
When The system completes the cross-border linking process
Then A log entry is created documenting the successful Canadian cargo match
R-GCX016E-cbl-01443 Log No Canadian Cargo Found
Process Rules
📊 Business Logic Narrative
When the process 'Log No Canadian Cargo Found' is invoked, and assuming that no canadian cargo record is found for the equipment id, when the system completes the canadian cargo search, the desired outcome is that a log entry is created documenting that no canadian cargo was found and processing continues.
💻 Technical Criteria
Given No Canadian cargo record is found for the equipment ID
When The system completes the Canadian cargo search
Then A log entry is created documenting that no Canadian cargo was found and processing continues
R-GCX016E-cbl-01444 Skip Deleted/Invalid Records
Policy Rules
📊 Business Logic Narrative
When the process 'Skip Deleted/Invalid Records' is invoked, and assuming that a canadian cargo record is found but has deleted or new bond created status, when the system evaluates the record for processing, the desired outcome is that the record is skipped and excluded from cross-border tracking, and processing continues with the next record.
💻 Technical Criteria
Given A Canadian cargo record is found but has deleted or new bond created status
When The system evaluates the record for processing
Then The record is skipped and excluded from cross-border tracking, and processing continues with the next record
R-GCX016E-cbl-01445 Multi-Manifest Scenario?
Decision Rules
📊 Business Logic Narrative
When the process 'Multi-Manifest Scenario?' is invoked, and assuming that a cargo processing transaction is being executed, when the system evaluates whether multiple manifests are involved in the current transaction, the desired outcome is that the system determines if follower manifest processing is required and routes accordingly.
💻 Technical Criteria
Given A cargo processing transaction is being executed
When The system evaluates whether multiple manifests are involved in the current transaction
Then The system determines if follower manifest processing is required and routes accordingly
R-GCX016E-cbl-01463 Cargo Not Found Error
Validation Rules
📊 Business Logic Narrative
When the process 'Cargo Not Found Error' is invoked, and assuming that x4 and n7 segments specify cargo identification information, when cargo lookup fails to find matching cargo records in the database, the desired outcome is that generate cargo not found error message, log the missing cargo information, and continue processing other cargos.
💻 Technical Criteria
Given X4 and N7 segments specify cargo identification information
When Cargo lookup fails to find matching cargo records in the database
Then Generate cargo not found error message, log the missing cargo information, and continue processing other cargos
R-GCX016E-cbl-01465 Generate Merlin Error Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Merlin Error Message' is invoked, and assuming that an error condition has been detected during message processing, when error information needs to be communicated to business users, the desired outcome is that format error message with relevant business context (train id, cargo information, disposition codes) and route to merlin system.
💻 Technical Criteria
Given An error condition has been detected during message processing
When Error information needs to be communicated to business users
Then Format error message with relevant business context (train ID, cargo information, disposition codes) and route to Merlin system
R-GCX016E-cbl-01469 Continue Processing or Terminate
Decision Rules
📊 Business Logic Narrative
When the process 'Continue Processing or Terminate' is invoked, and assuming that an error has been detected and appropriate error handling has been performed, when decision is needed on whether to continue processing remaining messages/segments, the desired outcome is that continue processing for non-critical errors (train not found, cargo not found) or terminate for critical system errors (database failures, mq errors).
💻 Technical Criteria
Given An error has been detected and appropriate error handling has been performed
When Decision is needed on whether to continue processing remaining messages/segments
Then Continue processing for non-critical errors (train not found, cargo not found) or terminate for critical system errors (database failures, MQ errors)
R-GCX016E-cbl-01470 Reroute Message with Error Notification
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Reroute Message with Error Notification', assuming that a business-level error has occurred (train not found, cargo not found, invalid disposition code), when original message routing cannot be completed due to the error, the desired outcome is that reroute message to backup recipients with error notification explaining the business issue.
💻 Technical Criteria
EXCLUDING A business-level error has occurred (train not found, cargo not found, invalid disposition code)
When Original message routing cannot be completed due to the error
Then Reroute message to backup recipients with error notification explaining the business issue
R-GCX016E-cbl-01471 Create Debug Log Entry
Process Rules
📊 Business Logic Narrative
When the process 'Create Debug Log Entry' is invoked, and assuming that error handling is in progress and debug logging is enabled, when detailed troubleshooting information is needed for business rule analysis, the desired outcome is that create debug log entries showing before/after status arrays, disposition codes, and cargo status changes.
💻 Technical Criteria
Given Error handling is in progress and debug logging is enabled
When Detailed troubleshooting information is needed for business rule analysis
Then Create debug log entries showing before/after status arrays, disposition codes, and cargo status changes
R-GCX016E-cbl-01486 Extract Equipment ID from VID Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment ID from VID Segment' is invoked, and assuming that a vid segment has been received for equipment hold processing, when the system processes the vid segment, the desired outcome is that the equipment id is extracted from the vid segment data.
💻 Technical Criteria
Given A VID segment has been received for equipment hold processing
When The system processes the VID segment
Then The equipment ID is extracted from the VID segment data
R-GCX016E-cbl-01487 Validate Equipment ID Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Equipment ID Format' is invoked, and assuming that an equipment id has been extracted from a vid segment, when the system validates the equipment id format, the desired outcome is that the equipment id format is checked against validation criteria.
💻 Technical Criteria
Given An equipment ID has been extracted from a VID segment
When The system validates the equipment ID format
Then The equipment ID format is checked against validation criteria
R-GCX016E-cbl-01488 Equipment ID Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment ID Valid?' is invoked, and assuming that an equipment id format has been validated, when the system checks equipment id validity, the desired outcome is that if equipment id is invalid, generate invalid equipment id error, otherwise proceed to locate equipment in train.
💻 Technical Criteria
Given An equipment ID format has been validated
When The system checks equipment ID validity
Then If equipment ID is invalid, generate invalid equipment ID error, otherwise proceed to locate equipment in train
R-GCX016E-cbl-01489 Locate Equipment in Train Consist
Process Rules
📊 Business Logic Narrative
When the process 'Locate Equipment in Train Consist' is invoked, and assuming that a valid equipment id has been confirmed, when the system searches for the equipment in the train consist, the desired outcome is that the equipment is located within the train's equipment list.
💻 Technical Criteria
Given A valid equipment ID has been confirmed
When The system searches for the equipment in the train consist
Then The equipment is located within the train's equipment list
R-GCX016E-cbl-01490 Equipment Found in Train?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment Found in Train?' is invoked, and assuming that the system has searched for equipment in the train consist, when the equipment search is completed, the desired outcome is that if equipment is not found in train, generate equipment not found error, otherwise check current equipment status.
💻 Technical Criteria
Given The system has searched for equipment in the train consist
When The equipment search is completed
Then If equipment is not found in train, generate equipment not found error, otherwise check current equipment status
R-GCX016E-cbl-01491 Check Current Equipment Status
Process Rules
📊 Business Logic Narrative
When the process 'Check Current Equipment Status' is invoked, and assuming that equipment has been found in the train consist, when the system checks the current equipment status, the desired outcome is that the current hold status of the equipment is retrieved.
💻 Technical Criteria
Given Equipment has been found in the train consist
When The system checks the current equipment status
Then The current hold status of the equipment is retrieved
R-GCX016E-cbl-01492 Equipment Already Held?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment Already Held?' is invoked, and assuming that the current equipment status has been checked, when the system evaluates the equipment hold status, the desired outcome is that if equipment is already held, generate already held warning, otherwise apply hold status to equipment.
💻 Technical Criteria
Given The current equipment status has been checked
When The system evaluates the equipment hold status
Then If equipment is already held, generate already held warning, otherwise apply hold status to equipment
R-GCX016E-cbl-01493 Apply Hold Status to Equipment
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Apply Hold Status to Equipment', assuming that equipment is not currently held, when the system applies hold status to the equipment, the desired outcome is that the equipment hold status is set.
💻 Technical Criteria
EXCLUDING Equipment is not currently held
When The system applies hold status to the equipment
Then The equipment hold status is set
R-GCX016E-cbl-01494 Update Equipment Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Update Equipment Status Flags' is invoked, and assuming that hold status has been applied to equipment, when the system updates equipment status flags, the desired outcome is that equipment status flags are updated to reflect held status.
💻 Technical Criteria
Given Hold status has been applied to equipment
When The system updates equipment status flags
Then Equipment status flags are updated to reflect held status
R-GCX016E-cbl-01495 Increment Train Hold Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment Train Hold Counter' is invoked, and assuming that equipment status flags have been updated, when the system increments the train hold counter, the desired outcome is that the train hold counter is increased by one.
💻 Technical Criteria
Given Equipment status flags have been updated
When The system increments the train hold counter
Then The train hold counter is increased by one
R-GCX016E-cbl-01496 Log Equipment Hold Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Equipment Hold Action' is invoked, and assuming that train hold counter has been incremented, when the system logs the equipment hold action, the desired outcome is that a log entry is created documenting the equipment hold with timestamp and equipment details.
💻 Technical Criteria
Given Train hold counter has been incremented
When The system logs the equipment hold action
Then A log entry is created documenting the equipment hold with timestamp and equipment details
R-GCX016E-cbl-01497 Generate Hold Confirmation Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Hold Confirmation Message' is invoked, and assuming that equipment hold action has been logged, when the system generates hold confirmation message, the desired outcome is that a confirmation message is created indicating successful equipment hold.
💻 Technical Criteria
Given Equipment hold action has been logged
When The system generates hold confirmation message
Then A confirmation message is created indicating successful equipment hold
R-GCX016E-cbl-01498 Update Train Equipment List
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Equipment List' is invoked, and assuming that hold confirmation message has been generated, when the system updates the train equipment list, the desired outcome is that the train equipment list is updated with the equipment's new held status.
💻 Technical Criteria
Given Hold confirmation message has been generated
When The system updates the train equipment list
Then The train equipment list is updated with the equipment's new held status
R-GCX016E-cbl-01499 Generate Equipment Not Found Error
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Equipment Not Found Error', assuming that equipment search in train consist has been completed, when equipment is not found in the train, the desired outcome is that an equipment not found error message is generated.
💻 Technical Criteria
EXCLUDING Equipment search in train consist has been completed
When Equipment is not found in the train
Then An equipment not found error message is generated
R-GCX016E-cbl-01500 Generate Invalid Equipment ID Error
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Invalid Equipment ID Error', assuming that equipment id format validation has been performed, when equipment id is determined to be invalid, the desired outcome is that an invalid equipment id error message is generated.
💻 Technical Criteria
EXCLUDING Equipment ID format validation has been performed
When Equipment ID is determined to be invalid
Then An invalid equipment ID error message is generated
R-GCX016E-cbl-01501 Generate Already Held Warning
Action Rules
📊 Business Logic Narrative
When the process 'Generate Already Held Warning' is invoked, and assuming that equipment hold status has been evaluated, when equipment is already in held status, the desired outcome is that an already held warning message is generated.
💻 Technical Criteria
Given Equipment hold status has been evaluated
When Equipment is already in held status
Then An already held warning message is generated
R-GCX016E-cbl-01502 Extract Equipment ID from VID Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment ID from VID Segment' is invoked, and assuming that a vid segment is received for equipment release processing, when the system processes the vid segment, the desired outcome is that the equipment id is extracted from the vid segment data.
💻 Technical Criteria
Given A VID segment is received for equipment release processing
When The system processes the VID segment
Then The equipment ID is extracted from the VID segment data
R-GCX016E-cbl-01503 Equipment Found in Train?
Validation Rules
📊 Business Logic Narrative
When the process 'Equipment Found in Train?' is invoked, and assuming that an equipment id has been extracted from vid segment, when the system searches for the equipment in the train equipment list, the desired outcome is that the system determines if the equipment exists in the train or generates equipment not found error.
💻 Technical Criteria
Given An equipment ID has been extracted from VID segment
When The system searches for the equipment in the train equipment list
Then The system determines if the equipment exists in the train or generates equipment not found error
R-GCX016E-cbl-01504 Valid Release Request?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid Release Request?' is invoked, and assuming that equipment exists in the train and release request data is available, when the system validates the release request parameters, the desired outcome is that the system determines if the release request is valid or generates invalid release request error.
💻 Technical Criteria
Given Equipment exists in the train and release request data is available
When The system validates the release request parameters
Then The system determines if the release request is valid or generates invalid release request error
R-GCX016E-cbl-01505 Equipment Currently Held?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment Currently Held?' is invoked, and assuming that a valid release request exists for equipment found in train, when the system checks the current hold status of the equipment, the desired outcome is that the system determines if equipment is held or generates warning for equipment not held.
💻 Technical Criteria
Given A valid release request exists for equipment found in train
When The system checks the current hold status of the equipment
Then The system determines if equipment is held or generates warning for equipment not held
R-GCX016E-cbl-01506 Process Equipment Release
Process Rules
📊 Business Logic Narrative
When the process 'Process Equipment Release' is invoked, and assuming that equipment is currently held and release request is valid, when the system processes the equipment release, the desired outcome is that the equipment release is processed and hold counter is decremented.
💻 Technical Criteria
Given Equipment is currently held and release request is valid
When The system processes the equipment release
Then The equipment release is processed and hold counter is decremented
R-GCX016E-cbl-01507 Decrement Hold Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Decrement Hold Counter' is invoked, and assuming that equipment release is being processed, when the system updates the hold counter, the desired outcome is that the hold counter is decremented by one.
💻 Technical Criteria
Given Equipment release is being processed
When The system updates the hold counter
Then The hold counter is decremented by one
R-GCX016E-cbl-01508 Hold Counter = 0?
Decision Rules
📊 Business Logic Narrative
When the process 'Hold Counter = 0?' is invoked, and assuming that hold counter has been decremented for equipment release, when the system checks the hold counter value, the desired outcome is that the system determines if hold counter equals zero to set equipment status to released.
💻 Technical Criteria
Given Hold counter has been decremented for equipment release
When The system checks the hold counter value
Then The system determines if hold counter equals zero to set equipment status to released
R-GCX016E-cbl-01509 Set Equipment Status to Released
Action Rules
📊 Business Logic Narrative
When the process 'Set Equipment Status to Released' is invoked, and assuming that hold counter equals zero after decrement, when the system updates equipment status, the desired outcome is that the equipment status is set to released.
💻 Technical Criteria
Given Hold counter equals zero after decrement
When The system updates equipment status
Then The equipment status is set to released
R-GCX016E-cbl-01510 Update Equipment Status in Train List
Action Rules
📊 Business Logic Narrative
When the process 'Update Equipment Status in Train List' is invoked, and assuming that equipment status has been processed for release, when the system updates the train equipment list, the desired outcome is that the equipment status is updated in the train list.
💻 Technical Criteria
Given Equipment status has been processed for release
When The system updates the train equipment list
Then The equipment status is updated in the train list
R-GCX016E-cbl-01511 Log Equipment Release Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Equipment Release Action' is invoked, and assuming that equipment status has been updated in train list, when the system logs the release action, the desired outcome is that the equipment release action is logged with relevant details.
💻 Technical Criteria
Given Equipment status has been updated in train list
When The system logs the release action
Then The equipment release action is logged with relevant details
R-GCX016E-cbl-01512 Generate Equipment Release Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Equipment Release Notification' is invoked, and assuming that equipment release action has been logged, when the system generates release notification, the desired outcome is that an equipment release notification is generated.
💻 Technical Criteria
Given Equipment release action has been logged
When The system generates release notification
Then An equipment release notification is generated
R-GCX016E-cbl-01513 Update Train Equipment Status Flags
Process Rules
📊 Business Logic Narrative
When the process 'Update Train Equipment Status Flags' is invoked, and assuming that equipment release notification has been generated, when the system updates train equipment status flags, the desired outcome is that the train equipment status flags are updated to reflect current equipment states.
💻 Technical Criteria
Given Equipment release notification has been generated
When The system updates train equipment status flags
Then The train equipment status flags are updated to reflect current equipment states
R-GCX016E-cbl-01514 All Equipment in Train Released?
Decision Rules
📊 Business Logic Narrative
When the process 'All Equipment in Train Released?' is invoked, and assuming that train equipment status flags have been updated, when the system checks if all equipment in train is released, the desired outcome is that the system determines if all equipment is released or if some equipment remains held.
💻 Technical Criteria
Given Train equipment status flags have been updated
When The system checks if all equipment in train is released
Then The system determines if all equipment is released or if some equipment remains held
R-GCX016E-cbl-01515 Update Overall Train Status
Action Rules
📊 Business Logic Narrative
When the process 'Update Overall Train Status' is invoked, and assuming that all equipment in the train has been released, when the system updates overall train status, the desired outcome is that the overall train status is updated to reflect that all equipment is released.
💻 Technical Criteria
Given All equipment in the train has been released
When The system updates overall train status
Then The overall train status is updated to reflect that all equipment is released
R-GCX016E-cbl-01516 Send Release Confirmation Message
Action Rules
📊 Business Logic Narrative
When the process 'Send Release Confirmation Message' is invoked, and assuming that equipment release processing is complete and train status is updated, when the system sends release confirmation, the desired outcome is that a release confirmation message is sent.
💻 Technical Criteria
Given Equipment release processing is complete and train status is updated
When The system sends release confirmation
Then A release confirmation message is sent
R-GCX016E-cbl-01517 Generate Error - Equipment Not Found
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error - Equipment Not Found', assuming that equipment id has been extracted from vid segment, when equipment is not found in the train equipment list, the desired outcome is that an equipment not found error is generated.
💻 Technical Criteria
EXCLUDING Equipment ID has been extracted from VID segment
When Equipment is not found in the train equipment list
Then An equipment not found error is generated
R-GCX016E-cbl-01518 Generate Error - Invalid Release Request
Action Rules
📊 Business Logic Narrative
When the process 'Generate Error - Invalid Release Request' is invoked, and assuming that equipment exists in train but release request validation is performed, when release request validation fails, the desired outcome is that an invalid release request error is generated.
💻 Technical Criteria
Given Equipment exists in train but release request validation is performed
When Release request validation fails
Then An invalid release request error is generated
R-GCX016E-cbl-01519 Generate Warning - Equipment Not Held
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Warning - Equipment Not Held', assuming that valid release request exists for equipment found in train, when equipment is not currently in held status, the desired outcome is that a warning is generated indicating equipment is not held.
💻 Technical Criteria
EXCLUDING Valid release request exists for equipment found in train
When Equipment is not currently in held status
Then A warning is generated indicating equipment is not held
R-GCX016E-cbl-01520 VID Segment Received
Process Rules
📊 Business Logic Narrative
When the process 'VID Segment Received' is invoked, and assuming that a vid segment is received in the message queue, when the system processes the vid segment, the desired outcome is that the equipment id is extracted from the vid segment for further processing.
💻 Technical Criteria
Given A VID segment is received in the message queue
When The system processes the VID segment
Then The equipment ID is extracted from the VID segment for further processing
R-GCX016E-cbl-01521 Extract Equipment ID from VID Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment ID from VID Segment' is invoked, and assuming that a vid segment contains equipment identification data, when the system processes the vid segment, the desired outcome is that the equipment id is extracted and made available for validation.
💻 Technical Criteria
Given A VID segment contains equipment identification data
When The system processes the VID segment
Then The equipment ID is extracted and made available for validation
R-GCX016E-cbl-01523 Validate Equipment ID Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Equipment ID Format' is invoked, and assuming that an equipment id has been extracted from vid segment and disposition code is sei, when the system validates the equipment id format, the desired outcome is that the equipment id format is checked against validation rules.
💻 Technical Criteria
Given An equipment ID has been extracted from VID segment and disposition code is SEI
When The system validates the equipment ID format
Then The equipment ID format is checked against validation rules
R-GCX016E-cbl-01524 Equipment ID Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment ID Valid?' is invoked, and assuming that equipment id format validation has been performed, when the system evaluates validation results, the desired outcome is that if equipment id is valid, proceed to locate equipment in train, otherwise generate invalid equipment id error.
💻 Technical Criteria
Given Equipment ID format validation has been performed
When The system evaluates validation results
Then If equipment ID is valid, proceed to locate equipment in train, otherwise generate invalid equipment ID error
R-GCX016E-cbl-01525 Locate Equipment in Train Consist
Process Rules
📊 Business Logic Narrative
When the process 'Locate Equipment in Train Consist' is invoked, and assuming that equipment id is valid and formatted correctly, when the system searches the train consist, the desired outcome is that the system attempts to locate the equipment within the train's equipment list.
💻 Technical Criteria
Given Equipment ID is valid and formatted correctly
When The system searches the train consist
Then The system attempts to locate the equipment within the train's equipment list
R-GCX016E-cbl-01526 Equipment Found in Train?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment Found in Train?' is invoked, and assuming that equipment location search has been completed, when the system evaluates search results, the desired outcome is that if equipment is found in train, proceed to check current status, otherwise generate equipment not found error.
💻 Technical Criteria
Given Equipment location search has been completed
When The system evaluates search results
Then If equipment is found in train, proceed to check current status, otherwise generate equipment not found error
R-GCX016E-cbl-01527 Check Current Equipment Status
Process Rules
📊 Business Logic Narrative
When the process 'Check Current Equipment Status' is invoked, and assuming that equipment has been found in the train consist, when the system checks equipment status, the desired outcome is that the current seizure status of the equipment is retrieved and evaluated.
💻 Technical Criteria
Given Equipment has been found in the train consist
When The system checks equipment status
Then The current seizure status of the equipment is retrieved and evaluated
R-GCX016E-cbl-01528 Equipment Already Seized?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment Already Seized?' is invoked, and assuming that current equipment status has been retrieved, when the system evaluates seizure status, the desired outcome is that if equipment is not already seized, proceed with seizure, otherwise generate already seized warning.
💻 Technical Criteria
Given Current equipment status has been retrieved
When The system evaluates seizure status
Then If equipment is not already seized, proceed with seizure, otherwise generate already seized warning
R-GCX016E-cbl-01529 Set Equipment Seizure Flag
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Equipment Seizure Flag', assuming that equipment is found in train and not already seized, when the system processes seizure request, the desired outcome is that the equipment seizure flag is set to indicate seized status.
💻 Technical Criteria
EXCLUDING Equipment is found in train and not already seized
When The system processes seizure request
Then The equipment seizure flag is set to indicate seized status
R-GCX016E-cbl-01530 Update Equipment Status in Train List
Action Rules
📊 Business Logic Narrative
When the process 'Update Equipment Status in Train List' is invoked, and assuming that equipment seizure flag has been set, when the system updates train records, the desired outcome is that the equipment status in the train list is updated to reflect seized status.
💻 Technical Criteria
Given Equipment seizure flag has been set
When The system updates train records
Then The equipment status in the train list is updated to reflect seized status
R-GCX016E-cbl-01531 Log Equipment Seizure Action
Action Rules
📊 Business Logic Narrative
When the process 'Log Equipment Seizure Action' is invoked, and assuming that equipment status has been updated in train list, when the system performs logging, the desired outcome is that a log entry is created documenting the equipment seizure action with relevant details.
💻 Technical Criteria
Given Equipment status has been updated in train list
When The system performs logging
Then A log entry is created documenting the equipment seizure action with relevant details
R-GCX016E-cbl-01532 Generate Equipment Seizure Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Equipment Seizure Notification' is invoked, and assuming that equipment seizure action has been logged, when the system generates notifications, the desired outcome is that seizure notification messages are created and sent to appropriate recipients.
💻 Technical Criteria
Given Equipment seizure action has been logged
When The system generates notifications
Then Seizure notification messages are created and sent to appropriate recipients
R-GCX016E-cbl-01533 Update Train Equipment Counter
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Equipment Counter' is invoked, and assuming that equipment seizure notification has been generated, when the system updates counters, the desired outcome is that train equipment counters are updated to reflect the newly seized equipment.
💻 Technical Criteria
Given Equipment seizure notification has been generated
When The system updates counters
Then Train equipment counters are updated to reflect the newly seized equipment
R-GCX016E-cbl-01534 Process Complete - Equipment Seized
Process Rules
📊 Business Logic Narrative
When the process 'Process Complete - Equipment Seized' is invoked, and assuming that all seizure processing steps have been completed successfully, when the system finalizes processing, the desired outcome is that the equipment seizure process is marked as complete.
💻 Technical Criteria
Given All seizure processing steps have been completed successfully
When The system finalizes processing
Then The equipment seizure process is marked as complete
R-GCX016E-cbl-01535 Generate Error - Invalid Equipment ID
Action Rules
📊 Business Logic Narrative
When the process 'Generate Error - Invalid Equipment ID' is invoked, and assuming that equipment id format validation has failed, when the system handles validation failure, the desired outcome is that an error message is generated indicating invalid equipment id format.
💻 Technical Criteria
Given Equipment ID format validation has failed
When The system handles validation failure
Then An error message is generated indicating invalid equipment ID format
R-GCX016E-cbl-01536 Generate Error - Equipment Not Found
Action Rules
📊 Business Logic Narrative
When the process 'Generate Error - Equipment Not Found' is invoked, and assuming that equipment search in train consist has failed to locate the specified equipment, when the system handles search failure, the desired outcome is that an error message is generated indicating equipment not found in train.
💻 Technical Criteria
Given Equipment search in train consist has failed to locate the specified equipment
When The system handles search failure
Then An error message is generated indicating equipment not found in train
R-GCX016E-cbl-01537 Generate Warning - Equipment Already Seized
Action Rules
📊 Business Logic Narrative
When the process 'Generate Warning - Equipment Already Seized' is invoked, and assuming that equipment is found but already has seized status, when the system detects duplicate seizure attempt, the desired outcome is that a warning message is generated indicating equipment is already seized.
💻 Technical Criteria
Given Equipment is found but already has seized status
When The system detects duplicate seizure attempt
Then A warning message is generated indicating equipment is already seized
R-GCX016E-cbl-01538 Validate Equipment ID in VID Segment
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Equipment ID in VID Segment' is invoked, and assuming that a vid segment is received with ser disposition code, when the system processes the vid segment equipment id field, the desired outcome is that the equipment id must be validated for proper format and non-blank content.
💻 Technical Criteria
Given A VID segment is received with SER disposition code
When The system processes the VID segment equipment ID field
Then The equipment ID must be validated for proper format and non-blank content
R-GCX016E-cbl-01539 Lookup Equipment in Train Consist
Validation Rules
📊 Business Logic Narrative
When the process 'Lookup Equipment in Train Consist' is invoked, and assuming that a valid equipment id from vid segment, when the system searches the train equipment consist, the desired outcome is that the equipment must be found in the train's equipment list to proceed with seizure release.
💻 Technical Criteria
Given A valid equipment ID from VID segment
When The system searches the train equipment consist
Then The equipment must be found in the train's equipment list to proceed with seizure release
R-GCX016E-cbl-01540 Check Current Seizure Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check Current Seizure Status' is invoked, and assuming that equipment is found in the train consist, when the system checks the equipment's current seizure status flags, the desired outcome is that the equipment must currently be in seized status to allow seizure release.
💻 Technical Criteria
Given Equipment is found in the train consist
When The system checks the equipment's current seizure status flags
Then The equipment must currently be in seized status to allow seizure release
R-GCX016E-cbl-01541 Remove Seizure Status from Equipment
Action Rules
📊 Business Logic Narrative
When the process 'Remove Seizure Status from Equipment' is invoked, and assuming that equipment is currently seized and seizure release is authorized, when the system processes the seizure release request, the desired outcome is that the seizure status flag must be removed from the equipment record.
💻 Technical Criteria
Given Equipment is currently seized and seizure release is authorized
When The system processes the seizure release request
Then The seizure status flag must be removed from the equipment record
R-GCX016E-cbl-01542 Update Equipment Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Update Equipment Status Flags' is invoked, and assuming that equipment seizure status has been removed, when the system updates equipment status information, the desired outcome is that all equipment status flags must be updated to reflect the released from seizure state.
💻 Technical Criteria
Given Equipment seizure status has been removed
When The system updates equipment status information
Then All equipment status flags must be updated to reflect the released from seizure state
R-GCX016E-cbl-01543 Decrement Train Seizure Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Decrement Train Seizure Counter' is invoked, and assuming that equipment seizure status has been successfully removed, when the system updates train-level seizure tracking, the desired outcome is that the train seizure counter must be decremented by one.
💻 Technical Criteria
Given Equipment seizure status has been successfully removed
When The system updates train-level seizure tracking
Then The train seizure counter must be decremented by one
R-GCX016E-cbl-01544 All Equipment Released from Seizure?
Decision Rules
📊 Business Logic Narrative
When the process 'All Equipment Released from Seizure?' is invoked, and assuming that train seizure counter has been decremented, when the system evaluates the remaining seizure counter value, the desired outcome is that if seizure counter equals zero, then all equipment is released from seizure, otherwise some equipment remains seized.
💻 Technical Criteria
Given Train seizure counter has been decremented
When The system evaluates the remaining seizure counter value
Then If seizure counter equals zero, then all equipment is released from seizure, otherwise some equipment remains seized
R-GCX016E-cbl-01545 Update Train Seizure Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Seizure Status Flag' is invoked, and assuming that all equipment in the train has been released from seizure, when the system updates train status information, the desired outcome is that the train seizure status flag must be cleared to indicate no equipment is seized.
💻 Technical Criteria
Given All equipment in the train has been released from seizure
When The system updates train status information
Then The train seizure status flag must be cleared to indicate no equipment is seized
R-GCX016E-cbl-01546 Log Seizure Release Action
Action Rules
📊 Business Logic Narrative
When the process 'Log Seizure Release Action' is invoked, and assuming that equipment seizure release has been processed successfully, when the system performs audit logging, the desired outcome is that a log entry must be created documenting the seizure release action with equipment details and timestamp.
💻 Technical Criteria
Given Equipment seizure release has been processed successfully
When The system performs audit logging
Then A log entry must be created documenting the seizure release action with equipment details and timestamp
R-GCX016E-cbl-01547 Generate Equipment Release Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Equipment Release Notification' is invoked, and assuming that equipment seizure release action has been logged, when the system generates notifications, the desired outcome is that a release notification must be created containing equipment identification and release details.
💻 Technical Criteria
Given Equipment seizure release action has been logged
When The system generates notifications
Then A release notification must be created containing equipment identification and release details
R-GCX016E-cbl-01548 Update Equipment Status in Database
Action Rules
📊 Business Logic Narrative
When the process 'Update Equipment Status in Database' is invoked, and assuming that equipment status flags have been updated and notifications generated, when the system commits the changes, the desired outcome is that the equipment status must be updated in the database to reflect the seizure release.
💻 Technical Criteria
Given Equipment status flags have been updated and notifications generated
When The system commits the changes
Then The equipment status must be updated in the database to reflect the seizure release
R-GCX016E-cbl-01549 Generate Error - Invalid Equipment ID
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error - Invalid Equipment ID', assuming that a vid segment with ser disposition is received, when the equipment id validation fails due to invalid format or blank content, the desired outcome is that an error must be generated indicating invalid equipment id.
💻 Technical Criteria
EXCLUDING A VID segment with SER disposition is received
When The equipment ID validation fails due to invalid format or blank content
Then An error must be generated indicating invalid equipment ID
R-GCX016E-cbl-01550 Generate Error - Equipment Not Found
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error - Equipment Not Found', assuming that a valid equipment id from vid segment, when the equipment is not found in the train equipment consist, the desired outcome is that an error must be generated indicating equipment not found in train.
💻 Technical Criteria
EXCLUDING A valid equipment ID from VID segment
When The equipment is not found in the train equipment consist
Then An error must be generated indicating equipment not found in train
R-GCX016E-cbl-01551 Generate Error - Equipment Not Seized
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error - Equipment Not Seized', assuming that equipment is found in train consist but seizure release is requested, when the equipment is not currently in seized status, the desired outcome is that an error must be generated indicating equipment is not currently seized.
💻 Technical Criteria
EXCLUDING Equipment is found in train consist but seizure release is requested
When The equipment is not currently in seized status
Then An error must be generated indicating equipment is not currently seized
R-GCX016E-cbl-01566 Process US Cargo Arrival Notifications
Process Rules
📊 Business Logic Narrative
When the process 'Process US Cargo Arrival Notifications' is invoked, and assuming that an import manifest train status has been updated in the database, when the system processes associated cargo arrivals, the desired outcome is that process arrival notifications for all us cargos in gcsusrt segments associated with the train.
💻 Technical Criteria
Given An import manifest train status has been updated in the database
When The system processes associated cargo arrivals
Then Process arrival notifications for all US cargos in GCSUSRT segments associated with the train
R-GCX016E-cbl-01567 Send AEI Messages for Train Arrival
Action Rules
📊 Business Logic Narrative
When the process 'Send AEI Messages for Train Arrival' is invoked, and assuming that us cargo arrival notifications have been processed for an import manifest train, when the system generates external notifications, the desired outcome is that send aei messages to notify external systems of the train arrival event.
💻 Technical Criteria
Given US cargo arrival notifications have been processed for an import manifest train
When The system generates external notifications
Then Send AEI messages to notify external systems of the train arrival event
R-GCX016E-cbl-01570 Extract Equipment ID from VID Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment ID from VID Segment' is invoked, and assuming that a vid segment is received in the message, when the vid segment contains equipment id information, the desired outcome is that the system extracts the equipment id for further processing.
💻 Technical Criteria
Given A VID segment is received in the message
When The VID segment contains equipment ID information
Then The system extracts the equipment ID for further processing
R-GCX016E-cbl-01571 Equipment ID Present?
Validation Rules
📊 Business Logic Narrative
When the process 'Equipment ID Present?' is invoked, and assuming that a vid segment is received, when the system checks for equipment id presence, the desired outcome is that processing continues if equipment id is present, otherwise equipment processing is skipped.
💻 Technical Criteria
Given A VID segment is received
When The system checks for equipment ID presence
Then Processing continues if equipment ID is present, otherwise equipment processing is skipped
R-GCX016E-cbl-01572 Locate Equipment in Train Consist
Process Rules
📊 Business Logic Narrative
When the process 'Locate Equipment in Train Consist' is invoked, and assuming that an equipment id has been extracted from vid segment, when the system searches the train consist for the equipment, the desired outcome is that the system determines whether the equipment is found in the train list.
💻 Technical Criteria
Given An equipment ID has been extracted from VID segment
When The system searches the train consist for the equipment
Then The system determines whether the equipment is found in the train list
R-GCX016E-cbl-01573 Equipment Found in Train?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment Found in Train?' is invoked, and assuming that equipment has been searched in the train consist, when the system evaluates the search results, the desired outcome is that if equipment is not found, it is added to the train list; if found, disposition processing continues.
💻 Technical Criteria
Given Equipment has been searched in the train consist
When The system evaluates the search results
Then If equipment is not found, it is added to the train list; if found, disposition processing continues
R-GCX016E-cbl-01574 Add Equipment to Train List
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Add Equipment to Train List', assuming that equipment is not found in the current train consist, when the system processes the equipment for the first time, the desired outcome is that the equipment is added to the train equipment list for future reference.
💻 Technical Criteria
EXCLUDING Equipment is not found in the current train consist
When The system processes the equipment for the first time
Then The equipment is added to the train equipment list for future reference
R-GCX016E-cbl-01575 Disposition Code Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Disposition Code Type?' is invoked, and assuming that equipment exists or has been added to the train list, when the system evaluates the disposition code type, the desired outcome is that the system routes to appropriate status update based on code type: hre for hold release, sei for seizure, ser for seizure release, or other hold types.
💻 Technical Criteria
Given Equipment exists or has been added to the train list
When The system evaluates the disposition code type
Then The system routes to appropriate status update based on code type: HRE for hold release, SEI for seizure, SER for seizure release, or other hold types
R-GCX016E-cbl-01576 Update Equipment Hold Status Flag
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Update Equipment Hold Status Flag', assuming that a hold-related disposition code is being processed for equipment, when the disposition code is not hre, sei, or ser, the desired outcome is that the system sets the equipment hold status flag to indicate the equipment is held.
💻 Technical Criteria
EXCLUDING A hold-related disposition code is being processed for equipment
When The disposition code is not HRE, SEI, or SER
Then The system sets the equipment hold status flag to indicate the equipment is held
R-GCX016E-cbl-01577 Update Equipment Release Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Update Equipment Release Status Flag' is invoked, and assuming that an hre hold release disposition code is being processed for equipment, when the system processes the hold release action, the desired outcome is that the system sets the equipment release status flag to indicate the equipment hold is released.
💻 Technical Criteria
Given An HRE hold release disposition code is being processed for equipment
When The system processes the hold release action
Then The system sets the equipment release status flag to indicate the equipment hold is released
R-GCX016E-cbl-01578 Update Equipment Seizure Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Update Equipment Seizure Status Flag' is invoked, and assuming that an sei seizure disposition code is being processed for equipment, when the system processes the seizure action, the desired outcome is that the system sets the equipment seizure status flag to indicate the equipment is seized.
💻 Technical Criteria
Given An SEI seizure disposition code is being processed for equipment
When The system processes the seizure action
Then The system sets the equipment seizure status flag to indicate the equipment is seized
R-GCX016E-cbl-01579 Update Equipment Seizure Release Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Update Equipment Seizure Release Status Flag' is invoked, and assuming that an ser seizure release disposition code is being processed for equipment, when the system processes the seizure release action, the desired outcome is that the system sets the equipment seizure release status flag to indicate the equipment seizure is released.
💻 Technical Criteria
Given An SER seizure release disposition code is being processed for equipment
When The system processes the seizure release action
Then The system sets the equipment seizure release status flag to indicate the equipment seizure is released
R-GCX016E-cbl-01580 Update Equipment Hold Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Update Equipment Hold Counter' is invoked, and assuming that equipment hold status flag has been updated, when the system processes the hold action, the desired outcome is that the system increments the equipment hold counter to track the number of holds applied.
💻 Technical Criteria
Given Equipment hold status flag has been updated
When The system processes the hold action
Then The system increments the equipment hold counter to track the number of holds applied
R-GCX016E-cbl-01581 Update Equipment Release Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Update Equipment Release Counter' is invoked, and assuming that equipment release status flag has been updated, when the system processes the release action, the desired outcome is that the system increments the equipment release counter to track the number of releases applied.
💻 Technical Criteria
Given Equipment release status flag has been updated
When The system processes the release action
Then The system increments the equipment release counter to track the number of releases applied
R-GCX016E-cbl-01582 Update Equipment Seizure Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Update Equipment Seizure Counter' is invoked, and assuming that equipment seizure status flag has been updated, when the system processes the seizure action, the desired outcome is that the system increments the equipment seizure counter to track the number of seizures applied.
💻 Technical Criteria
Given Equipment seizure status flag has been updated
When The system processes the seizure action
Then The system increments the equipment seizure counter to track the number of seizures applied
R-GCX016E-cbl-01583 Update Equipment Seizure Release Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Update Equipment Seizure Release Counter' is invoked, and assuming that equipment seizure release status flag has been updated, when the system processes the seizure release action, the desired outcome is that the system increments the equipment seizure release counter to track the number of seizure releases applied.
💻 Technical Criteria
Given Equipment seizure release status flag has been updated
When The system processes the seizure release action
Then The system increments the equipment seizure release counter to track the number of seizure releases applied
R-GCX016E-cbl-01584 Update Train Equipment List
Action Rules
📊 Business Logic Narrative
When the process 'Update Train Equipment List' is invoked, and assuming that equipment status flags and counters have been updated, when the system completes status processing for the equipment, the desired outcome is that the system updates the train equipment list with the current equipment status and counter values.
💻 Technical Criteria
Given Equipment status flags and counters have been updated
When The system completes status processing for the equipment
Then The system updates the train equipment list with the current equipment status and counter values
R-GCX016E-cbl-01585 Log Equipment Status Change
Process Rules
📊 Business Logic Narrative
When the process 'Log Equipment Status Change' is invoked, and assuming that train equipment list has been updated with new status information, when the system completes equipment status processing, the desired outcome is that the system logs the equipment status change for audit trail and tracking purposes.
💻 Technical Criteria
Given Train equipment list has been updated with new status information
When The system completes equipment status processing
Then The system logs the equipment status change for audit trail and tracking purposes
R-GCX016E-cbl-01586 Continue to Next Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Continue to Next Equipment' is invoked, and assuming that current equipment status change has been logged, when there are additional equipment items to process in the vid segment, the desired outcome is that the system continues to process the next equipment item in the list.
💻 Technical Criteria
Given Current equipment status change has been logged
When There are additional equipment items to process in the VID segment
Then The system continues to process the next equipment item in the list
R-GCX016E-cbl-01587 Equipment Processing Complete
Process Rules
📊 Business Logic Narrative
When the process 'Equipment Processing Complete' is invoked, and assuming that all equipment items have been processed or no equipment id was present in vid segment, when the system reaches the end of equipment processing, the desired outcome is that the system marks equipment processing as complete and continues with next segment processing.
💻 Technical Criteria
Given All equipment items have been processed or no equipment ID was present in VID segment
When The system reaches the end of equipment processing
Then The system marks equipment processing as complete and continues with next segment processing
R-GCX016E-cbl-01596 Update Individual Equipment Hold Status
Process Rules
📊 Business Logic Narrative
When the process 'Update Individual Equipment Hold Status' is invoked, and assuming that a train status event requires vid equipment processing for hold or seizure actions, when individual equipment processing is performed, the desired outcome is that equipment hold status is updated, equipment seizure status is updated, and equipment hold/seizure counters are incremented or decremented accordingly.
💻 Technical Criteria
Given A train status event requires VID equipment processing for hold or seizure actions
When Individual equipment processing is performed
Then Equipment hold status is updated, equipment seizure status is updated, and equipment hold/seizure counters are incremented or decremented accordingly
R-GCX016E-cbl-01598 Extract Equipment ID from VID Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment ID from VID Segment' is invoked, and assuming that a vid segment has been received for processing, when the system processes the vid segment to extract equipment identification, the desired outcome is that the equipment id is extracted from the vid segment data structure.
💻 Technical Criteria
Given A VID segment has been received for processing
When The system processes the VID segment to extract equipment identification
Then The equipment ID is extracted from the VID segment data structure
R-GCX016E-cbl-01599 Equipment ID Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Equipment ID Valid?' is invoked, and assuming that an equipment id has been extracted from a vid segment, when the system validates the equipment id format and content, the desired outcome is that the equipment id is accepted if valid or rejected if invalid with appropriate error handling.
💻 Technical Criteria
Given An equipment ID has been extracted from a VID segment
When The system validates the equipment ID format and content
Then The equipment ID is accepted if valid or rejected if invalid with appropriate error handling
R-GCX016E-cbl-01600 Locate Equipment in Train Consist
Process Rules
📊 Business Logic Narrative
When the process 'Locate Equipment in Train Consist' is invoked, and assuming that a valid equipment id has been extracted from a vid segment, when the system searches for the equipment in the current train consist, the desired outcome is that the equipment location is identified within the train consist data structure.
💻 Technical Criteria
Given A valid equipment ID has been extracted from a VID segment
When The system searches for the equipment in the current train consist
Then The equipment location is identified within the train consist data structure
R-GCX016E-cbl-01601 Equipment Found in Train?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment Found in Train?' is invoked, and assuming that the system has searched for equipment in the train consist, when the search results are evaluated, the desired outcome is that the system confirms equipment exists in train or generates equipment not found condition.
💻 Technical Criteria
Given The system has searched for equipment in the train consist
When The search results are evaluated
Then The system confirms equipment exists in train or generates equipment not found condition
R-GCX016E-cbl-01602 Determine VID Disposition Code
Process Rules
📊 Business Logic Narrative
When the process 'Determine VID Disposition Code' is invoked, and assuming that equipment has been found in the train consist, when the system analyzes the vid segment for disposition code information, the desired outcome is that the specific disposition code (hmi, hre, sei, ser) is determined for equipment status processing.
💻 Technical Criteria
Given Equipment has been found in the train consist
When The system analyzes the VID segment for disposition code information
Then The specific disposition code (HMI, HRE, SEI, SER) is determined for equipment status processing
R-GCX016E-cbl-01604 Process Equipment Hold - HMI
Action Rules
📊 Business Logic Narrative
When the process 'Process Equipment Hold - HMI' is invoked, and assuming that a vid segment contains hmi disposition code for valid equipment in train, when the system processes the equipment hold request, the desired outcome is that equipment hold processing is initiated for the specified equipment.
💻 Technical Criteria
Given A VID segment contains HMI disposition code for valid equipment in train
When The system processes the equipment hold request
Then Equipment hold processing is initiated for the specified equipment
R-GCX016E-cbl-01605 Process Equipment Release - HRE
Action Rules
📊 Business Logic Narrative
When the process 'Process Equipment Release - HRE' is invoked, and assuming that a vid segment contains hre disposition code for valid equipment in train, when the system processes the equipment release request, the desired outcome is that equipment release processing is initiated for the specified equipment.
💻 Technical Criteria
Given A VID segment contains HRE disposition code for valid equipment in train
When The system processes the equipment release request
Then Equipment release processing is initiated for the specified equipment
R-GCX016E-cbl-01606 Process Equipment Seizure - SEI
Action Rules
📊 Business Logic Narrative
When the process 'Process Equipment Seizure - SEI' is invoked, and assuming that a vid segment contains sei disposition code for valid equipment in train, when the system processes the equipment seizure request, the desired outcome is that equipment seizure processing is initiated for the specified equipment.
💻 Technical Criteria
Given A VID segment contains SEI disposition code for valid equipment in train
When The system processes the equipment seizure request
Then Equipment seizure processing is initiated for the specified equipment
R-GCX016E-cbl-01607 Process Equipment Seizure Release - SER
Action Rules
📊 Business Logic Narrative
When the process 'Process Equipment Seizure Release - SER' is invoked, and assuming that a vid segment contains ser disposition code for valid equipment in train, when the system processes the equipment seizure release request, the desired outcome is that equipment seizure release processing is initiated for the specified equipment.
💻 Technical Criteria
Given A VID segment contains SER disposition code for valid equipment in train
When The system processes the equipment seizure release request
Then Equipment seizure release processing is initiated for the specified equipment
R-GCX016E-cbl-01608 Update Equipment Hold Status Flag
Process Rules
📊 Business Logic Narrative
When the process 'Update Equipment Hold Status Flag' is invoked, and assuming that equipment hold processing has been initiated for specific equipment, when the system updates equipment status information, the desired outcome is that the equipment hold status flag is set to indicate hold condition.
💻 Technical Criteria
Given Equipment hold processing has been initiated for specific equipment
When The system updates equipment status information
Then The equipment hold status flag is set to indicate hold condition
R-GCX016E-cbl-01609 Update Equipment Release Status Flag
Process Rules
📊 Business Logic Narrative
When the process 'Update Equipment Release Status Flag' is invoked, and assuming that equipment release processing has been initiated for specific equipment, when the system updates equipment status information, the desired outcome is that the equipment release status flag is set to indicate release condition.
💻 Technical Criteria
Given Equipment release processing has been initiated for specific equipment
When The system updates equipment status information
Then The equipment release status flag is set to indicate release condition
R-GCX016E-cbl-01610 Update Equipment Seizure Status Flag
Process Rules
📊 Business Logic Narrative
When the process 'Update Equipment Seizure Status Flag' is invoked, and assuming that equipment seizure processing has been initiated for specific equipment, when the system updates equipment status information, the desired outcome is that the equipment seizure status flag is set to indicate seizure condition.
💻 Technical Criteria
Given Equipment seizure processing has been initiated for specific equipment
When The system updates equipment status information
Then The equipment seizure status flag is set to indicate seizure condition
R-GCX016E-cbl-01611 Update Equipment Seizure Release Status Flag
Process Rules
📊 Business Logic Narrative
When the process 'Update Equipment Seizure Release Status Flag' is invoked, and assuming that equipment seizure release processing has been initiated for specific equipment, when the system updates equipment status information, the desired outcome is that the equipment seizure release status flag is set to indicate release from seizure condition.
💻 Technical Criteria
Given Equipment seizure release processing has been initiated for specific equipment
When The system updates equipment status information
Then The equipment seizure release status flag is set to indicate release from seizure condition
R-GCX016E-cbl-01612 Update Equipment Hold Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Update Equipment Hold Counter' is invoked, and assuming that equipment hold status flag has been updated for specific equipment, when the system updates equipment tracking counters, the desired outcome is that the equipment hold counter is incremented to reflect the additional hold action.
💻 Technical Criteria
Given Equipment hold status flag has been updated for specific equipment
When The system updates equipment tracking counters
Then The equipment hold counter is incremented to reflect the additional hold action
R-GCX016E-cbl-01613 Update Equipment Release Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Update Equipment Release Counter' is invoked, and assuming that equipment release status flag has been updated for specific equipment, when the system updates equipment tracking counters, the desired outcome is that the equipment release counter is incremented to reflect the additional release action.
💻 Technical Criteria
Given Equipment release status flag has been updated for specific equipment
When The system updates equipment tracking counters
Then The equipment release counter is incremented to reflect the additional release action
R-GCX016E-cbl-01614 Update Equipment Seizure Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Update Equipment Seizure Counter' is invoked, and assuming that equipment seizure status flag has been updated for specific equipment, when the system updates equipment tracking counters, the desired outcome is that the equipment seizure counter is incremented to reflect the additional seizure action.
💻 Technical Criteria
Given Equipment seizure status flag has been updated for specific equipment
When The system updates equipment tracking counters
Then The equipment seizure counter is incremented to reflect the additional seizure action
R-GCX016E-cbl-01615 Update Equipment Seizure Release Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Update Equipment Seizure Release Counter' is invoked, and assuming that equipment seizure release status flag has been updated for specific equipment, when the system updates equipment tracking counters, the desired outcome is that the equipment seizure release counter is incremented to reflect the additional seizure release action.
💻 Technical Criteria
Given Equipment seizure release status flag has been updated for specific equipment
When The system updates equipment tracking counters
Then The equipment seizure release counter is incremented to reflect the additional seizure release action
R-GCX016E-cbl-01616 Update Train Equipment List
Process Rules
📊 Business Logic Narrative
When the process 'Update Train Equipment List' is invoked, and assuming that equipment status counters have been updated for specific equipment, when the system updates the train equipment list, the desired outcome is that the train equipment list reflects the current status information for the processed equipment.
💻 Technical Criteria
Given Equipment status counters have been updated for specific equipment
When The system updates the train equipment list
Then The train equipment list reflects the current status information for the processed equipment
R-GCX016E-cbl-01617 Log Equipment Status Change
Process Rules
📊 Business Logic Narrative
When the process 'Log Equipment Status Change' is invoked, and assuming that train equipment list has been updated with current equipment status, when the system creates audit trail documentation, the desired outcome is that equipment status change is logged with timestamp, equipment id, and status change details.
💻 Technical Criteria
Given Train equipment list has been updated with current equipment status
When The system creates audit trail documentation
Then Equipment status change is logged with timestamp, equipment ID, and status change details
R-GCX016E-cbl-01618 Generate Equipment Status Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Equipment Status Notification' is invoked, and assuming that equipment status change has been logged in the system, when the system generates status notifications, the desired outcome is that equipment status notification is created and sent to appropriate recipients.
💻 Technical Criteria
Given Equipment status change has been logged in the system
When The system generates status notifications
Then Equipment status notification is created and sent to appropriate recipients
R-GCX016E-cbl-01619 Generate Equipment Not Found Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Equipment Not Found Error', assuming that equipment search in train consist has been completed, when the specified equipment is not found in the train consist, the desired outcome is that equipment not found error is generated with appropriate error details.
💻 Technical Criteria
EXCLUDING Equipment search in train consist has been completed
When The specified equipment is not found in the train consist
Then Equipment not found error is generated with appropriate error details
R-GCX016E-cbl-01620 Generate Invalid Equipment ID Error
Validation Rules
📊 Business Logic Narrative
When the process 'Generate Invalid Equipment ID Error' is invoked, and assuming that equipment id has been extracted from vid segment, when the equipment id fails validation requirements, the desired outcome is that invalid equipment id error is generated with appropriate error details.
💻 Technical Criteria
Given Equipment ID has been extracted from VID segment
When The equipment ID fails validation requirements
Then Invalid equipment ID error is generated with appropriate error details
R-GCX016E-cbl-01638 US Cargo Found?
Decision Rules
📊 Business Logic Narrative
When the process 'US Cargo Found?' is invoked, and assuming that a train arrival date has been updated, when the system searches for us cargo in the train manifest, the desired outcome is that if us cargo is found in the train, proceed with cargo arrival processing, otherwise complete train processing without cargo updates.
💻 Technical Criteria
Given A train arrival date has been updated
When The system searches for US cargo in the train manifest
Then If US cargo is found in the train, proceed with cargo arrival processing, otherwise complete train processing without cargo updates
R-GCX016E-cbl-01639 Set Cargo Arrival Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Cargo Arrival Flag' is invoked, and assuming that us cargo has been found in an arriving train, when the system processes each cargo shipment, the desired outcome is that set the arrival flag for each cargo to indicate it has arrived at destination.
💻 Technical Criteria
Given US cargo has been found in an arriving train
When The system processes each cargo shipment
Then Set the arrival flag for each cargo to indicate it has arrived at destination
R-GCX016E-cbl-01640 Calculate Cargo Age
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Cargo Age' is invoked, and assuming that cargo arrival flag has been set, when the system calculates cargo transit time, the desired outcome is that calculate the age of cargo based on the difference between current date and original shipment date.
💻 Technical Criteria
Given Cargo arrival flag has been set
When The system calculates cargo transit time
Then Calculate the age of cargo based on the difference between current date and original shipment date
R-GCX016E-cbl-01641 Clear Bond Start Dates
Action Rules
📊 Business Logic Narrative
When the process 'Clear Bond Start Dates' is invoked, and assuming that cargo age has been calculated, when the system processes bond information for arrived cargo, the desired outcome is that clear the bond start dates to reset the bonding period for the arrived cargo.
💻 Technical Criteria
Given Cargo age has been calculated
When The system processes bond information for arrived cargo
Then Clear the bond start dates to reset the bonding period for the arrived cargo
R-GCX016E-cbl-01642 Set Arrival Index
Action Rules
📊 Business Logic Narrative
When the process 'Set Arrival Index' is invoked, and assuming that bond start dates have been cleared for cargo, when the system assigns tracking references, the desired outcome is that set the arrival index for the cargo to enable proper tracking and reference.
💻 Technical Criteria
Given Bond start dates have been cleared for cargo
When The system assigns tracking references
Then Set the arrival index for the cargo to enable proper tracking and reference
R-GCX016E-cbl-01643 Generate AEI Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate AEI Message' is invoked, and assuming that arrival index has been set for cargo, when the system generates arrival notifications, the desired outcome is that create an aei message containing train and cargo arrival information.
💻 Technical Criteria
Given Arrival index has been set for cargo
When The system generates arrival notifications
Then Create an AEI message containing train and cargo arrival information
R-GCX016E-cbl-01645 Create Arrival Notification Message
Action Rules
📊 Business Logic Narrative
When the process 'Create Arrival Notification Message' is invoked, and assuming that aei notification has been sent, when the system creates business notifications, the desired outcome is that create a detailed arrival notification message containing train and cargo details.
💻 Technical Criteria
Given AEI notification has been sent
When The system creates business notifications
Then Create a detailed arrival notification message containing train and cargo details
R-GCX016E-cbl-01647 Update Equipment Status in Train
Action Rules
📊 Business Logic Narrative
When the process 'Update Equipment Status in Train' is invoked, and assuming that train arrival action has been logged, when the system updates equipment records, the desired outcome is that update the status of all equipment in the train to reflect arrival at destination.
💻 Technical Criteria
Given Train arrival action has been logged
When The system updates equipment records
Then Update the status of all equipment in the train to reflect arrival at destination
R-GCX016E-cbl-01660 Associated with Cargo?
Decision Rules
📊 Business Logic Narrative
When the process 'Associated with Cargo?' is invoked, and assuming that a k1 comment has been extracted from the segment, when the system evaluates the processing context, the desired outcome is that the system should determine if the comment is cargo-related and route accordingly.
💻 Technical Criteria
Given A K1 comment has been extracted from the segment
When The system evaluates the processing context
Then The system should determine if the comment is cargo-related and route accordingly
R-GCX016E-cbl-01661 Store K1 Text in Cargo Context
Process Rules
📊 Business Logic Narrative
When the process 'Store K1 Text in Cargo Context' is invoked, and assuming that a k1 comment is determined to be cargo-associated, when the comment text needs to be preserved, the desired outcome is that the system should store the k1 text in the cargo processing context.
💻 Technical Criteria
Given A K1 comment is determined to be cargo-associated
When The comment text needs to be preserved
Then The system should store the K1 text in the cargo processing context
R-GCX016E-cbl-01662 Link K1 Message to Disposition Code
Process Rules
📊 Business Logic Narrative
When the process 'Link K1 Message to Disposition Code' is invoked, and assuming that a k1 comment is stored in cargo context, when a disposition code is being processed, the desired outcome is that the system should link the k1 message to the appropriate disposition code.
💻 Technical Criteria
Given A K1 comment is stored in cargo context
When A disposition code is being processed
Then The system should link the K1 message to the appropriate disposition code
R-GCX016E-cbl-01665 Integrate K1 Comments into Processing
Process Rules
📊 Business Logic Narrative
When the process 'Integrate K1 Comments into Processing' is invoked, and assuming that all k1 segments have been processed and stored, when the system needs to integrate comments into cargo processing, the desired outcome is that the system should make k1 comments available for subsequent processing steps.
💻 Technical Criteria
Given All K1 segments have been processed and stored
When The system needs to integrate comments into cargo processing
Then The system should make K1 comments available for subsequent processing steps
R-GCX016E-cbl-01681 Is Disposition Code 'Proceed'?
Decision Rules
📊 Business Logic Narrative
When the process 'Is Disposition Code 'Proceed'?' is invoked, and assuming that a disposition code is being processed for a cargo shipment, when the disposition code is 'proceed' and the cargo arrival status is checked, the desired outcome is that if cargo has arrived, apply standard proceed processing; if cargo has not arrived, skip proceed processing and continue with normal flow.
💻 Technical Criteria
Given A disposition code is being processed for a cargo shipment
When The disposition code is 'PROCEED' and the cargo arrival status is checked
Then If cargo has arrived, apply standard proceed processing; if cargo has not arrived, skip proceed processing and continue with normal flow
R-GCX016E-cbl-01682 Is Disposition Code 'Cancel'?
Process Rules
📊 Business Logic Narrative
When the process 'Is Disposition Code 'Cancel'?' is invoked, and assuming that a disposition code is being processed for a cargo shipment, when the disposition code is 'cancel-xj' and previous disposition codes are searched, the desired outcome is that if a matching proceed code is found, remove the previous proceed code and then apply cancel processing; if no matching code is found, proceed directly to cancel processing.
💻 Technical Criteria
Given A disposition code is being processed for a cargo shipment
When The disposition code is 'CANCEL-XJ' and previous disposition codes are searched
Then If a matching proceed code is found, remove the previous proceed code and then apply cancel processing; if no matching code is found, proceed directly to cancel processing
R-GCX016E-cbl-01683 Has Cargo Arrived?
Validation Rules
📊 Business Logic Narrative
When the process 'Has Cargo Arrived?' is invoked, and assuming that a proceed disposition code is being processed for a cargo shipment, when the cargo arrival status is evaluated, the desired outcome is that return true if cargo arrival date exists and cargo status indicates arrival, otherwise return false.
💻 Technical Criteria
Given A proceed disposition code is being processed for a cargo shipment
When The cargo arrival status is evaluated
Then Return true if cargo arrival date exists and cargo status indicates arrival, otherwise return false
R-GCX016E-cbl-01684 Find Matching Proceed Code?
Decision Rules
📊 Business Logic Narrative
When the process 'Find Matching Proceed Code?' is invoked, and assuming that a cancel disposition code is being processed and previous disposition codes exist, when the system searches through the cargo's disposition code history, the desired outcome is that return true if a proceed disposition code with matching entry number and quantity is found, otherwise return false.
💻 Technical Criteria
Given A cancel disposition code is being processed and previous disposition codes exist
When The system searches through the cargo's disposition code history
Then Return true if a proceed disposition code with matching entry number and quantity is found, otherwise return false
R-GCX016E-cbl-01686 Cargo Status Changed?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Status Changed?' is invoked, and assuming that cancel disposition processing has been completed for a cargo shipment, when the cargo status before and after cancel processing is compared, the desired outcome is that return true if the cargo status flags, release quantities, or arrival status have changed, otherwise return false.
💻 Technical Criteria
Given Cancel disposition processing has been completed for a cargo shipment
When The cargo status before and after cancel processing is compared
Then Return true if the cargo status flags, release quantities, or arrival status have changed, otherwise return false
R-GCX016E-cbl-01687 Update Cargo Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status Flags' is invoked, and assuming that cargo status has changed as a result of disposition code re-processing, when status flags need to be updated to reflect the new cargo state, the desired outcome is that update arrival status, release status, hold status, and any other relevant cargo status indicators based on the final disposition code array.
💻 Technical Criteria
Given Cargo status has changed as a result of disposition code re-processing
When Status flags need to be updated to reflect the new cargo state
Then Update arrival status, release status, hold status, and any other relevant cargo status indicators based on the final disposition code array
R-GCX016E-cbl-01688 Log Re-processing Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Re-processing Action' is invoked, and assuming that disposition code re-processing has occurred for a cargo shipment, when the re-processing action needs to be recorded, the desired outcome is that create a log entry containing the original disposition code, re-processing type, cargo identifier, and timestamp.
💻 Technical Criteria
Given Disposition code re-processing has occurred for a cargo shipment
When The re-processing action needs to be recorded
Then Create a log entry containing the original disposition code, re-processing type, cargo identifier, and timestamp
R-GCX016E-cbl-01695 Validate Cargo Record Status
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Cargo Record Status' is invoked, and assuming that cargo record has been retrieved from the database, when the system validates the cargo record status using gcsccrt, the desired outcome is that cargo record status is checked for validity and processing eligibility.
💻 Technical Criteria
Given Cargo record has been retrieved from the database
When The system validates the cargo record status using GCSCCRT
Then Cargo record status is checked for validity and processing eligibility
R-GCX016E-cbl-01696 Valid Cargo Record?
Decision Rules
📊 Business Logic Narrative
When the process 'Valid Cargo Record?' is invoked, and assuming that cargo record status validation has been completed, when the system evaluates cargo record validity, the desired outcome is that if cargo record is valid, proceed with cargo processing; otherwise generate cargo not found error.
💻 Technical Criteria
Given Cargo record status validation has been completed
When The system evaluates cargo record validity
Then If cargo record is valid, proceed with cargo processing; otherwise generate cargo not found error
R-GCX016E-cbl-01697 Process Found Cargo
Process Rules
📊 Business Logic Narrative
When the process 'Process Found Cargo' is invoked, and assuming that cargo record has been found and validated as eligible for processing, when the system begins cargo processing operations, the desired outcome is that cargo processing is initiated with the validated cargo record.
💻 Technical Criteria
Given Cargo record has been found and validated as eligible for processing
When The system begins cargo processing operations
Then Cargo processing is initiated with the validated cargo record
R-GCX016E-cbl-01698 Update Cargo Processing Flags
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo Processing Flags' is invoked, and assuming that cargo processing has been initiated, when the system updates cargo processing status flags, the desired outcome is that processing flags are set to indicate successful cargo location and processing status.
💻 Technical Criteria
Given Cargo processing has been initiated
When The system updates cargo processing status flags
Then Processing flags are set to indicate successful cargo location and processing status
R-GCX016E-cbl-01699 Continue with Disposition Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue with Disposition Processing' is invoked, and assuming that cargo has been found, validated, and processing flags updated, when the system continues with disposition processing, the desired outcome is that disposition code processing proceeds with the located cargo record.
💻 Technical Criteria
Given Cargo has been found, validated, and processing flags updated
When The system continues with disposition processing
Then Disposition code processing proceeds with the located cargo record
R-GCX016E-cbl-01701 Log Search Attempt
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Search Attempt', assuming that cargo not found error has been generated, when the system logs the search attempt, the desired outcome is that search attempt details are recorded for audit trail.
💻 Technical Criteria
EXCLUDING Cargo not found error has been generated
When The system logs the search attempt
Then Search attempt details are recorded for audit trail
R-GCX016E-cbl-01703 Clear BOL Type Code
Action Rules
📊 Business Logic Narrative
When the process 'Clear BOL Type Code' is invoked, and assuming that disposition code 95 has been validated and bond cancellation is being processed, when the system processes the bond information clearing, the desired outcome is that the bol type code field in the cargo record is cleared to spaces.
💻 Technical Criteria
Given Disposition code 95 has been validated and bond cancellation is being processed
When The system processes the bond information clearing
Then The BOL type code field in the cargo record is cleared to spaces
R-GCX016E-cbl-01709 Log Bond Clearing Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Bond Clearing Action' is invoked, and assuming that cargo status arrays have been updated with the bond cancellation, when the system creates audit log entries, the desired outcome is that a log entry is created with timestamp, user information, and details of the bond clearing action for audit trail purposes.
💻 Technical Criteria
Given Cargo status arrays have been updated with the bond cancellation
When The system creates audit log entries
Then A log entry is created with timestamp, user information, and details of the bond clearing action for audit trail purposes
R-GCX016E-cbl-01710 Generate Merlin Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Merlin Notification' is invoked, and assuming that bond clearing action has been logged and all updates are complete, when the system generates merlin notifications, the desired outcome is that a merlin message is created and sent to appropriate recipients containing cargo details and bond cancellation information.
💻 Technical Criteria
Given Bond clearing action has been logged and all updates are complete
When The system generates Merlin notifications
Then A Merlin message is created and sent to appropriate recipients containing cargo details and bond cancellation information
R-GCX016E-cbl-01712 Entry Type Code Present?
Validation Rules
📊 Business Logic Narrative
When the process 'Entry Type Code Present?' is invoked, and assuming that an x4 segment is being processed for cargo disposition, when the system checks for the presence of an entry type code in the segment, the desired outcome is that if entry type code is present, continue with conversion processing, otherwise skip entry type processing and continue with cargo processing.
💻 Technical Criteria
Given An X4 segment is being processed for cargo disposition
When The system checks for the presence of an entry type code in the segment
Then If entry type code is present, continue with conversion processing, otherwise skip entry type processing and continue with cargo processing
R-GCX016E-cbl-01713 Retrieve Current Entry Type Code Value
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Entry Type Code Value' is invoked, and assuming that an entry type code is present in the x4 segment, when the system needs to process entry type code conversion, the desired outcome is that retrieve the current entry type code value from the us cargo root segment record.
💻 Technical Criteria
Given An entry type code is present in the X4 segment
When The system needs to process entry type code conversion
Then Retrieve the current entry type code value from the US cargo root segment record
R-GCX016E-cbl-01716 Set Master In-Bond Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Master In-Bond Flag' is invoked, and assuming that the entry type code is classified as in-bond (61, 62, 63, or 69), when the system processes in-bond entry type classification, the desired outcome is that set the master in-bond flag to indicate this cargo requires in-bond processing.
💻 Technical Criteria
Given The entry type code is classified as in-bond (61, 62, 63, or 69)
When The system processes in-bond entry type classification
Then Set the master in-bond flag to indicate this cargo requires in-bond processing
R-GCX016E-cbl-01717 Update Entry Type Code in Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Update Entry Type Code in Cargo Record' is invoked, and assuming that an entry type code has been converted to internal system value, when the system completes entry type code processing, the desired outcome is that update the entry type code field in the us cargo root segment record with the converted internal value.
💻 Technical Criteria
Given An entry type code has been converted to internal system value
When The system completes entry type code processing
Then Update the entry type code field in the US cargo root segment record with the converted internal value
R-GCX016E-cbl-01718 Border Crossing Scenario?
Decision Rules
📊 Business Logic Narrative
When the process 'Border Crossing Scenario?' is invoked, and assuming that entry type code has been updated in the cargo record, when the system evaluates processing context for special scenarios, the desired outcome is that if the cargo involves a border crossing scenario, apply special border crossing rules, otherwise proceed with standard validation.
💻 Technical Criteria
Given Entry type code has been updated in the cargo record
When The system evaluates processing context for special scenarios
Then If the cargo involves a border crossing scenario, apply special border crossing rules, otherwise proceed with standard validation
R-GCX016E-cbl-01719 Apply Special Border Crossing Rules
Policy Rules
📊 Business Logic Narrative
When the process 'Apply Special Border Crossing Rules' is invoked, and assuming that a border crossing scenario has been detected, when the system processes entry type code for border crossing cargo, the desired outcome is that apply special border crossing rules for entry type code processing and validation.
💻 Technical Criteria
Given A border crossing scenario has been detected
When The system processes entry type code for border crossing cargo
Then Apply special border crossing rules for entry type code processing and validation
R-GCX016E-cbl-01721 Store Internal Entry Type Code Value
Action Rules
📊 Business Logic Narrative
When the process 'Store Internal Entry Type Code Value' is invoked, and assuming that the converted entry type code has passed validation, when the system completes entry type code processing, the desired outcome is that store the validated internal entry type code value in the cargo record for future processing.
💻 Technical Criteria
Given The converted entry type code has passed validation
When The system completes entry type code processing
Then Store the validated internal entry type code value in the cargo record for future processing
R-GCX016E-cbl-01723 Generate Error for Invalid Entry Type Code
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error for Invalid Entry Type Code', assuming that the converted entry type code fails validation, when the system detects an invalid entry type code, the desired outcome is that generate an error message indicating invalid entry type code and continue with cargo processing.
💻 Technical Criteria
EXCLUDING The converted entry type code fails validation
When The system detects an invalid entry type code
Then Generate an error message indicating invalid entry type code and continue with cargo processing
R-GCX016E-cbl-01724 Extract US Port Code from Cargo Data
Process Rules
📊 Business Logic Narrative
When the process 'Extract US Port Code from Cargo Data' is invoked, and assuming that a cargo record contains cross-border movement information, when the system processes cargo for cross-border movement, the desired outcome is that the us port code is extracted from the cargo data for mapping purposes.
💻 Technical Criteria
Given A cargo record contains cross-border movement information
When The system processes cargo for cross-border movement
Then The US port code is extracted from the cargo data for mapping purposes
R-GCX016E-cbl-01729 Update Cargo Record with Canadian Location
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo Record with Canadian Location' is invoked, and assuming that a canadian border location name has been retrieved from the mapping table, when the location mapping is successful, the desired outcome is that the cargo record is updated with the canadian border location information.
💻 Technical Criteria
Given A Canadian border location name has been retrieved from the mapping table
When The location mapping is successful
Then The cargo record is updated with the Canadian border location information
R-GCX016E-cbl-01730 Set Cross-Border Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Cross-Border Flag' is invoked, and assuming that a cargo record has been updated with canadian border location information, when the location update is completed, the desired outcome is that a cross-border flag is set to indicate the cargo involves cross-border movement.
💻 Technical Criteria
Given A cargo record has been updated with Canadian border location information
When The location update is completed
Then A cross-border flag is set to indicate the cargo involves cross-border movement
R-GCX016E-cbl-01731 Log Mapping Success
Process Rules
📊 Business Logic Narrative
When the process 'Log Mapping Success' is invoked, and assuming that a cross-border flag has been set for the cargo, when the mapping process completes successfully, the desired outcome is that the system logs the successful mapping operation for audit purposes.
💻 Technical Criteria
Given A cross-border flag has been set for the cargo
When The mapping process completes successfully
Then The system logs the successful mapping operation for audit purposes
R-GCX016E-cbl-01734 A1 Disposition Code Processing
Process Rules
📊 Business Logic Narrative
When the process 'A1 Disposition Code Processing' is invoked, and assuming that a cargo has an a1 disposition code requiring fda reference number processing, when the system processes the a1 disposition code, the desired outcome is that the fda reference number is formatted and processed for a1 specific requirements.
💻 Technical Criteria
Given A cargo has an A1 disposition code requiring FDA reference number processing
When The system processes the A1 disposition code
Then The FDA reference number is formatted and processed for A1 specific requirements
R-GCX016E-cbl-01735 A3 Disposition Code Processing
Process Rules
📊 Business Logic Narrative
When the process 'A3 Disposition Code Processing' is invoked, and assuming that a cargo has an a3 disposition code requiring fda reference number processing, when the system processes the a3 disposition code, the desired outcome is that the fda reference number is formatted and processed for a3 specific requirements.
💻 Technical Criteria
Given A cargo has an A3 disposition code requiring FDA reference number processing
When The system processes the A3 disposition code
Then The FDA reference number is formatted and processed for A3 specific requirements
R-GCX016E-cbl-01740 N9 Segment Exists?
Decision Rules
📊 Business Logic Narrative
When the process 'N9 Segment Exists?' is invoked, and assuming that fda reference number processing is required for a cargo, when the system checks for existing n9 reference segments, the desired outcome is that the system determines if an n9 segment exists and routes processing accordingly.
💻 Technical Criteria
Given FDA reference number processing is required for a cargo
When The system checks for existing N9 reference segments
Then The system determines if an N9 segment exists and routes processing accordingly
R-GCX016E-cbl-01741 Create New N9 Reference Segment
Action Rules
📊 Business Logic Narrative
When the process 'Create New N9 Reference Segment' is invoked, and assuming that no existing n9 reference segment exists for the cargo, when fda reference number processing is required, the desired outcome is that a new n9 reference segment is created to store the fda reference number.
💻 Technical Criteria
Given No existing N9 reference segment exists for the cargo
When FDA reference number processing is required
Then A new N9 reference segment is created to store the FDA reference number
R-GCX016E-cbl-01742 Update Existing N9 Reference Segment
Action Rules
📊 Business Logic Narrative
When the process 'Update Existing N9 Reference Segment' is invoked, and assuming that an existing n9 reference segment exists for the cargo, when fda reference number processing is required, the desired outcome is that the existing n9 reference segment is updated with the fda reference number.
💻 Technical Criteria
Given An existing N9 reference segment exists for the cargo
When FDA reference number processing is required
Then The existing N9 reference segment is updated with the FDA reference number
R-GCX016E-cbl-01745 Insert N9 Reference Segment
Action Rules
📊 Business Logic Narrative
When the process 'Insert N9 Reference Segment' is invoked, and assuming that a new n9 reference segment needs to be created with fda reference number, when the system processes the segment insertion, the desired outcome is that the n9 reference segment is inserted with the fda reference information into the cargo record.
💻 Technical Criteria
Given A new N9 reference segment needs to be created with FDA reference number
When The system processes the segment insertion
Then The N9 reference segment is inserted with the FDA reference information into the cargo record
R-GCX016E-cbl-01747 Prepare Follower Manifest Data
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Follower Manifest Data' is invoked, and assuming that a follower manifest has been identified for processing, when the system prepares follower manifest data, the desired outcome is that all required manifest data elements including cargo information, quantities, and entry numbers are prepared for message creation.
💻 Technical Criteria
Given A follower manifest has been identified for processing
When The system prepares follower manifest data
Then All required manifest data elements including cargo information, quantities, and entry numbers are prepared for message creation
R-GCX016E-cbl-01750 Include Cargo Quantities in Message
Process Rules
📊 Business Logic Narrative
When the process 'Include Cargo Quantities in Message' is invoked, and assuming that a follower manifest message is being prepared and cargo quantities are available, when the system includes cargo quantities in the message, the desired outcome is that all relevant cargo quantities are included in the follower manifest message.
💻 Technical Criteria
Given A follower manifest message is being prepared and cargo quantities are available
When The system includes cargo quantities in the message
Then All relevant cargo quantities are included in the follower manifest message
R-GCX016E-cbl-01754 Update Comprehensive Cargo Tracking
Process Rules
📊 Business Logic Narrative
When the process 'Update Comprehensive Cargo Tracking' is invoked, and assuming that a follower manifest has been processed and linked to its lead manifest, when the system updates comprehensive cargo tracking, the desired outcome is that the cargo tracking system is updated with complete follower manifest information for full visibility.
💻 Technical Criteria
Given A follower manifest has been processed and linked to its lead manifest
When The system updates comprehensive cargo tracking
Then The cargo tracking system is updated with complete follower manifest information for full visibility
R-GCX016E-cbl-01757 Receive Bond Number as Search Key
Validation Rules
📊 Business Logic Narrative
When the process 'Receive Bond Number as Search Key' is invoked, and assuming that a cargo lookup request is initiated, when the system receives the search parameters, the desired outcome is that the bond number must be present and valid as the primary search key.
💻 Technical Criteria
Given A cargo lookup request is initiated
When The system receives the search parameters
Then The bond number must be present and valid as the primary search key
R-GCX016E-cbl-01758 Call GCCUSIO2 Database Interface
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCUSIO2 Database Interface' is invoked, and assuming that a valid bond number is provided for search, when the system needs to access cargo database records, the desired outcome is that the gccusio2 database interface program must be invoked with the bond number parameter.
💻 Technical Criteria
Given A valid bond number is provided for search
When The system needs to access cargo database records
Then The GCCUSIO2 database interface program must be invoked with the bond number parameter
R-GCX016E-cbl-01759 Search GCSUSRT US Cargo Root Segments
Process Rules
📊 Business Logic Narrative
When the process 'Search GCSUSRT US Cargo Root Segments' is invoked, and assuming that the database interface is active and bond number is provided, when the system searches the gcsusrt table, the desired outcome is that all cargo root segments with matching bond numbers must be identified and retrieved.
💻 Technical Criteria
Given The database interface is active and bond number is provided
When The system searches the GCSUSRT table
Then All cargo root segments with matching bond numbers must be identified and retrieved
R-GCX016E-cbl-01760 First Cargo Record Found?
Decision Rules
📊 Business Logic Narrative
When the process 'First Cargo Record Found?' is invoked, and assuming that a search has been performed on the cargo database using bond number, when the system evaluates the search results, the desired outcome is that if no cargo records are found for the bond number, the system must return 'no records found' status, otherwise proceed with record retrieval.
💻 Technical Criteria
Given A search has been performed on the cargo database using bond number
When The system evaluates the search results
Then If no cargo records are found for the bond number, the system must return 'No Records Found' status, otherwise proceed with record retrieval
R-GCX016E-cbl-01761 Retrieve First Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve First Cargo Record' is invoked, and assuming that at least one cargo record exists for the specified bond number, when the system processes the first matching record, the desired outcome is that the complete cargo record data must be retrieved and made available for processing.
💻 Technical Criteria
Given At least one cargo record exists for the specified bond number
When The system processes the first matching record
Then The complete cargo record data must be retrieved and made available for processing
R-GCX016E-cbl-01762 Set Bond Index Position
Process Rules
📊 Business Logic Narrative
When the process 'Set Bond Index Position' is invoked, and assuming that the first cargo record has been successfully retrieved, when the system prepares for additional record searches, the desired outcome is that the bond index position must be set to enable sequential access to remaining records with the same bond number.
💻 Technical Criteria
Given The first cargo record has been successfully retrieved
When The system prepares for additional record searches
Then The bond index position must be set to enable sequential access to remaining records with the same bond number
R-GCX016E-cbl-01763 Search for Subsequent Records
Process Rules
📊 Business Logic Narrative
When the process 'Search for Subsequent Records' is invoked, and assuming that the first cargo record has been processed and bond index position is set, when the system searches for additional records, the desired outcome is that all remaining cargo records with the same bond number must be identified in sequential order.
💻 Technical Criteria
Given The first cargo record has been processed and bond index position is set
When The system searches for additional records
Then All remaining cargo records with the same bond number must be identified in sequential order
R-GCX016E-cbl-01765 Retrieve Next Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Next Cargo Record' is invoked, and assuming that additional cargo records exist with the same bond number, when the system processes the next record in sequence, the desired outcome is that the complete cargo record data must be retrieved and prepared for validation.
💻 Technical Criteria
Given Additional cargo records exist with the same bond number
When The system processes the next record in sequence
Then The complete cargo record data must be retrieved and prepared for validation
R-GCX016E-cbl-01766 Validate Status Code
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Status Code' is invoked, and assuming that a cargo record has been retrieved from the database, when the system examines the record's status code, the desired outcome is that the status code must be validated against business rules to determine if the record should be included in processing.
💻 Technical Criteria
Given A cargo record has been retrieved from the database
When The system examines the record's status code
Then The status code must be validated against business rules to determine if the record should be included in processing
R-GCX016E-cbl-01767 Status Code Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Status Code Valid?' is invoked, and assuming that a cargo record's status code has been validated, when the system evaluates the validation results, the desired outcome is that if the status code is valid, the record must be considered for inclusion in the cargo processing list, otherwise the record must be excluded and the search must continue.
💻 Technical Criteria
Given A cargo record's status code has been validated
When The system evaluates the validation results
Then If the status code is valid, the record must be considered for inclusion in the cargo processing list, otherwise the record must be excluded and the search must continue
R-GCX016E-cbl-01768 Add to Cargo Processing List
Process Rules
📊 Business Logic Narrative
When the process 'Add to Cargo Processing List' is invoked, and assuming that a cargo record has a valid status code, when the system determines the record should be included, the desired outcome is that the cargo record must be added to the cargo processing list for further business processing.
💻 Technical Criteria
Given A cargo record has a valid status code
When The system determines the record should be included
Then The cargo record must be added to the cargo processing list for further business processing
R-GCX016E-cbl-01769 Continue Search Loop
Process Rules
📊 Business Logic Narrative
When the process 'Continue Search Loop' is invoked, and assuming that a cargo record has been processed (either included or excluded), when the system needs to check for additional records, the desired outcome is that the search loop must continue to evaluate remaining cargo records with the same bond number.
💻 Technical Criteria
Given A cargo record has been processed (either included or excluded)
When The system needs to check for additional records
Then The search loop must continue to evaluate remaining cargo records with the same bond number
R-GCX016E-cbl-01770 Complete Bond Lookup
Process Rules
📊 Business Logic Narrative
When the process 'Complete Bond Lookup' is invoked, and assuming that all cargo records with the specified bond number have been evaluated, when no more records exist with the same bond number, the desired outcome is that the bond lookup process must be completed and the system must prepare to return the cargo record set.
💻 Technical Criteria
Given All cargo records with the specified bond number have been evaluated
When No more records exist with the same bond number
Then The bond lookup process must be completed and the system must prepare to return the cargo record set
R-GCX016E-cbl-01771 Return Cargo Record Set
Process Rules
📊 Business Logic Narrative
When the process 'Return Cargo Record Set' is invoked, and assuming that the bond lookup process has been completed, when the system has identified all valid cargo records for the bond number, the desired outcome is that the complete set of cargo records must be returned to the calling process for further business operations.
💻 Technical Criteria
Given The bond lookup process has been completed
When The system has identified all valid cargo records for the bond number
Then The complete set of cargo records must be returned to the calling process for further business operations
R-GCX016E-cbl-01773 Return No Records Found
Process Rules
📊 Business Logic Narrative
When the process 'Return No Records Found' is invoked, and assuming that no cargo records exist for the bond number or an error has occurred, when the system completes the lookup process, the desired outcome is that a 'no records found' status must be returned to indicate that no valid cargo records are available for processing.
💻 Technical Criteria
Given No cargo records exist for the bond number or an error has occurred
When The system completes the lookup process
Then A 'No Records Found' status must be returned to indicate that no valid cargo records are available for processing
R-GCX016E-cbl-01774 Extract Car ID from Input Message
Process Rules
📊 Business Logic Narrative
When the process 'Extract Car ID from Input Message' is invoked, and assuming that an input message containing car identification information is received, when the system processes the message to extract car id, the desired outcome is that the car id is extracted and made available for database search operations.
💻 Technical Criteria
Given An input message containing car identification information is received
When The system processes the message to extract car ID
Then The car ID is extracted and made available for database search operations
R-GCX016E-cbl-01776 Format Car ID for Database Search
Process Rules
📊 Business Logic Narrative
When the process 'Format Car ID for Database Search' is invoked, and assuming that a raw car id has been extracted from the input message, when the system formats the car id for database compatibility, the desired outcome is that the car id is properly formatted and ready for use in database search operations.
💻 Technical Criteria
Given A raw car ID has been extracted from the input message
When The system formats the car ID for database compatibility
Then The car ID is properly formatted and ready for use in database search operations
R-GCX016E-cbl-01780 Retrieve First Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve First Cargo Record' is invoked, and assuming that a matching cargo record has been found in the database, when the system retrieves the first cargo record, the desired outcome is that the first matching cargo record is loaded and available for processing.
💻 Technical Criteria
Given A matching cargo record has been found in the database
When The system retrieves the first cargo record
Then The first matching cargo record is loaded and available for processing
R-GCX016E-cbl-01781 Set Record Found Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Record Found Flag' is invoked, and assuming that the first cargo record has been successfully retrieved, when the system updates the record found status, the desired outcome is that the record found flag is set to indicate successful cargo record retrieval.
💻 Technical Criteria
Given The first cargo record has been successfully retrieved
When The system updates the record found status
Then The record found flag is set to indicate successful cargo record retrieval
R-GCX016E-cbl-01782 Check for Additional Records
Decision Rules
📊 Business Logic Narrative
When the process 'Check for Additional Records' is invoked, and assuming that the first cargo record has been retrieved successfully, when the system checks for additional records with the same search key, the desired outcome is that the system determines whether more matching cargo records exist.
💻 Technical Criteria
Given The first cargo record has been retrieved successfully
When The system checks for additional records with the same search key
Then The system determines whether more matching cargo records exist
R-GCX016E-cbl-01783 More Records with Same Key?
Decision Rules
📊 Business Logic Narrative
When the process 'More Records with Same Key?' is invoked, and assuming that the system is checking for additional cargo records, when the database search continues for more records with the same key, the desired outcome is that the system determines if additional matching records are available for retrieval.
💻 Technical Criteria
Given The system is checking for additional cargo records
When The database search continues for more records with the same key
Then The system determines if additional matching records are available for retrieval
R-GCX016E-cbl-01784 Retrieve Next Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Next Cargo Record' is invoked, and assuming that additional matching cargo records have been identified, when the system retrieves the next cargo record, the desired outcome is that the next matching cargo record is loaded and available for processing.
💻 Technical Criteria
Given Additional matching cargo records have been identified
When The system retrieves the next cargo record
Then The next matching cargo record is loaded and available for processing
R-GCX016E-cbl-01785 Add to Cargo Record List
Process Rules
📊 Business Logic Narrative
When the process 'Add to Cargo Record List' is invoked, and assuming that a cargo record has been successfully retrieved from the database, when the system adds the record to the cargo record collection, the desired outcome is that the cargo record is included in the list of records for processing.
💻 Technical Criteria
Given A cargo record has been successfully retrieved from the database
When The system adds the record to the cargo record collection
Then The cargo record is included in the list of records for processing
R-GCX016E-cbl-01786 Continue Search for Additional Records
Process Rules
📊 Business Logic Narrative
When the process 'Continue Search for Additional Records' is invoked, and assuming that a cargo record has been added to the collection, when the system continues searching for additional records, the desired outcome is that the search process loops back to check for more matching cargo records.
💻 Technical Criteria
Given A cargo record has been added to the collection
When The system continues searching for additional records
Then The search process loops back to check for more matching cargo records
R-GCX016E-cbl-01787 Return All Found Records
Process Rules
📊 Business Logic Narrative
When the process 'Return All Found Records' is invoked, and assuming that all matching cargo records have been retrieved and collected, when no more matching records exist in the database, the desired outcome is that the complete collection of found cargo records is returned for business processing.
💻 Technical Criteria
Given All matching cargo records have been retrieved and collected
When No more matching records exist in the database
Then The complete collection of found cargo records is returned for business processing
R-GCX016E-cbl-01789 Generate Not Found Message
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Not Found Message', assuming that no cargo records were found matching the search criteria, when the system generates a not found message, the desired outcome is that an appropriate message is created indicating that no matching cargo records exist.
💻 Technical Criteria
EXCLUDING No cargo records were found matching the search criteria
When The system generates a not found message
Then An appropriate message is created indicating that no matching cargo records exist
R-GCX016E-cbl-01791 Format Car ID Using Standard Rules
Computation Rules
📊 Business Logic Narrative
When the process 'Format Car ID Using Standard Rules' is invoked, and assuming that raw car equipment initial and number from n7 segment data, when the system processes the car information for cprs cargo creation, the desired outcome is that the system formats the car id by combining equipment initial and number according to standard formatting rules.
💻 Technical Criteria
Given Raw car equipment initial and number from N7 segment data
When The system processes the car information for CPRS cargo creation
Then The system formats the car ID by combining equipment initial and number according to standard formatting rules
R-GCX016E-cbl-01792 Set CPRS-Specific Flags and Identifiers
Definitional Rules
📊 Business Logic Narrative
When the process 'Set CPRS-Specific Flags and Identifiers' is invoked, and assuming that a new cprs cargo record being created, when the system initializes cprs cargo attributes, the desired outcome is that the system sets cprs-specific processing flags and identifiers to enable proper cprs handling.
💻 Technical Criteria
Given A new CPRS cargo record being created
When The system initializes CPRS cargo attributes
Then The system sets CPRS-specific processing flags and identifiers to enable proper CPRS handling
R-GCX016E-cbl-01793 Build Cargo Record from X4 Segment Data
Process Rules
📊 Business Logic Narrative
When the process 'Build Cargo Record from X4 Segment Data' is invoked, and assuming that x4 segment data containing disposition codes, quantities, and entry information, when the system builds a new cprs cargo record, the desired outcome is that the system populates cargo record fields with disposition code, quantity, entry number, and related x4 segment information.
💻 Technical Criteria
Given X4 segment data containing disposition codes, quantities, and entry information
When The system builds a new CPRS cargo record
Then The system populates cargo record fields with disposition code, quantity, entry number, and related X4 segment information
R-GCX016E-cbl-01794 Build Cargo Record from N7 Segment Data
Process Rules
📊 Business Logic Narrative
When the process 'Build Cargo Record from N7 Segment Data' is invoked, and assuming that n7 segment data containing equipment initial, number, and related equipment information, when the system builds a new cprs cargo record, the desired outcome is that the system populates cargo record fields with equipment information, car id, and related n7 segment data.
💻 Technical Criteria
Given N7 segment data containing equipment initial, number, and related equipment information
When The system builds a new CPRS cargo record
Then The system populates cargo record fields with equipment information, car ID, and related N7 segment data
R-GCX016E-cbl-01795 Set CPRS Bond Information
Definitional Rules
📊 Business Logic Narrative
When the process 'Set CPRS Bond Information' is invoked, and assuming that a new cprs cargo record with disposition code and entry information, when the system sets bond information for the cprs cargo, the desired outcome is that the system assigns bond number and related bond information based on cprs processing rules.
💻 Technical Criteria
Given A new CPRS cargo record with disposition code and entry information
When The system sets bond information for the CPRS cargo
Then The system assigns bond number and related bond information based on CPRS processing rules
R-GCX016E-cbl-01796 Set CPRS Broker Information
Definitional Rules
📊 Business Logic Narrative
When the process 'Set CPRS Broker Information' is invoked, and assuming that a new cprs cargo record and access to carrier information database, when the system sets broker information for the cprs cargo, the desired outcome is that the system assigns broker code and related broker information from the carrier information database.
💻 Technical Criteria
Given A new CPRS cargo record and access to carrier information database
When The system sets broker information for the CPRS cargo
Then The system assigns broker code and related broker information from the carrier information database
R-GCX016E-cbl-01797 Initialize Cargo Status Arrays
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Cargo Status Arrays' is invoked, and assuming that a new cprs cargo record being created, when the system initializes cargo status tracking, the desired outcome is that the system creates empty status arrays and sets up status segment structures for tracking cprs cargo disposition codes.
💻 Technical Criteria
Given A new CPRS cargo record being created
When The system initializes cargo status tracking
Then The system creates empty status arrays and sets up status segment structures for tracking CPRS cargo disposition codes
R-GCX016E-cbl-01798 Set Default CPRS Processing Flags
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Default CPRS Processing Flags' is invoked, and assuming that a new cprs cargo record with basic information populated, when the system sets default processing flags, the desired outcome is that the system assigns default values for processing flags that control cprs cargo handling and workflow.
💻 Technical Criteria
Given A new CPRS cargo record with basic information populated
When The system sets default processing flags
Then The system assigns default values for processing flags that control CPRS cargo handling and workflow
R-GCX016E-cbl-01799 Insert New CPRS Cargo Record into Database
Action Rules
📊 Business Logic Narrative
When the process 'Insert New CPRS Cargo Record into Database' is invoked, and assuming that a complete cprs cargo record ready for database insertion, when the system attempts to insert the record into the us cargo root database, the desired outcome is that the system successfully adds the new cprs cargo record to the database or returns an insertion failure status.
💻 Technical Criteria
Given A complete CPRS cargo record ready for database insertion
When The system attempts to insert the record into the US cargo root database
Then The system successfully adds the new CPRS cargo record to the database or returns an insertion failure status
R-GCX016E-cbl-01800 Database Insert Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Database Insert Successful?' is invoked, and assuming that an attempt to insert a new cprs cargo record into the database, when the system checks the database insertion result, the desired outcome is that the system determines whether the insertion was successful or failed based on the database response.
💻 Technical Criteria
Given An attempt to insert a new CPRS cargo record into the database
When The system checks the database insertion result
Then The system determines whether the insertion was successful or failed based on the database response
R-GCX016E-cbl-01801 Log CPRS Cargo Creation Action
Process Rules
📊 Business Logic Narrative
When the process 'Log CPRS Cargo Creation Action' is invoked, and assuming that a successfully created cprs cargo record, when the system logs the creation action, the desired outcome is that the system records the cprs cargo creation event with relevant details for audit trail and tracking.
💻 Technical Criteria
Given A successfully created CPRS cargo record
When The system logs the creation action
Then The system records the CPRS cargo creation event with relevant details for audit trail and tracking
R-GCX016E-cbl-01802 Generate CPRS Creation Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate CPRS Creation Notification' is invoked, and assuming that a successfully created and logged cprs cargo record, when the system generates creation notifications, the desired outcome is that the system sends notifications to appropriate recipients about the new cprs cargo creation.
💻 Technical Criteria
Given A successfully created and logged CPRS cargo record
When The system generates creation notifications
Then The system sends notifications to appropriate recipients about the new CPRS cargo creation
R-GCX016E-cbl-01803 Handle CPRS Creation Error
Action Rules
📊 Business Logic Narrative
When the process 'Handle CPRS Creation Error' is invoked, and assuming that a failed cprs cargo record insertion or creation error, when the system handles the creation error, the desired outcome is that the system processes the error condition and takes appropriate corrective action or error reporting.
💻 Technical Criteria
Given A failed CPRS cargo record insertion or creation error
When The system handles the creation error
Then The system processes the error condition and takes appropriate corrective action or error reporting
R-GCX016E-cbl-01805 Initialize New Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Initialize New Cargo Record' is invoked, and assuming that a foreign bill requires a new cargo record, when the system begins cargo record creation, the desired outcome is that a new cargo record structure is initialized with default values and cleared fields.
💻 Technical Criteria
Given A foreign bill requires a new cargo record
When The system begins cargo record creation
Then A new cargo record structure is initialized with default values and cleared fields
R-GCX016E-cbl-01806 Set Up Cargo Record with X4 Segment Data
Process Rules
📊 Business Logic Narrative
When the process 'Set Up Cargo Record with X4 Segment Data' is invoked, and assuming that an x4 segment contains cargo disposition information, when the system processes the x4 segment for new cargo creation, the desired outcome is that the cargo record is populated with disposition code, entry number, quantity, and date/time information from the x4 segment.
💻 Technical Criteria
Given An X4 segment contains cargo disposition information
When The system processes the X4 segment for new cargo creation
Then The cargo record is populated with disposition code, entry number, quantity, and date/time information from the X4 segment
R-GCX016E-cbl-01807 Set Up Cargo Record with N7 Segment Data
Process Rules
📊 Business Logic Narrative
When the process 'Set Up Cargo Record with N7 Segment Data' is invoked, and assuming that an n7 segment contains equipment information, when the system processes the n7 segment for new cargo creation, the desired outcome is that the cargo record is populated with equipment initial, equipment number, and formatted car id from the n7 segment.
💻 Technical Criteria
Given An N7 segment contains equipment information
When The system processes the N7 segment for new cargo creation
Then The cargo record is populated with equipment initial, equipment number, and formatted car ID from the N7 segment
R-GCX016E-cbl-01808 Build Foreign Manifest from M10 Segments
Process Rules
📊 Business Logic Narrative
When the process 'Build Foreign Manifest from M10 Segments' is invoked, and assuming that m10 segments contain manifest header information, when the system processes m10 segments for foreign cargo creation, the desired outcome is that the cargo record is populated with vessel name, voyage number, and manifest routing information from the m10 segments.
💻 Technical Criteria
Given M10 segments contain manifest header information
When The system processes M10 segments for foreign cargo creation
Then The cargo record is populated with vessel name, voyage number, and manifest routing information from the M10 segments
R-GCX016E-cbl-01809 Extract SCAC Information
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract SCAC Information' is invoked, and assuming that manifest information contains carrier identification, when the system processes carrier information for foreign cargo, the desired outcome is that the scac code is extracted and stored in the cargo record for carrier identification.
💻 Technical Criteria
Given Manifest information contains carrier identification
When The system processes carrier information for foreign cargo
Then The SCAC code is extracted and stored in the cargo record for carrier identification
R-GCX016E-cbl-01810 Extract Transport Type
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Transport Type' is invoked, and assuming that manifest data contains transportation mode information, when the system processes transportation details for foreign cargo, the desired outcome is that the transport type is identified and recorded in the cargo record.
💻 Technical Criteria
Given Manifest data contains transportation mode information
When The system processes transportation details for foreign cargo
Then The transport type is identified and recorded in the cargo record
R-GCX016E-cbl-01811 Extract Country Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Country Code' is invoked, and assuming that manifest data contains country identification information, when the system processes location details for foreign cargo, the desired outcome is that the country code is extracted and assigned to the cargo record.
💻 Technical Criteria
Given Manifest data contains country identification information
When The system processes location details for foreign cargo
Then The country code is extracted and assigned to the cargo record
R-GCX016E-cbl-01812 Extract Vessel Details
Process Rules
📊 Business Logic Narrative
When the process 'Extract Vessel Details' is invoked, and assuming that m10 segments contain vessel identification and voyage information, when the system processes vessel details for foreign cargo, the desired outcome is that vessel name, voyage number, and vessel identifiers are extracted and stored in the cargo record.
💻 Technical Criteria
Given M10 segments contain vessel identification and voyage information
When The system processes vessel details for foreign cargo
Then Vessel name, voyage number, and vessel identifiers are extracted and stored in the cargo record
R-GCX016E-cbl-01813 Format Car ID for Database
Computation Rules
📊 Business Logic Narrative
When the process 'Format Car ID for Database' is invoked, and assuming that equipment initial and number are available from n7 segment, when the system prepares car identification for database storage, the desired outcome is that the car id is formatted into standardized database format combining equipment initial and number.
💻 Technical Criteria
Given Equipment initial and number are available from N7 segment
When The system prepares car identification for database storage
Then The car ID is formatted into standardized database format combining equipment initial and number
R-GCX016E-cbl-01814 Insert New Cargo Record into Database
Action Rules
📊 Business Logic Narrative
When the process 'Insert New Cargo Record into Database' is invoked, and assuming that a complete foreign cargo record has been constructed with all required information, when the system performs database insertion, the desired outcome is that the new cargo record is successfully inserted into the cargo database.
💻 Technical Criteria
Given A complete foreign cargo record has been constructed with all required information
When The system performs database insertion
Then The new cargo record is successfully inserted into the cargo database
R-GCX016E-cbl-01815 Validate Record Creation
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Record Creation' is invoked, and assuming that a cargo record insertion has been attempted, when the system checks the insertion result, the desired outcome is that the system confirms successful record creation or identifies creation failures.
💻 Technical Criteria
Given A cargo record insertion has been attempted
When The system checks the insertion result
Then The system confirms successful record creation or identifies creation failures
R-GCX016E-cbl-01816 Log Foreign Cargo Creation
Process Rules
📊 Business Logic Narrative
When the process 'Log Foreign Cargo Creation' is invoked, and assuming that a foreign cargo record has been successfully created, when the system completes the cargo creation process, the desired outcome is that the cargo creation event is logged with relevant details for audit and tracking.
💻 Technical Criteria
Given A foreign cargo record has been successfully created
When The system completes the cargo creation process
Then The cargo creation event is logged with relevant details for audit and tracking
R-GCX016E-cbl-01817 Foreign Cargo Record Created Successfully
Process Rules
📊 Business Logic Narrative
When the process 'Foreign Cargo Record Created Successfully' is invoked, and assuming that all foreign cargo creation steps have been completed, when the system finalizes the cargo creation process, the desired outcome is that the system confirms successful creation of the foreign cargo record and makes it available for further processing.
💻 Technical Criteria
Given All foreign cargo creation steps have been completed
When The system finalizes the cargo creation process
Then The system confirms successful creation of the foreign cargo record and makes it available for further processing
R-GCX016E-cbl-01818 Apply Standard Formatting Rules
Computation Rules
📊 Business Logic Narrative
When the process 'Apply Standard Formatting Rules' is invoked, and assuming that an n7 segment contains equipment initial and equipment number, when the system processes the n7 segment for car id formatting, the desired outcome is that the equipment initial and number are concatenated and formatted into a standardized car id format.
💻 Technical Criteria
Given An N7 segment contains equipment initial and equipment number
When The system processes the N7 segment for car ID formatting
Then The equipment initial and number are concatenated and formatted into a standardized car ID format
R-GCX016E-cbl-01819 Validate Car ID Length and Characters
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Car ID Length and Characters' is invoked, and assuming that a formatted car id from equipment initial and number, when the system validates the car id format, the desired outcome is that the car id must meet specified length requirements and contain only valid characters.
💻 Technical Criteria
Given A formatted car ID from equipment initial and number
When The system validates the car ID format
Then The car ID must meet specified length requirements and contain only valid characters
R-GCX016E-cbl-01820 CPRS Traffic?
Decision Rules
📊 Business Logic Narrative
When the process 'CPRS Traffic?' is invoked, and assuming that a cargo record with traffic type information, when the system checks if the cargo is cprs traffic, the desired outcome is that the system identifies whether cprs-specific formatting rules should be applied.
💻 Technical Criteria
Given A cargo record with traffic type information
When The system checks if the cargo is CPRS traffic
Then The system identifies whether CPRS-specific formatting rules should be applied
R-GCX016E-cbl-01821 Apply CPRS Specific Formatting
Computation Rules
📊 Business Logic Narrative
When the process 'Apply CPRS Specific Formatting' is invoked, and assuming that a car id that belongs to cprs traffic type, when the system applies cprs-specific formatting rules, the desired outcome is that the car id is formatted according to cprs business requirements which may clear or modify the standard car id format.
💻 Technical Criteria
Given A car ID that belongs to CPRS traffic type
When The system applies CPRS-specific formatting rules
Then The car ID is formatted according to CPRS business requirements which may clear or modify the standard car ID format
R-GCX016E-cbl-01822 Apply Standard Formatting
Computation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Apply Standard Formatting', assuming that a car id that is not cprs traffic type, when the system applies standard formatting rules, the desired outcome is that the car id is formatted using standard business formatting requirements.
💻 Technical Criteria
EXCLUDING A car ID that is not CPRS traffic type
When The system applies standard formatting rules
Then The car ID is formatted using standard business formatting requirements
R-GCX016E-cbl-01823 Update Car ID in Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Update Car ID in Cargo Record' is invoked, and assuming that a properly formatted and validated car id, when the system updates the cargo record, the desired outcome is that the car id information is stored in the cargo record for future processing and tracking.
💻 Technical Criteria
Given A properly formatted and validated car ID
When The system updates the cargo record
Then The car ID information is stored in the cargo record for future processing and tracking
R-GCX016E-cbl-01824 Generate Format Error
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Format Error', assuming that a car id that fails format validation, when the system detects invalid car id format, the desired outcome is that an appropriate format error is generated to indicate the car id formatting issue.
💻 Technical Criteria
EXCLUDING A car ID that fails format validation
When The system detects invalid car ID format
Then An appropriate format error is generated to indicate the car ID formatting issue
R-GCX016E-cbl-01825 Log Formatting Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Formatting Action' is invoked, and assuming that a completed car id formatting process, when the system completes car id formatting (successful or with errors), the desired outcome is that the formatting action and results are logged for audit trail and troubleshooting purposes.
💻 Technical Criteria
Given A completed car ID formatting process
When The system completes car ID formatting (successful or with errors)
Then The formatting action and results are logged for audit trail and troubleshooting purposes
R-GCX016E-cbl-01826 Cargo Disposition Code Processing
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Disposition Code Processing' is invoked, and assuming that a cargo is being processed with disposition codes, when the disposition code is 95, the desired outcome is that the system should initiate bond information clearing process.
💻 Technical Criteria
Given A cargo is being processed with disposition codes
When The disposition code is 95
Then The system should initiate bond information clearing process
R-GCX016E-cbl-01834 Update Cargo Status
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status' is invoked, and assuming that bond clearing action has been logged, when the system updates cargo status, the desired outcome is that the cargo status should be updated to reflect that bond information has been cleared.
💻 Technical Criteria
Given Bond clearing action has been logged
When The system updates cargo status
Then The cargo status should be updated to reflect that bond information has been cleared
R-GCX016E-cbl-01835 Generate Cancellation Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Cancellation Notification' is invoked, and assuming that cargo status has been updated after bond clearing, when the system generates notifications, the desired outcome is that a cancellation notification should be generated and sent to appropriate recipients regarding the bond clearing.
💻 Technical Criteria
Given Cargo status has been updated after bond clearing
When The system generates notifications
Then A cancellation notification should be generated and sent to appropriate recipients regarding the bond clearing
R-GCX016E-cbl-01836 Continue Cargo Processing
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Continue Cargo Processing', assuming that bond clearing operations have been completed or disposition code is not 95, when the system continues cargo processing, the desired outcome is that normal cargo processing workflow should continue with the next processing steps.
💻 Technical Criteria
EXCLUDING Bond clearing operations have been completed OR disposition code is not 95
When The system continues cargo processing
Then Normal cargo processing workflow should continue with the next processing steps
R-GCX016E-cbl-01847 Entry Type Code Present?
Validation Rules
📊 Business Logic Narrative
When the process 'Entry Type Code Present?' is invoked, and assuming that an x4 segment is being processed for cargo disposition, when the system checks for the presence of an entry type code in the segment, the desired outcome is that if entry type code is present, proceed to lookup conversion; if not present, skip entry type processing.
💻 Technical Criteria
Given An X4 segment is being processed for cargo disposition
When The system checks for the presence of an entry type code in the segment
Then If entry type code is present, proceed to lookup conversion; if not present, skip entry type processing
R-GCX016E-cbl-01853 Border Crossing Scenario?
Decision Rules
📊 Business Logic Narrative
When the process 'Border Crossing Scenario?' is invoked, and assuming that entry type conversion has been completed, when the system evaluates if this is a border crossing scenario, the desired outcome is that if border crossing scenario detected, apply special border crossing rules; otherwise update cargo record directly.
💻 Technical Criteria
Given Entry type conversion has been completed
When The system evaluates if this is a border crossing scenario
Then If border crossing scenario detected, apply special border crossing rules; otherwise update cargo record directly
R-GCX016E-cbl-01854 Apply Special Border Crossing Rules
Process Rules
📊 Business Logic Narrative
When the process 'Apply Special Border Crossing Rules' is invoked, and assuming that a border crossing scenario has been detected, when the system applies special border crossing processing rules, the desired outcome is that execute border crossing specific logic before updating the cargo record.
💻 Technical Criteria
Given A border crossing scenario has been detected
When The system applies special border crossing processing rules
Then Execute border crossing specific logic before updating the cargo record
R-GCX016E-cbl-01855 Update Cargo Record with Converted Entry Type
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Record with Converted Entry Type' is invoked, and assuming that entry type conversion is complete and any special rules have been applied, when the system updates the cargo record, the desired outcome is that store the converted entry type value in the cargo record.
💻 Technical Criteria
Given Entry type conversion is complete and any special rules have been applied
When The system updates the cargo record
Then Store the converted entry type value in the cargo record
R-GCX016E-cbl-01856 Log Entry Type Conversion Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Entry Type Conversion Action' is invoked, and assuming that entry type conversion and cargo record update are complete, when the system performs logging operations, the desired outcome is that create a log entry documenting the entry type conversion action.
💻 Technical Criteria
Given Entry type conversion and cargo record update are complete
When The system performs logging operations
Then Create a log entry documenting the entry type conversion action
R-GCX016E-cbl-01857 Use Default Entry Type Value
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Use Default Entry Type Value', assuming that entry type code lookup did not find a valid conversion, when the system needs to assign an entry type value, the desired outcome is that use the default entry type value and proceed with cargo record update.
💻 Technical Criteria
EXCLUDING Entry type code lookup did not find a valid conversion
When The system needs to assign an entry type value
Then Use the default entry type value and proceed with cargo record update
R-GCX016E-cbl-01860 Set Master In-Bond Flag for Code 61
Decision Rules
📊 Business Logic Narrative
When the process 'Set Master In-Bond Flag for Code 61' is invoked, and assuming that an x4 segment is being processed and contains an entry type code, when the entry type code value is 61, the desired outcome is that the master in-bond flag is set for entry type code 61 and the cargo record is updated with master in-bond status.
💻 Technical Criteria
Given An X4 segment is being processed and contains an entry type code
When The entry type code value is 61
Then The master in-bond flag is set for entry type code 61 and the cargo record is updated with master in-bond status
R-GCX016E-cbl-01861 Set Master In-Bond Flag for Code 62
Decision Rules
📊 Business Logic Narrative
When the process 'Set Master In-Bond Flag for Code 62' is invoked, and assuming that an x4 segment is being processed and contains an entry type code, when the entry type code value is 62, the desired outcome is that the master in-bond flag is set for entry type code 62 and the cargo record is updated with master in-bond status.
💻 Technical Criteria
Given An X4 segment is being processed and contains an entry type code
When The entry type code value is 62
Then The master in-bond flag is set for entry type code 62 and the cargo record is updated with master in-bond status
R-GCX016E-cbl-01862 Set Master In-Bond Flag for Code 63
Decision Rules
📊 Business Logic Narrative
When the process 'Set Master In-Bond Flag for Code 63' is invoked, and assuming that an x4 segment is being processed and contains an entry type code, when the entry type code value is 63, the desired outcome is that the master in-bond flag is set for entry type code 63 and the cargo record is updated with master in-bond status.
💻 Technical Criteria
Given An X4 segment is being processed and contains an entry type code
When The entry type code value is 63
Then The master in-bond flag is set for entry type code 63 and the cargo record is updated with master in-bond status
R-GCX016E-cbl-01863 Set Master In-Bond Flag for Code 69
Decision Rules
📊 Business Logic Narrative
When the process 'Set Master In-Bond Flag for Code 69' is invoked, and assuming that an x4 segment is being processed and contains an entry type code, when the entry type code value is 69, the desired outcome is that the master in-bond flag is set for entry type code 69 and the cargo record is updated with master in-bond status.
💻 Technical Criteria
Given An X4 segment is being processed and contains an entry type code
When The entry type code value is 69
Then The master in-bond flag is set for entry type code 69 and the cargo record is updated with master in-bond status
R-GCX016E-cbl-01866 Update Cargo Record with Master In-Bond Status
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Record with Master In-Bond Status' is invoked, and assuming that a master in-bond flag has been set for entry type codes 61, 62, 63, or 69, when the cargo record needs to be updated with the master in-bond status, the desired outcome is that the cargo record is updated to reflect the master in-bond status for the specific entry type code.
💻 Technical Criteria
Given A master in-bond flag has been set for entry type codes 61, 62, 63, or 69
When The cargo record needs to be updated with the master in-bond status
Then The cargo record is updated to reflect the master in-bond status for the specific entry type code
R-GCX016E-cbl-01867 Log Master In-Bond Flag Setting Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Master In-Bond Flag Setting Action' is invoked, and assuming that a master in-bond flag has been set and cargo record has been updated, when the master in-bond flag setting action needs to be logged, the desired outcome is that the system logs the master in-bond flag setting action for audit trail purposes.
💻 Technical Criteria
Given A master in-bond flag has been set and cargo record has been updated
When The master in-bond flag setting action needs to be logged
Then The system logs the master in-bond flag setting action for audit trail purposes
R-GCX016E-cbl-01868 Is Cargo Cross-Border?
Decision Rules
📊 Business Logic Narrative
When the process 'Is Cargo Cross-Border?' is invoked, and assuming that a cargo record with location and routing data is being processed, when the system evaluates cargo characteristics for cross-border requirements, the desired outcome is that the cargo is identified as cross-border if it meets the criteria for international movement between us and canadian borders.
💻 Technical Criteria
Given A cargo record with location and routing data is being processed
When The system evaluates cargo characteristics for cross-border requirements
Then The cargo is identified as cross-border if it meets the criteria for international movement between US and Canadian borders
R-GCX016E-cbl-01869 Extract US Port Code from Location Data
Process Rules
📊 Business Logic Narrative
When the process 'Extract US Port Code from Location Data' is invoked, and assuming that cross-border cargo with location data containing us port information, when the system processes the cargo location data, the desired outcome is that the us port code is extracted from the location data for further processing.
💻 Technical Criteria
Given Cross-border cargo with location data containing US port information
When The system processes the cargo location data
Then The US port code is extracted from the location data for further processing
R-GCX016E-cbl-01870 Access Canadian Border Mapping Table
Action Rules
📊 Business Logic Narrative
When the process 'Access Canadian Border Mapping Table' is invoked, and assuming that a us port code has been extracted from cargo location data, when the system needs to find the corresponding canadian border port name, the desired outcome is that the canadian border mapping table is accessed for port code lookup.
💻 Technical Criteria
Given A US port code has been extracted from cargo location data
When The system needs to find the corresponding Canadian border port name
Then The Canadian border mapping table is accessed for port code lookup
R-GCX016E-cbl-01873 Set Canadian Border Location for Cargo
Process Rules
📊 Business Logic Narrative
When the process 'Set Canadian Border Location for Cargo' is invoked, and assuming that a canadian border port name has been successfully retrieved from the mapping table, when the system processes the mapping result, the desired outcome is that the canadian border location is set in the cargo record for cross-border processing.
💻 Technical Criteria
Given A Canadian border port name has been successfully retrieved from the mapping table
When The system processes the mapping result
Then The Canadian border location is set in the cargo record for cross-border processing
R-GCX016E-cbl-01874 Update Cargo Routing Information
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo Routing Information' is invoked, and assuming that cargo with a set canadian border location, when the system updates cargo routing information, the desired outcome is that the routing information is updated to include the canadian border location for proper cargo flow.
💻 Technical Criteria
Given Cargo with a set Canadian border location
When The system updates cargo routing information
Then The routing information is updated to include the Canadian border location for proper cargo flow
R-GCX016E-cbl-01875 Log Border Crossing Information
Process Rules
📊 Business Logic Narrative
When the process 'Log Border Crossing Information' is invoked, and assuming that cargo with updated routing information including canadian border location, when the system completes the border location assignment, the desired outcome is that border crossing information is logged for audit trail and cargo tracking purposes.
💻 Technical Criteria
Given Cargo with updated routing information including Canadian border location
When The system completes the border location assignment
Then Border crossing information is logged for audit trail and cargo tracking purposes
R-GCX016E-cbl-01876 Use Default Border Location
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Use Default Border Location', assuming that a us port code that does not exist in the canadian border mapping table, when the system cannot find a valid mapping for the port code, the desired outcome is that a default border location is assigned to ensure cargo processing can continue.
💻 Technical Criteria
EXCLUDING A US port code that does not exist in the Canadian border mapping table
When The system cannot find a valid mapping for the port code
Then A default border location is assigned to ensure cargo processing can continue
R-GCX016E-cbl-01878 Continue Cargo Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue Cargo Processing' is invoked, and assuming that cargo with either mapped canadian border location or default border location assigned, when border location processing is complete, the desired outcome is that the system continues with normal cargo processing workflow.
💻 Technical Criteria
Given Cargo with either mapped Canadian border location or default border location assigned
When Border location processing is complete
Then The system continues with normal cargo processing workflow
R-GCX016E-cbl-01897 Receive Bond Number as Input
Validation Rules
📊 Business Logic Narrative
When the process 'Receive Bond Number as Input' is invoked, and assuming that a cargo retrieval request is initiated, when the system receives the bond number parameter, the desired outcome is that the bond number must be present and not empty to proceed with cargo search.
💻 Technical Criteria
Given A cargo retrieval request is initiated
When The system receives the bond number parameter
Then The bond number must be present and not empty to proceed with cargo search
R-GCX016E-cbl-01898 Initialize Bond Search Parameters
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Bond Search Parameters' is invoked, and assuming that a valid bond number is received, when the system prepares to search for cargo records, the desired outcome is that search parameters including bond index key and search criteria must be initialized with proper values.
💻 Technical Criteria
Given A valid bond number is received
When The system prepares to search for cargo records
Then Search parameters including bond index key and search criteria must be initialized with proper values
R-GCX016E-cbl-01899 Call GCCUSIO2 with Bond Index
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCUSIO2 with Bond Index' is invoked, and assuming that bond search parameters are properly initialized, when the system needs to retrieve cargo records for a specific bond, the desired outcome is that gccusio2 module must be called with bond index parameters to access the cargo database.
💻 Technical Criteria
Given Bond search parameters are properly initialized
When The system needs to retrieve cargo records for a specific bond
Then GCCUSIO2 module must be called with bond index parameters to access the cargo database
R-GCX016E-cbl-01900 Cargo Record Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Record Found?' is invoked, and assuming that a database search has been performed using bond index, when the system evaluates the search results, the desired outcome is that if no cargo records are found for the bond number, return 'no records found' status, otherwise proceed to retrieve the first record.
💻 Technical Criteria
Given A database search has been performed using bond index
When The system evaluates the search results
Then If no cargo records are found for the bond number, return 'No Records Found' status, otherwise proceed to retrieve the first record
R-GCX016E-cbl-01901 Retrieve First Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve First Cargo Record' is invoked, and assuming that at least one cargo record exists for the bond number, when the system begins cargo record processing, the desired outcome is that the first cargo record associated with the bond must be retrieved and made available for processing.
💻 Technical Criteria
Given At least one cargo record exists for the bond number
When The system begins cargo record processing
Then The first cargo record associated with the bond must be retrieved and made available for processing
R-GCX016E-cbl-01902 Check Status Code
Validation Rules
📊 Business Logic Narrative
When the process 'Check Status Code' is invoked, and assuming that a cargo record has been retrieved from the database, when the system examines the record's status code, the desired outcome is that the status code must be valid and indicate an active, processable record state.
💻 Technical Criteria
Given A cargo record has been retrieved from the database
When The system examines the record's status code
Then The status code must be valid and indicate an active, processable record state
R-GCX016E-cbl-01903 Status Code Valid?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Status Code Valid?', assuming that a cargo record has been retrieved and status code checked, when the status code is invalid or indicates an inactive record, the desired outcome is that return 'invalid status' error and do not process the record further.
💻 Technical Criteria
EXCLUDING A cargo record has been retrieved and status code checked
When The status code is invalid or indicates an inactive record
Then Return 'Invalid Status' error and do not process the record further
R-GCX016E-cbl-01904 Load Cargo Data into Working Storage
Process Rules
📊 Business Logic Narrative
When the process 'Load Cargo Data into Working Storage' is invoked, and assuming that a cargo record with valid status code has been retrieved, when the system needs to process the cargo data, the desired outcome is that all relevant cargo information must be loaded into working storage areas for subsequent processing operations.
💻 Technical Criteria
Given A cargo record with valid status code has been retrieved
When The system needs to process the cargo data
Then All relevant cargo information must be loaded into working storage areas for subsequent processing operations
R-GCX016E-cbl-01905 Check for Additional Records
Decision Rules
📊 Business Logic Narrative
When the process 'Check for Additional Records' is invoked, and assuming that the first cargo record for a bond has been processed, when the system checks for additional records, the desired outcome is that the system must determine if more cargo records exist for the same bond number.
💻 Technical Criteria
Given The first cargo record for a bond has been processed
When The system checks for additional records
Then The system must determine if more cargo records exist for the same bond number
R-GCX016E-cbl-01907 Retrieve Next Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Next Cargo Record' is invoked, and assuming that additional cargo records exist for the current bond number, when the system continues processing multiple bond records, the desired outcome is that the next cargo record in the sequence must be retrieved from the database.
💻 Technical Criteria
Given Additional cargo records exist for the current bond number
When The system continues processing multiple bond records
Then The next cargo record in the sequence must be retrieved from the database
R-GCX016E-cbl-01908 Validate Record Status
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Record Status' is invoked, and assuming that an additional cargo record has been retrieved for the bond, when the system validates the record before processing, the desired outcome is that the record status must be checked to ensure it represents an active, processable cargo.
💻 Technical Criteria
Given An additional cargo record has been retrieved for the bond
When The system validates the record before processing
Then The record status must be checked to ensure it represents an active, processable cargo
R-GCX016E-cbl-01909 Record Status Active?
Decision Rules
📊 Business Logic Narrative
When the process 'Record Status Active?' is invoked, and assuming that a cargo record status has been validated, when the system evaluates whether the record is active, the desired outcome is that if the record status is active, add it to the cargo processing list, otherwise skip to the next record.
💻 Technical Criteria
Given A cargo record status has been validated
When The system evaluates whether the record is active
Then If the record status is active, add it to the cargo processing list, otherwise skip to the next record
R-GCX016E-cbl-01910 Add to Cargo Processing List
Process Rules
📊 Business Logic Narrative
When the process 'Add to Cargo Processing List' is invoked, and assuming that a cargo record has been validated as active, when the record needs to be included in processing, the desired outcome is that the cargo record must be added to the cargo processing list for further business rule application.
💻 Technical Criteria
Given A cargo record has been validated as active
When The record needs to be included in processing
Then The cargo record must be added to the cargo processing list for further business rule application
R-GCX016E-cbl-01911 Continue to Next Record
Process Rules
📊 Business Logic Narrative
When the process 'Continue to Next Record' is invoked, and assuming that a cargo record has been determined to be inactive, when the system processes multiple records for a bond, the desired outcome is that skip the inactive record and continue processing the next record in the sequence.
💻 Technical Criteria
Given A cargo record has been determined to be inactive
When The system processes multiple records for a bond
Then Skip the inactive record and continue processing the next record in the sequence
R-GCX016E-cbl-01912 Complete Bond Index Retrieval
Process Rules
📊 Business Logic Narrative
When the process 'Complete Bond Index Retrieval' is invoked, and assuming that all cargo records for a bond number have been processed, when no more records exist for the current bond, the desired outcome is that complete the bond index retrieval operation and return the processed cargo list.
💻 Technical Criteria
Given All cargo records for a bond number have been processed
When No more records exist for the current bond
Then Complete the bond index retrieval operation and return the processed cargo list
R-GCX016E-cbl-01913 Return No Records Found
Process Rules
📊 Business Logic Narrative
When the process 'Return No Records Found' is invoked, and assuming that a bond number search has been performed, when no cargo records are found for the specified bond, the desired outcome is that return 'no records found' status to indicate that no cargo exists for the bond number.
💻 Technical Criteria
Given A bond number search has been performed
When No cargo records are found for the specified bond
Then Return 'No Records Found' status to indicate that no cargo exists for the bond number
R-GCX016E-cbl-01914 Return Error - Invalid Status
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Return Error - Invalid Status', assuming that cargo records have been retrieved for a bond number, when the records contain invalid or unprocessable status codes, the desired outcome is that return 'invalid status' error to indicate that the cargo records cannot be processed due to status issues.
💻 Technical Criteria
EXCLUDING Cargo records have been retrieved for a bond number
When The records contain invalid or unprocessable status codes
Then Return 'Invalid Status' error to indicate that the cargo records cannot be processed due to status issues
R-GCX016E-cbl-01915 Format Car ID for Search
Process Rules
📊 Business Logic Narrative
When the process 'Format Car ID for Search' is invoked, and assuming that a cargo record contains equipment initial and equipment number from n7 segment, when the system needs to create a car id for database search, the desired outcome is that the system concatenates equipment initial and equipment number to form the car id search key.
💻 Technical Criteria
Given A cargo record contains equipment initial and equipment number from N7 segment
When The system needs to create a car ID for database search
Then The system concatenates equipment initial and equipment number to form the car ID search key
R-GCX016E-cbl-01919 Retrieve First Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve First Cargo Record' is invoked, and assuming that database lookup has returned one or more matching cargo records, when the system begins processing the found records, the desired outcome is that the system retrieves and loads the first cargo record from the result set.
💻 Technical Criteria
Given Database lookup has returned one or more matching cargo records
When The system begins processing the found records
Then The system retrieves and loads the first cargo record from the result set
R-GCX016E-cbl-01923 Validate Record Status
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Record Status' is invoked, and assuming that a cargo record has been retrieved from the database, when the system evaluates the record for processing eligibility, the desired outcome is that the system validates the record status to ensure it meets processing criteria.
💻 Technical Criteria
Given A cargo record has been retrieved from the database
When The system evaluates the record for processing eligibility
Then The system validates the record status to ensure it meets processing criteria
R-GCX016E-cbl-01924 Record Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Record Valid?' is invoked, and assuming that a cargo record has undergone status validation, when the system evaluates the validation results, the desired outcome is that the system decides whether the record is valid for processing or should be skipped.
💻 Technical Criteria
Given A cargo record has undergone status validation
When The system evaluates the validation results
Then The system decides whether the record is valid for processing or should be skipped
R-GCX016E-cbl-01925 Add to Processing List
Process Rules
📊 Business Logic Narrative
When the process 'Add to Processing List' is invoked, and assuming that a cargo record has passed validation checks, when the system processes valid records, the desired outcome is that the system adds the valid cargo record to the processing list for further operations.
💻 Technical Criteria
Given A cargo record has passed validation checks
When The system processes valid records
Then The system adds the valid cargo record to the processing list for further operations
R-GCX016E-cbl-01926 Skip Invalid Record
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Skip Invalid Record', assuming that a cargo record has failed validation checks, when the system processes invalid records, the desired outcome is that the system skips the invalid cargo record and continues with the next record.
💻 Technical Criteria
EXCLUDING A cargo record has failed validation checks
When The system processes invalid records
Then The system skips the invalid cargo record and continues with the next record
R-GCX016E-cbl-01928 Validate CPRS Traffic Type
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Validate CPRS Traffic Type', assuming that a cargo record is not found in the system and cprs cargo creation is requested, when the system checks the traffic type indicators and cprs-specific identifiers, the desired outcome is that the system should validate that this is legitimate cprs traffic and proceed with creation, or reject invalid traffic types.
💻 Technical Criteria
EXCLUDING A cargo record is not found in the system and CPRS cargo creation is requested
When The system checks the traffic type indicators and CPRS-specific identifiers
Then The system should validate that this is legitimate CPRS traffic and proceed with creation, or reject invalid traffic types
R-GCX016E-cbl-01929 Check Car ID Format
Validation Rules
📊 Business Logic Narrative
When the process 'Check Car ID Format' is invoked, and assuming that cprs traffic type has been validated and car id information is available from n7 segment, when the system processes the car initial and car number from the equipment data, the desired outcome is that the system should validate the car id format meets cprs standards and format it appropriately.
💻 Technical Criteria
Given CPRS traffic type has been validated and car ID information is available from N7 segment
When The system processes the car initial and car number from the equipment data
Then The system should validate the car ID format meets CPRS standards and format it appropriately
R-GCX016E-cbl-01930 Initialize New Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Initialize New Cargo Record' is invoked, and assuming that car id format has been validated for cprs standards, when the system begins creating a new cargo record, the desired outcome is that the system should initialize all cargo record fields to appropriate default values for new cprs cargo.
💻 Technical Criteria
Given Car ID format has been validated for CPRS standards
When The system begins creating a new cargo record
Then The system should initialize all cargo record fields to appropriate default values for new CPRS cargo
R-GCX016E-cbl-01931 Set CPRS-Specific Fields
Definitional Rules
📊 Business Logic Narrative
When the process 'Set CPRS-Specific Fields' is invoked, and assuming that a new cargo record has been initialized for cprs traffic, when the system assigns cprs-specific field values, the desired outcome is that the system should set cargo type indicators, processing flags, and other cprs-specific attributes.
💻 Technical Criteria
Given A new cargo record has been initialized for CPRS traffic
When The system assigns CPRS-specific field values
Then The system should set cargo type indicators, processing flags, and other CPRS-specific attributes
R-GCX016E-cbl-01932 Copy X4 Segment Data
Process Rules
📊 Business Logic Narrative
When the process 'Copy X4 Segment Data' is invoked, and assuming that cprs-specific fields have been set in the new cargo record and x4 segment data is available, when the system copies x4 segment information to the cargo record, the desired outcome is that the system should transfer disposition code, entry number, quantity, and date/time information from x4 segment to cargo record.
💻 Technical Criteria
Given CPRS-specific fields have been set in the new cargo record and X4 segment data is available
When The system copies X4 segment information to the cargo record
Then The system should transfer disposition code, entry number, quantity, and date/time information from X4 segment to cargo record
R-GCX016E-cbl-01933 Copy N7 Equipment Data
Process Rules
📊 Business Logic Narrative
When the process 'Copy N7 Equipment Data' is invoked, and assuming that x4 segment data has been copied to the cargo record and n7 equipment data is available, when the system copies n7 equipment information to the cargo record, the desired outcome is that the system should transfer car initial, car number, and other equipment details from n7 segment to cargo record.
💻 Technical Criteria
Given X4 segment data has been copied to the cargo record and N7 equipment data is available
When The system copies N7 equipment information to the cargo record
Then The system should transfer car initial, car number, and other equipment details from N7 segment to cargo record
R-GCX016E-cbl-01934 Set Default Values for Missing Fields
Definitional Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Default Values for Missing Fields', assuming that x4 and n7 segment data has been copied to the cargo record, when the system identifies fields that do not have values from the source segments, the desired outcome is that the system should assign appropriate default values for missing mandatory fields and leave optional fields blank.
💻 Technical Criteria
EXCLUDING X4 and N7 segment data has been copied to the cargo record
When The system identifies fields that do not have values from the source segments
Then The system should assign appropriate default values for missing mandatory fields and leave optional fields blank
R-GCX016E-cbl-01935 Format Car ID for CPRS Standards
Computation Rules
📊 Business Logic Narrative
When the process 'Format Car ID for CPRS Standards' is invoked, and assuming that default values have been set for missing fields and raw car id components are available, when the system formats the car id for cprs processing, the desired outcome is that the system should combine car initial and car number according to cprs formatting rules and standards.
💻 Technical Criteria
Given Default values have been set for missing fields and raw car ID components are available
When The system formats the car ID for CPRS processing
Then The system should combine car initial and car number according to CPRS formatting rules and standards
R-GCX016E-cbl-01938 Database Insert Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Database Insert Successful?' is invoked, and assuming that a new cargo record has been prepared with status set to 'new', when the system attempts to insert the cargo record into the database, the desired outcome is that the system should verify the database insert operation completed successfully and handle any insertion failures.
💻 Technical Criteria
Given A new cargo record has been prepared with status set to 'New'
When The system attempts to insert the cargo record into the database
Then The system should verify the database insert operation completed successfully and handle any insertion failures
R-GCX016E-cbl-01939 Log CPRS Cargo Creation
Process Rules
📊 Business Logic Narrative
When the process 'Log CPRS Cargo Creation' is invoked, and assuming that the database insert operation was successful, when the system logs the cargo creation event, the desired outcome is that the system should create an audit log entry documenting the creation of the new cprs cargo record with relevant details.
💻 Technical Criteria
Given The database insert operation was successful
When The system logs the cargo creation event
Then The system should create an audit log entry documenting the creation of the new CPRS cargo record with relevant details
R-GCX016E-cbl-01940 Update Cargo Processing Counters
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo Processing Counters' is invoked, and assuming that cprs cargo creation has been logged successfully, when the system updates processing counters, the desired outcome is that the system should increment counters for new cargo records created and total cargos processed.
💻 Technical Criteria
Given CPRS cargo creation has been logged successfully
When The system updates processing counters
Then The system should increment counters for new cargo records created and total cargos processed
R-GCX016E-cbl-01941 Continue with Disposition Processing
Action Rules
📊 Business Logic Narrative
When the process 'Continue with Disposition Processing' is invoked, and assuming that cargo processing counters have been updated after successful cprs cargo creation, when the system continues with cargo processing, the desired outcome is that the system should proceed with disposition code processing for the newly created cprs cargo record.
💻 Technical Criteria
Given Cargo processing counters have been updated after successful CPRS cargo creation
When The system continues with cargo processing
Then The system should proceed with disposition code processing for the newly created CPRS cargo record
R-GCX016E-cbl-01942 Generate Error Message
Process Rules
📊 Business Logic Narrative
When the process 'Generate Error Message' is invoked, and assuming that cprs traffic validation failed or database insert operation failed, when the system encounters an error during cprs cargo creation, the desired outcome is that the system should generate an appropriate error message describing the failure reason and route it to the appropriate destination.
💻 Technical Criteria
Given CPRS traffic validation failed or database insert operation failed
When The system encounters an error during CPRS cargo creation
Then The system should generate an appropriate error message describing the failure reason and route it to the appropriate destination
R-GCX016E-cbl-01943 Skip Cargo Processing
Decision Rules
📊 Business Logic Narrative
When the process 'Skip Cargo Processing' is invoked, and assuming that an error message has been generated due to cprs cargo creation failure, when the system determines next processing steps, the desired outcome is that the system should skip all further processing for this cargo and continue with the next cargo or segment.
💻 Technical Criteria
Given An error message has been generated due to CPRS cargo creation failure
When The system determines next processing steps
Then The system should skip all further processing for this cargo and continue with the next cargo or segment
R-GCX016E-cbl-01944 Initialize New Cargo Record
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Initialize New Cargo Record', assuming that a foreign bill is not found in the existing cargo system, when the system needs to create a new cargo record, the desired outcome is that a new cargo record structure is initialized with default values and prepared for data population.
💻 Technical Criteria
EXCLUDING A foreign bill is not found in the existing cargo system
When The system needs to create a new cargo record
Then A new cargo record structure is initialized with default values and prepared for data population
R-GCX016E-cbl-01945 Set Up Cargo Record with X4 Segment Data
Process Rules
📊 Business Logic Narrative
When the process 'Set Up Cargo Record with X4 Segment Data' is invoked, and assuming that an initialized cargo record and x4 segment data containing disposition codes and cargo details, when the system processes x4 segment information for foreign bill cargo creation, the desired outcome is that the cargo record is populated with disposition code, entry number, quantity, and other x4 segment data.
💻 Technical Criteria
Given An initialized cargo record and X4 segment data containing disposition codes and cargo details
When The system processes X4 segment information for foreign bill cargo creation
Then The cargo record is populated with disposition code, entry number, quantity, and other X4 segment data
R-GCX016E-cbl-01946 Set Up Cargo Record with N7 Segment Data
Process Rules
📊 Business Logic Narrative
When the process 'Set Up Cargo Record with N7 Segment Data' is invoked, and assuming that a cargo record with x4 data populated and n7 segment data containing equipment information, when the system processes n7 segment information for equipment details, the desired outcome is that the cargo record is updated with car id, equipment initial, equipment number, and other n7 equipment data.
💻 Technical Criteria
Given A cargo record with X4 data populated and N7 segment data containing equipment information
When The system processes N7 segment information for equipment details
Then The cargo record is updated with car ID, equipment initial, equipment number, and other N7 equipment data
R-GCX016E-cbl-01947 Build Foreign Manifest Information from M10 Segments
Process Rules
📊 Business Logic Narrative
When the process 'Build Foreign Manifest Information from M10 Segments' is invoked, and assuming that m10 segments containing manifest header information for foreign bills, when the system processes m10 segments to build foreign manifest data, the desired outcome is that manifest information including scac code, transport type, country code, and vessel details are extracted and prepared for cargo record.
💻 Technical Criteria
Given M10 segments containing manifest header information for foreign bills
When The system processes M10 segments to build foreign manifest data
Then Manifest information including SCAC code, transport type, country code, and vessel details are extracted and prepared for cargo record
R-GCX016E-cbl-01948 Extract SCAC Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract SCAC Code' is invoked, and assuming that m10 manifest segments containing carrier information, when the system processes manifest data to identify the carrier, the desired outcome is that the scac code is extracted and assigned to the cargo record for carrier identification.
💻 Technical Criteria
Given M10 manifest segments containing carrier information
When The system processes manifest data to identify the carrier
Then The SCAC code is extracted and assigned to the cargo record for carrier identification
R-GCX016E-cbl-01949 Extract Transport Type
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Transport Type' is invoked, and assuming that m10 manifest segments containing transportation mode information, when the system processes manifest data to classify transport method, the desired outcome is that the transport type is identified and recorded in the cargo record for proper routing and handling.
💻 Technical Criteria
Given M10 manifest segments containing transportation mode information
When The system processes manifest data to classify transport method
Then The transport type is identified and recorded in the cargo record for proper routing and handling
R-GCX016E-cbl-01950 Extract Country Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Country Code' is invoked, and assuming that m10 manifest segments containing country information, when the system processes manifest data to identify country details, the desired outcome is that the appropriate country code is extracted and assigned to the cargo record for customs and regulatory purposes.
💻 Technical Criteria
Given M10 manifest segments containing country information
When The system processes manifest data to identify country details
Then The appropriate country code is extracted and assigned to the cargo record for customs and regulatory purposes
R-GCX016E-cbl-01951 Extract Vessel Details
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Vessel Details' is invoked, and assuming that m10 manifest segments containing vessel or conveyance information, when the system processes manifest data to capture vessel details, the desired outcome is that vessel name, voyage number, and other conveyance details are extracted and recorded in the cargo record.
💻 Technical Criteria
Given M10 manifest segments containing vessel or conveyance information
When The system processes manifest data to capture vessel details
Then Vessel name, voyage number, and other conveyance details are extracted and recorded in the cargo record
R-GCX016E-cbl-01952 Format Car ID for Database
Validation Rules
📊 Business Logic Narrative
When the process 'Format Car ID for Database' is invoked, and assuming that raw car id information from n7 equipment segments, when the system prepares car id for database insertion, the desired outcome is that the car id is formatted according to database requirements with proper padding, case conversion, and structure validation.
💻 Technical Criteria
Given Raw car ID information from N7 equipment segments
When The system prepares car ID for database insertion
Then The car ID is formatted according to database requirements with proper padding, case conversion, and structure validation
R-GCX016E-cbl-01953 Insert New Cargo Record into Database
Action Rules
📊 Business Logic Narrative
When the process 'Insert New Cargo Record into Database' is invoked, and assuming that a complete cargo record populated with all required foreign bill information, when the system performs database insertion for the new cargo record, the desired outcome is that the cargo record is successfully inserted into gcsusrt database with all populated fields and proper indexing.
💻 Technical Criteria
Given A complete cargo record populated with all required foreign bill information
When The system performs database insertion for the new cargo record
Then The cargo record is successfully inserted into GCSUSRT database with all populated fields and proper indexing
R-GCX016E-cbl-01954 Log Foreign Cargo Creation Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Foreign Cargo Creation Action' is invoked, and assuming that a successfully created foreign cargo record in the database, when the system completes foreign cargo creation process, the desired outcome is that a log entry is created documenting the foreign cargo creation with timestamp, cargo details, and creation context for audit trail.
💻 Technical Criteria
Given A successfully created foreign cargo record in the database
When The system completes foreign cargo creation process
Then A log entry is created documenting the foreign cargo creation with timestamp, cargo details, and creation context for audit trail
R-GCX016E-cbl-01955 Search Cargo by Car ID
Action Rules
📊 Business Logic Narrative
When the process 'Search Cargo by Car ID' is invoked, and assuming that a car id is provided for cargo lookup, when the system performs initial cargo search using the car id, the desired outcome is that the system queries the cargo database to find matching cargo records.
💻 Technical Criteria
Given A car ID is provided for cargo lookup
When The system performs initial cargo search using the car ID
Then The system queries the cargo database to find matching cargo records
R-GCX016E-cbl-01956 Cargo Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Cargo Found?' is invoked, and assuming that a cargo search has been performed using car id, when the system evaluates the search results, the desired outcome is that the system determines if a cargo record was found or not found.
💻 Technical Criteria
Given A cargo search has been performed using car ID
When The system evaluates the search results
Then The system determines if a cargo record was found or not found
R-GCX016E-cbl-01957 Check SCAC Code
Validation Rules
📊 Business Logic Narrative
When the process 'Check SCAC Code' is invoked, and assuming that a cargo record has been found using car id search, when the system checks the scac code in the cargo record, the desired outcome is that the system retrieves and evaluates the scac code for further processing.
💻 Technical Criteria
Given A cargo record has been found using car ID search
When The system checks the SCAC code in the cargo record
Then The system retrieves and evaluates the SCAC code for further processing
R-GCX016E-cbl-01961 Cargo Found with New Key?
Validation Rules
📊 Business Logic Narrative
When the process 'Cargo Found with New Key?' is invoked, and assuming that a secondary cargo search has been performed with renumbered key, when the system evaluates the secondary search results, the desired outcome is that the system determines if cargo was successfully found with the new key.
💻 Technical Criteria
Given A secondary cargo search has been performed with renumbered key
When The system evaluates the secondary search results
Then The system determines if cargo was successfully found with the new key
R-GCX016E-cbl-01962 Handle SCAC Unknown Scenario
Process Rules
📊 Business Logic Narrative
When the process 'Handle SCAC Unknown Scenario' is invoked, and assuming that cargo has been found using renumbered key after scac unknown determination, when the system handles the scac unknown scenario, the desired outcome is that the system applies special processing rules for unknown scac situations.
💻 Technical Criteria
Given Cargo has been found using renumbered key after SCAC unknown determination
When The system handles the SCAC unknown scenario
Then The system applies special processing rules for unknown SCAC situations
R-GCX016E-cbl-01964 Return Found Cargo Record
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Return Found Cargo Record', assuming that a cargo record has been found and scac is not unknown, when the system processes the found cargo, the desired outcome is that the system returns the cargo record for further business processing.
💻 Technical Criteria
EXCLUDING A cargo record has been found and SCAC is not unknown
When The system processes the found cargo
Then The system returns the cargo record for further business processing
R-GCX016E-cbl-01965 Continue with Found Cargo
Process Rules
📊 Business Logic Narrative
When the process 'Continue with Found Cargo' is invoked, and assuming that a valid cargo record has been found through either initial search or scac unknown processing, when the system continues with cargo processing, the desired outcome is that the system proceeds with standard cargo business logic using the found record.
💻 Technical Criteria
Given A valid cargo record has been found through either initial search or SCAC unknown processing
When The system continues with cargo processing
Then The system proceeds with standard cargo business logic using the found record
R-GCX016E-cbl-01966 Generate Cargo Not Found Error
Action Rules
📊 Business Logic Narrative
When the process 'Generate Cargo Not Found Error' is invoked, and assuming that cargo search has failed in both initial search and secondary search with renumbered key, when the system cannot locate any matching cargo record, the desired outcome is that the system generates a cargo not found error for business exception handling.
💻 Technical Criteria
Given Cargo search has failed in both initial search and secondary search with renumbered key
When The system cannot locate any matching cargo record
Then The system generates a cargo not found error for business exception handling
R-GCX016E-cbl-01967 Initialize Status Segment Variables
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Status Segment Variables' is invoked, and assuming that a cargo status segment retrieval process is starting, when the system begins status segment processing, the desired outcome is that all status segment variables, arrays, and counters are initialized to their default values.
💻 Technical Criteria
Given A cargo status segment retrieval process is starting
When The system begins status segment processing
Then All status segment variables, arrays, and counters are initialized to their default values
R-GCX016E-cbl-01970 S09 Segments Found?
Decision Rules
📊 Business Logic Narrative
When the process 'S09 Segments Found?' is invoked, and assuming that gccusio2 has completed the status segment retrieval attempt, when the system evaluates the retrieval results, the desired outcome is that if segments are found, proceed to process them; if no segments found or database error occurred, initialize empty status arrays.
💻 Technical Criteria
Given GCCUSIO2 has completed the status segment retrieval attempt
When The system evaluates the retrieval results
Then If segments are found, proceed to process them; if no segments found or database error occurred, initialize empty status arrays
R-GCX016E-cbl-01971 Initialize Empty Status Arrays
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Empty Status Arrays' is invoked, and assuming that no s09 status segments were found or a database error occurred, when the system needs to continue processing without existing status data, the desired outcome is that empty status arrays are initialized to allow new status processing.
💻 Technical Criteria
Given No S09 status segments were found or a database error occurred
When The system needs to continue processing without existing status data
Then Empty status arrays are initialized to allow new status processing
R-GCX016E-cbl-01977 Initialize Status Array Counter
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Status Array Counter' is invoked, and assuming that a cargo requires status array population from database segments, when the status array population process begins, the desired outcome is that the status array counter is initialized to zero to track processed segments.
💻 Technical Criteria
Given A cargo requires status array population from database segments
When The status array population process begins
Then The status array counter is initialized to zero to track processed segments
R-GCX016E-cbl-01978 Retrieve S09 Status Segments from Database
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve S09 Status Segments from Database' is invoked, and assuming that a cargo identifier exists in the system, when status array population is requested for the cargo, the desired outcome is that all s09 status segments are retrieved from the gcsuss09 database table for that cargo.
💻 Technical Criteria
Given A cargo identifier exists in the system
When Status array population is requested for the cargo
Then All S09 status segments are retrieved from the GCSUSS09 database table for that cargo
R-GCX016E-cbl-01986 More Status Segments?
Decision Rules
📊 Business Logic Narrative
When the process 'More Status Segments?' is invoked, and assuming that a status segment has been processed and stored, when the system checks for remaining segments, the desired outcome is that if more status segments exist for the cargo, continue processing the next segment, otherwise proceed to completion.
💻 Technical Criteria
Given A status segment has been processed and stored
When The system checks for remaining segments
Then If more status segments exist for the cargo, continue processing the next segment, otherwise proceed to completion
R-GCX016E-cbl-01988 Status Array Updated?
Validation Rules
📊 Business Logic Narrative
When the process 'Status Array Updated?' is invoked, and assuming that a cargo status processing operation has been completed, when the system checks if the status array has been modified, the desired outcome is that if the status array is updated, proceed to convert to database format, otherwise complete the process without database operations.
💻 Technical Criteria
Given A cargo status processing operation has been completed
When The system checks if the status array has been modified
Then If the status array is updated, proceed to convert to database format, otherwise complete the process without database operations
R-GCX016E-cbl-01989 Convert Status Array to Database Format
Process Rules
📊 Business Logic Narrative
When the process 'Convert Status Array to Database Format' is invoked, and assuming that the status array has been updated with new cargo status information, when the system needs to prepare data for database storage, the desired outcome is that convert the status array elements to the proper database segment format maintaining all status codes, quantities, and sequence information.
💻 Technical Criteria
Given The status array has been updated with new cargo status information
When The system needs to prepare data for database storage
Then Convert the status array elements to the proper database segment format maintaining all status codes, quantities, and sequence information
R-GCX016E-cbl-01990 Cargo Type Check
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Type Check' is invoked, and assuming that a cargo record is being processed for status segment replacement, when the system evaluates the cargo type, the desired outcome is that if the cargo is non-cprs, proceed to update car id information, if cprs, skip car id updates and proceed directly to database segment preparation.
💻 Technical Criteria
Given A cargo record is being processed for status segment replacement
When The system evaluates the cargo type
Then If the cargo is Non-CPRS, proceed to update car ID information, if CPRS, skip car ID updates and proceed directly to database segment preparation
R-GCX016E-cbl-01991 Update Car ID for Non-CPRS Cargo
Process Rules
📊 Business Logic Narrative
When the process 'Update Car ID for Non-CPRS Cargo' is invoked, and assuming that a non-cprs cargo is being processed and car id information is available from n7 equipment segments, when the system updates cargo information before database storage, the desired outcome is that update the cargo record with the current car id information from the equipment segment data.
💻 Technical Criteria
Given A non-CPRS cargo is being processed and car ID information is available from N7 equipment segments
When The system updates cargo information before database storage
Then Update the cargo record with the current car ID information from the equipment segment data
R-GCX016E-cbl-01995 Log Successful Replacement
Process Rules
📊 Business Logic Narrative
When the process 'Log Successful Replacement' is invoked, and assuming that the database replacement operation completed successfully, when the system needs to record the successful operation, the desired outcome is that log the successful replacement of status segment with cargo identification and timestamp information.
💻 Technical Criteria
Given The database replacement operation completed successfully
When The system needs to record the successful operation
Then Log the successful replacement of status segment with cargo identification and timestamp information
R-GCX016E-cbl-01997 Update Status Tracking
Process Rules
📊 Business Logic Narrative
When the process 'Update Status Tracking' is invoked, and assuming that a database replacement operation has been completed (successfully or with error), when the system updates internal tracking information, the desired outcome is that update status tracking records to reflect the current state of the cargo status segment replacement operation.
💻 Technical Criteria
Given A database replacement operation has been completed (successfully or with error)
When The system updates internal tracking information
Then Update status tracking records to reflect the current state of the cargo status segment replacement operation
R-GCX016E-cbl-02016 Update Cargo Record with Segment Count
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo Record with Segment Count' is invoked, and assuming that database segments have been written for a cargo's status information, when the conversion process is complete, the desired outcome is that the cargo record is updated with the total count of database segments created.
💻 Technical Criteria
Given Database segments have been written for a cargo's status information
When The conversion process is complete
Then The cargo record is updated with the total count of database segments created
R-GCX016E-cbl-02017 Complete Conversion Process
Process Rules
📊 Business Logic Narrative
When the process 'Complete Conversion Process' is invoked, and assuming that all status array entries have been converted and written to database segments, when the cargo record has been updated with segment information, the desired outcome is that the conversion process is marked as complete and control returns to calling process.
💻 Technical Criteria
Given All status array entries have been converted and written to database segments
When The cargo record has been updated with segment information
Then The conversion process is marked as complete and control returns to calling process
R-GCX016E-cbl-02024 Extract Hold/Release Indicator
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Hold/Release Indicator' is invoked, and assuming that a valid disposition code with processing attributes, when the system needs to determine the hold or release nature of the code, the desired outcome is that the hold/release indicator is extracted to determine the appropriate cargo status action.
💻 Technical Criteria
Given A valid disposition code with processing attributes
When The system needs to determine the hold or release nature of the code
Then The hold/release indicator is extracted to determine the appropriate cargo status action
R-GCX016E-cbl-02025 Extract Status Information Flag
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Status Information Flag' is invoked, and assuming that a valid disposition code with complete attributes, when the system needs to determine if the code is informational, the desired outcome is that the status information flag is extracted to determine if the code affects cargo status or is informational only.
💻 Technical Criteria
Given A valid disposition code with complete attributes
When The system needs to determine if the code is informational
Then The status information flag is extracted to determine if the code affects cargo status or is informational only
R-GCX016E-cbl-02029 Continue Processing with Retrieved Rules
Process Rules
📊 Business Logic Narrative
When the process 'Continue Processing with Retrieved Rules' is invoked, and assuming that a disposition code has been validated and processing rules retrieved, when all validation checks pass successfully, the desired outcome is that the system continues with cargo processing using the retrieved disposition code rules and attributes.
💻 Technical Criteria
Given A disposition code has been validated and processing rules retrieved
When All validation checks pass successfully
Then The system continues with cargo processing using the retrieved disposition code rules and attributes
R-GCX016E-cbl-02030 Skip Processing Due to Invalid Code
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Skip Processing Due to Invalid Code', assuming that a disposition code has failed validation, when the code is determined to be invalid or unauthorized, the desired outcome is that the system skips further processing of the cargo to prevent incorrect status updates.
💻 Technical Criteria
EXCLUDING A disposition code has failed validation
When The code is determined to be invalid or unauthorized
Then The system skips further processing of the cargo to prevent incorrect status updates
R-GCX016E-cbl-02031 Search Existing S09A Status Arrays
Process Rules
📊 Business Logic Narrative
When the process 'Search Existing S09A Status Arrays' is invoked, and assuming that a new disposition code needs to be processed for a cargo, when the system searches through all existing s09a status array entries, the desired outcome is that the system identifies whether the disposition code already exists in the status arrays.
💻 Technical Criteria
Given A new disposition code needs to be processed for a cargo
When The system searches through all existing S09A status array entries
Then The system identifies whether the disposition code already exists in the status arrays
R-GCX016E-cbl-02043 Search for Conflicting Codes?
Process Rules
📊 Business Logic Narrative
When the process 'Search for Conflicting Codes?' is invoked, and assuming that a new disposition code is being processed for a cargo and current status arrays exist with existing disposition codes, when the system needs to check for conflicting codes before adding the new disposition code, the desired outcome is that the system searches through all existing disposition codes in the status arrays to identify potential conflicts.
💻 Technical Criteria
Given A new disposition code is being processed for a cargo AND current status arrays exist with existing disposition codes
When The system needs to check for conflicting codes before adding the new disposition code
Then The system searches through all existing disposition codes in the status arrays to identify potential conflicts
R-GCX016E-cbl-02070 Update Cargo Status
Computation Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status' is invoked, and assuming that a disposition code has been removed and confirmation generated, when the system updates the cargo status, the desired outcome is that the cargo status must be recalculated based on the remaining disposition codes in the status array.
💻 Technical Criteria
Given A disposition code has been removed and confirmation generated
When The system updates the cargo status
Then The cargo status must be recalculated based on the remaining disposition codes in the status array
R-GCX016E-cbl-02071 Send Status Change Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send Status Change Notification' is invoked, and assuming that the cargo status has been updated after disposition code removal, when the system sends status change notifications, the desired outcome is that notifications must be sent to all relevant parties including brokers, freight forwarders, and customs officials.
💻 Technical Criteria
Given The cargo status has been updated after disposition code removal
When The system sends status change notifications
Then Notifications must be sent to all relevant parties including brokers, freight forwarders, and customs officials
R-GCX016E-cbl-02075 Check Current Status Array
Validation Rules
📊 Business Logic Narrative
When the process 'Check Current Status Array' is invoked, and assuming that a release request has been received for a cargo, when the system needs to process the release request, the desired outcome is that the system must retrieve and examine the current status array from cargo status segments to identify existing disposition codes.
💻 Technical Criteria
Given A release request has been received for a cargo
When The system needs to process the release request
Then The system must retrieve and examine the current status array from cargo status segments to identify existing disposition codes
R-GCX016E-cbl-02076 Search for Existing Release Codes
Decision Rules
📊 Business Logic Narrative
When the process 'Search for Existing Release Codes' is invoked, and assuming that the current status array has been retrieved for a cargo, when processing a new release request, the desired outcome is that the system must search through all disposition codes in the status array to identify existing release codes.
💻 Technical Criteria
Given The current status array has been retrieved for a cargo
When Processing a new release request
Then The system must search through all disposition codes in the status array to identify existing release codes
R-GCX016E-cbl-02083 Calculate Release Quantity Impact
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Release Quantity Impact' is invoked, and assuming that a release disposition code has been added to the status array, when the release quantity needs to be determined, the desired outcome is that the system must calculate the quantity impact of the release code on the total cargo release amount.
💻 Technical Criteria
Given A release disposition code has been added to the status array
When The release quantity needs to be determined
Then The system must calculate the quantity impact of the release code on the total cargo release amount
R-GCX016E-cbl-02084 Set Release Status Flags
Process Rules
📊 Business Logic Narrative
When the process 'Set Release Status Flags' is invoked, and assuming that release quantity impact has been calculated, when the cargo status needs to be updated, the desired outcome is that the system must set appropriate release status flags to reflect the current release state of the cargo.
💻 Technical Criteria
Given Release quantity impact has been calculated
When The cargo status needs to be updated
Then The system must set appropriate release status flags to reflect the current release state of the cargo
R-GCX016E-cbl-02088 Reject Release Request
Decision Rules
📊 Business Logic Narrative
When the process 'Reject Release Request' is invoked, and assuming that an error message has been generated for invalid release code, when the release request cannot be processed due to validation failure, the desired outcome is that the system must reject the release request and maintain the original cargo status without any changes.
💻 Technical Criteria
Given An error message has been generated for invalid release code
When The release request cannot be processed due to validation failure
Then The system must reject the release request and maintain the original cargo status without any changes
R-GCX016E-cbl-02089 Validate Manual Release Request
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Manual Release Request' is invoked, and assuming that a manual release request is received for a cargo, when the system validates the request parameters including disposition code format, cargo identification, and request authorization, the desired outcome is that the system determines if the request is valid and can proceed with manual release processing.
💻 Technical Criteria
Given A manual release request is received for a cargo
When The system validates the request parameters including disposition code format, cargo identification, and request authorization
Then The system determines if the request is valid and can proceed with manual release processing
R-GCX016E-cbl-02090 Conflicting Codes Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Conflicting Codes Found?' is invoked, and assuming that a cargo has an existing status array with disposition codes, when a manual release request is processed and the system searches for conflicting hold or restriction codes, the desired outcome is that the system identifies any existing codes that must be removed before applying the manual release.
💻 Technical Criteria
Given A cargo has an existing status array with disposition codes
When A manual release request is processed and the system searches for conflicting hold or restriction codes
Then The system identifies any existing codes that must be removed before applying the manual release
R-GCX016E-cbl-02091 Remove Existing Hold/Restriction Codes
Process Rules
📊 Business Logic Narrative
When the process 'Remove Existing Hold/Restriction Codes' is invoked, and assuming that conflicting hold or restriction codes exist in the cargo status array, when a manual release is being processed, the desired outcome is that the system removes all conflicting disposition codes from the status array to clear the path for manual release.
💻 Technical Criteria
Given Conflicting hold or restriction codes exist in the cargo status array
When A manual release is being processed
Then The system removes all conflicting disposition codes from the status array to clear the path for manual release
R-GCX016E-cbl-02094 Log Manual Release Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Manual Release Action' is invoked, and assuming that a manual release has been successfully applied to a cargo, when the system completes the manual release processing, the desired outcome is that the system logs the manual release action with timestamp, user information, and cargo details for audit purposes.
💻 Technical Criteria
Given A manual release has been successfully applied to a cargo
When The system completes the manual release processing
Then The system logs the manual release action with timestamp, user information, and cargo details for audit purposes
R-GCX016E-cbl-02095 Cargo Fully Released?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Fully Released?' is invoked, and assuming that the cargo status array has been updated with manual release disposition code, when the system evaluates the final status of the cargo, the desired outcome is that the system determines if the cargo is fully released by checking for any remaining hold or restriction codes and validating release quantities.
💻 Technical Criteria
Given The cargo status array has been updated with manual release disposition code
When The system evaluates the final status of the cargo
Then The system determines if the cargo is fully released by checking for any remaining hold or restriction codes and validating release quantities
R-GCX016E-cbl-02096 Set Cargo Release Status
Process Rules
📊 Business Logic Narrative
When the process 'Set Cargo Release Status' is invoked, and assuming that the cargo status evaluation determines the cargo is fully released, when manual release processing is completed, the desired outcome is that the system sets the cargo status to 'relsd' (released) and updates all related status flags.
💻 Technical Criteria
Given The cargo status evaluation determines the cargo is fully released
When Manual release processing is completed
Then The system sets the cargo status to 'RELSD' (Released) and updates all related status flags
R-GCX016E-cbl-02097 Calculate Release Quantities
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Release Quantities' is invoked, and assuming that a cargo has been set to released status through manual release, when the system processes the release quantities, the desired outcome is that the system calculates the total released quantity based on the manual release disposition and updates the cargo record with the new released amount.
💻 Technical Criteria
Given A cargo has been set to released status through manual release
When The system processes the release quantities
Then The system calculates the total released quantity based on the manual release disposition and updates the cargo record with the new released amount
R-GCX016E-cbl-02098 Generate Release Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Release Notification' is invoked, and assuming that a cargo has been successfully manually released with updated quantities, when the system completes the release processing, the desired outcome is that the system generates and sends release notifications to brokers, freight forwarders, and other stakeholders via merlin messaging system.
💻 Technical Criteria
Given A cargo has been successfully manually released with updated quantities
When The system completes the release processing
Then The system generates and sends release notifications to brokers, freight forwarders, and other stakeholders via Merlin messaging system
R-GCX016E-cbl-02099 Update Cargo Status Flags
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status Flags' is invoked, and assuming that manual release processing has been completed for a cargo, when the system finalizes the cargo status changes, the desired outcome is that the system updates all cargo status flags including hold indicators, release flags, and processing status markers to reflect the current state.
💻 Technical Criteria
Given Manual release processing has been completed for a cargo
When The system finalizes the cargo status changes
Then The system updates all cargo status flags including hold indicators, release flags, and processing status markers to reflect the current state
R-GCX016E-cbl-02100 Create Audit Trail Entry
Process Rules
📊 Business Logic Narrative
When the process 'Create Audit Trail Entry' is invoked, and assuming that manual release processing has been successfully completed, when the system finalizes all cargo updates, the desired outcome is that the system creates detailed audit trail entries including before/after status, user identification, timestamp, and transaction details for compliance and tracking purposes.
💻 Technical Criteria
Given Manual release processing has been successfully completed
When The system finalizes all cargo updates
Then The system creates detailed audit trail entries including before/after status, user identification, timestamp, and transaction details for compliance and tracking purposes
R-GCX016E-cbl-02105 Add New Auto Release Code to Status Array
Process Rules
📊 Business Logic Narrative
When the process 'Add New Auto Release Code to Status Array' is invoked, and assuming that any existing duplicate auto release codes have been removed, when the system processes a valid auto release request, the desired outcome is that the system adds the new auto release code to the cargo's status array with appropriate sequence and occurrence data.
💻 Technical Criteria
Given Any existing duplicate auto release codes have been removed
When The system processes a valid auto release request
Then The system adds the new auto release code to the cargo's status array with appropriate sequence and occurrence data
R-GCX016E-cbl-02106 Cargo Currently Held?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Currently Held?' is invoked, and assuming that an auto release code has been added to the status array, when the system evaluates the current cargo status including all active holds, the desired outcome is that the system determines if the cargo is currently held and requires release processing or if no release action is needed.
💻 Technical Criteria
Given An auto release code has been added to the status array
When The system evaluates the current cargo status including all active holds
Then The system determines if the cargo is currently held and requires release processing or if no release action is needed
R-GCX016E-cbl-02107 Calculate Release Impact on Quantities
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Release Impact on Quantities' is invoked, and assuming that cargo is currently held and eligible for auto release, when the system calculates the impact on release quantities based on current held amounts and requested release quantities, the desired outcome is that the system determines the quantity impact and whether full or partial release is possible.
💻 Technical Criteria
Given Cargo is currently held and eligible for auto release
When The system calculates the impact on release quantities based on current held amounts and requested release quantities
Then The system determines the quantity impact and whether full or partial release is possible
R-GCX016E-cbl-02108 Full Release Possible?
Decision Rules
📊 Business Logic Narrative
When the process 'Full Release Possible?' is invoked, and assuming that release quantity impact has been calculated, when the system evaluates if all cargo quantities can be fully released without restrictions, the desired outcome is that the system determines if full release is feasible or if partial release processing is required.
💻 Technical Criteria
Given Release quantity impact has been calculated
When The system evaluates if all cargo quantities can be fully released without restrictions
Then The system determines if full release is feasible or if partial release processing is required
R-GCX016E-cbl-02109 Set Cargo Status to Released
Process Rules
📊 Business Logic Narrative
When the process 'Set Cargo Status to Released' is invoked, and assuming that full release is determined to be possible, when the system processes the auto release request, the desired outcome is that the system sets the cargo status to released and updates all related status indicators.
💻 Technical Criteria
Given Full release is determined to be possible
When The system processes the auto release request
Then The system sets the cargo status to released and updates all related status indicators
R-GCX016E-cbl-02110 Update Release Quantities
Process Rules
📊 Business Logic Narrative
When the process 'Update Release Quantities' is invoked, and assuming that auto release processing has determined the release impact, when the system updates cargo quantities for either full or partial release, the desired outcome is that the system updates released quantities, remaining held quantities, and total quantity balances.
💻 Technical Criteria
Given Auto release processing has determined the release impact
When The system updates cargo quantities for either full or partial release
Then The system updates released quantities, remaining held quantities, and total quantity balances
R-GCX016E-cbl-02112 Log Auto Release Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Auto Release Action' is invoked, and assuming that auto release notifications have been generated, when the system logs the auto release action, the desired outcome is that the system creates audit records with cargo details, release quantities, and timestamp information.
💻 Technical Criteria
Given Auto release notifications have been generated
When The system logs the auto release action
Then The system creates audit records with cargo details, release quantities, and timestamp information
R-GCX016E-cbl-02113 Update Status Array in Database
Process Rules
📊 Business Logic Narrative
When the process 'Update Status Array in Database' is invoked, and assuming that auto release action has been logged, when the system updates the database with the modified status array, the desired outcome is that the system replaces the cargo's s09 status segments with the updated status array information.
💻 Technical Criteria
Given Auto release action has been logged
When The system updates the database with the modified status array
Then The system replaces the cargo's S09 status segments with the updated status array information
R-GCX016E-cbl-02114 Trigger GCCIIS Status Update
Action Rules
📊 Business Logic Narrative
When the process 'Trigger GCCIIS Status Update' is invoked, and assuming that status array has been updated in the database, when the system triggers gcciis integration for status synchronization, the desired outcome is that the system calls gcciis with appropriate cargo status information for external system updates.
💻 Technical Criteria
Given Status array has been updated in the database
When The system triggers GCCIIS integration for status synchronization
Then The system calls GCCIIS with appropriate cargo status information for external system updates
R-GCX016E-cbl-02116 Skip Auto Release Processing
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Skip Auto Release Processing', assuming that auto release code has been added to status array, when the system determines cargo is not currently held, the desired outcome is that the system skips release quantity processing and proceeds to completion without release actions.
💻 Technical Criteria
EXCLUDING Auto release code has been added to status array
When The system determines cargo is not currently held
Then The system skips release quantity processing and proceeds to completion without release actions
R-GCX016E-cbl-02128 Check for Conflicting Codes?
Decision Rules
📊 Business Logic Narrative
When the process 'Check for Conflicting Codes?' is invoked, and assuming that a new disposition code is being processed for a cargo and the cargo has an existing status array with disposition codes, when the system evaluates the new disposition code against existing codes, the desired outcome is that the system identifies if there are any conflicting or counterpart codes that need to be addressed.
💻 Technical Criteria
Given A new disposition code is being processed for a cargo AND the cargo has an existing status array with disposition codes
When The system evaluates the new disposition code against existing codes
Then The system identifies if there are any conflicting or counterpart codes that need to be addressed
R-GCX016E-cbl-02129 Hold vs Release Conflict?
Decision Rules
📊 Business Logic Narrative
When the process 'Hold vs Release Conflict?' is invoked, and assuming that a cargo has existing hold disposition codes in its status array and a new release disposition code is being processed, when the system checks for hold vs release conflicts, the desired outcome is that the system identifies the conflicting hold codes that should be removed when the release code is applied.
💻 Technical Criteria
Given A cargo has existing hold disposition codes in its status array AND a new release disposition code is being processed
When The system checks for hold vs release conflicts
Then The system identifies the conflicting hold codes that should be removed when the release code is applied
R-GCX016E-cbl-02130 Proceed vs Hold Conflict?
Decision Rules
📊 Business Logic Narrative
When the process 'Proceed vs Hold Conflict?' is invoked, and assuming that a cargo has existing proceed disposition codes in its status array and a new hold disposition code is being processed or a cargo has existing hold codes and a new proceed code is being processed, when the system checks for proceed vs hold conflicts, the desired outcome is that the system identifies the conflicting codes that should be removed based on the business precedence rules.
💻 Technical Criteria
Given A cargo has existing proceed disposition codes in its status array AND a new hold disposition code is being processed OR a cargo has existing hold codes AND a new proceed code is being processed
When The system checks for proceed vs hold conflicts
Then The system identifies the conflicting codes that should be removed based on the business precedence rules
R-GCX016E-cbl-02131 Seizure vs Release Conflict?
Decision Rules
📊 Business Logic Narrative
When the process 'Seizure vs Release Conflict?' is invoked, and assuming that a cargo has existing seizure disposition codes in its status array and a new release disposition code is being processed, when the system checks for seizure vs release conflicts, the desired outcome is that the system identifies the conflicting seizure codes that should be removed when the release code is applied.
💻 Technical Criteria
Given A cargo has existing seizure disposition codes in its status array AND a new release disposition code is being processed
When The system checks for seizure vs release conflicts
Then The system identifies the conflicting seizure codes that should be removed when the release code is applied
R-GCX016E-cbl-02132 Arrival vs Cancel Conflict?
Decision Rules
📊 Business Logic Narrative
When the process 'Arrival vs Cancel Conflict?' is invoked, and assuming that a cargo has existing arrival disposition codes in its status array and a new cancellation disposition code is being processed or a cargo has existing cancellation codes and a new arrival code is being processed, when the system checks for arrival vs cancel conflicts, the desired outcome is that the system identifies the conflicting codes that should be removed based on the most recent action.
💻 Technical Criteria
Given A cargo has existing arrival disposition codes in its status array AND a new cancellation disposition code is being processed OR a cargo has existing cancellation codes AND a new arrival code is being processed
When The system checks for arrival vs cancel conflicts
Then The system identifies the conflicting codes that should be removed based on the most recent action
R-GCX016E-cbl-02133 Code Should Be Removed?
Decision Rules
📊 Business Logic Narrative
When the process 'Code Should Be Removed?' is invoked, and assuming that a conflicting disposition code has been identified in the cargo status array and business rules define the precedence between the codes, when the system applies business rules to determine code precedence, the desired outcome is that the system decides whether the existing conflicting code should be removed to allow the new code to be processed.
💻 Technical Criteria
Given A conflicting disposition code has been identified in the cargo status array AND business rules define the precedence between the codes
When The system applies business rules to determine code precedence
Then The system decides whether the existing conflicting code should be removed to allow the new code to be processed
R-GCX016E-cbl-02134 Mark Counterpart Code for Removal
Action Rules
📊 Business Logic Narrative
When the process 'Mark Counterpart Code for Removal' is invoked, and assuming that a conflicting disposition code has been identified for removal and the code exists in the cargo status array, when the system processes the removal decision, the desired outcome is that the system marks the conflicting code for removal while preserving other status array elements.
💻 Technical Criteria
Given A conflicting disposition code has been identified for removal AND the code exists in the cargo status array
When The system processes the removal decision
Then The system marks the conflicting code for removal while preserving other status array elements
R-GCX016E-cbl-02135 Remove Conflicting Code from Array
Action Rules
📊 Business Logic Narrative
When the process 'Remove Conflicting Code from Array' is invoked, and assuming that disposition codes have been marked for removal from the cargo status array, when the system executes the removal process, the desired outcome is that the system removes the marked codes from the status array and maintains the integrity of remaining array elements.
💻 Technical Criteria
Given Disposition codes have been marked for removal from the cargo status array
When The system executes the removal process
Then The system removes the marked codes from the status array AND maintains the integrity of remaining array elements
R-GCX016E-cbl-02136 Reorganize Status Array
Process Rules
📊 Business Logic Narrative
When the process 'Reorganize Status Array' is invoked, and assuming that disposition codes have been removed from the cargo status array creating gaps in the array structure, when the system reorganizes the array, the desired outcome is that the system compacts the array by moving remaining elements to eliminate gaps and preserves the logical order of disposition codes.
💻 Technical Criteria
Given Disposition codes have been removed from the cargo status array creating gaps in the array structure
When The system reorganizes the array
Then The system compacts the array by moving remaining elements to eliminate gaps AND preserves the logical order of disposition codes
R-GCX016E-cbl-02139 Log Removal Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Removal Action' is invoked, and assuming that a conflicting disposition code has been removed from the cargo status array, when the system logs the removal action, the desired outcome is that the system records the removed disposition code details and the reason for removal and the timestamp of the action for audit trail purposes.
💻 Technical Criteria
Given A conflicting disposition code has been removed from the cargo status array
When The system logs the removal action
Then The system records the removed disposition code details AND the reason for removal AND the timestamp of the action for audit trail purposes
R-GCX016E-cbl-02140 Retrieve S09 Status Segments from Database
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve S09 Status Segments from Database' is invoked, and assuming that a cargo record exists in the system, when the system needs to process disposition codes for the cargo, the desired outcome is that the system retrieves all s09 status segments associated with the cargo from the database.
💻 Technical Criteria
Given A cargo record exists in the system
When The system needs to process disposition codes for the cargo
Then The system retrieves all S09 status segments associated with the cargo from the database
R-GCX016E-cbl-02141 Initialize Empty Status Array
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Empty Status Array' is invoked, and assuming that a cargo record has no existing s09 status segments in the database, when the system attempts to retrieve status segments, the desired outcome is that the system initializes empty s09a status arrays with zero entries and resets sequence counters.
💻 Technical Criteria
Given A cargo record has no existing S09 status segments in the database
When The system attempts to retrieve status segments
Then The system initializes empty S09A status arrays with zero entries and resets sequence counters
R-GCX016E-cbl-02142 Populate S09A Status Arrays from Database Segments
Process Rules
📊 Business Logic Narrative
When the process 'Populate S09A Status Arrays from Database Segments' is invoked, and assuming that s09 status segments exist in the database for a cargo, when the system retrieves the segments successfully, the desired outcome is that the system populates s09a status arrays with disposition codes, quantities, entry numbers, and sequence information from the database segments.
💻 Technical Criteria
Given S09 status segments exist in the database for a cargo
When The system retrieves the segments successfully
Then The system populates S09A status arrays with disposition codes, quantities, entry numbers, and sequence information from the database segments
R-GCX016E-cbl-02145 Handle Duplicate According to Business Rules
Decision Rules
📊 Business Logic Narrative
When the process 'Handle Duplicate According to Business Rules' is invoked, and assuming that a duplicate disposition code is found in the status arrays, when the duplicate has matching entry number and quantity, the desired outcome is that the system applies business rules such as removal, replacement, or skip processing based on the disposition code type and current cargo status.
💻 Technical Criteria
Given A duplicate disposition code is found in the status arrays
When The duplicate has matching entry number and quantity
Then The system applies business rules such as removal, replacement, or skip processing based on the disposition code type and current cargo status
R-GCX016E-cbl-02154 Replace Status Segments in Database
Action Rules
📊 Business Logic Narrative
When the process 'Replace Status Segments in Database' is invoked, and assuming that status arrays have been converted to database format, when the system updates the cargo record, the desired outcome is that the system replaces the existing s09 status segments in the database with the updated segments containing current disposition code information.
💻 Technical Criteria
Given Status arrays have been converted to database format
When The system updates the cargo record
Then The system replaces the existing S09 status segments in the database with the updated segments containing current disposition code information
R-GCX016E-cbl-02155 Update Car ID Information for Non-CPRS Cargo
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Update Car ID Information for Non-CPRS Cargo', assuming that a cargo is not a cprs shipment and car identification information is available from n7 segment processing, when the system completes status array processing, the desired outcome is that the system updates the cargo record with the car id information derived from the equipment initial and number.
💻 Technical Criteria
EXCLUDING A cargo is not a CPRS shipment and car identification information is available from N7 segment processing
When The system completes status array processing
Then The system updates the cargo record with the car ID information derived from the equipment initial and number
R-GCX016E-cbl-02156 Retrieve Current Release Quantity
Definitional Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Release Quantity' is invoked, and assuming that a cargo record exists with release quantity information, when the system needs to calculate new release quantities, the desired outcome is that the current release quantity is retrieved from the cargo record.
💻 Technical Criteria
Given A cargo record exists with release quantity information
When The system needs to calculate new release quantities
Then The current release quantity is retrieved from the cargo record
R-GCX016E-cbl-02157 Get Disposition Code Action Type
Decision Rules
📊 Business Logic Narrative
When the process 'Get Disposition Code Action Type' is invoked, and assuming that a disposition code is being processed for a cargo, when the system evaluates the disposition code action requirements, the desired outcome is that the action type is determined as either add, subtract, or no action based on the disposition code characteristics.
💻 Technical Criteria
Given A disposition code is being processed for a cargo
When The system evaluates the disposition code action requirements
Then The action type is determined as either Add, Subtract, or No Action based on the disposition code characteristics
R-GCX016E-cbl-02162 Quantity Cannot Exceed Total
Validation Rules
📊 Business Logic Narrative
When the process 'Quantity Cannot Exceed Total' is invoked, and assuming that a new release quantity has been calculated and total cargo quantity is known, when the calculated release quantity exceeds the total cargo quantity, the desired outcome is that the quantity calculation is rejected and processing terminates with validation error.
💻 Technical Criteria
Given A new release quantity has been calculated and total cargo quantity is known
When The calculated release quantity exceeds the total cargo quantity
Then The quantity calculation is rejected and processing terminates with validation error
R-GCX016E-cbl-02163 Update Release Quantity
Action Rules
📊 Business Logic Narrative
When the process 'Update Release Quantity' is invoked, and assuming that a new release quantity has passed all validation checks, when the quantity is valid and within acceptable ranges, the desired outcome is that the cargo record is updated with the new release quantity.
💻 Technical Criteria
Given A new release quantity has passed all validation checks
When The quantity is valid and within acceptable ranges
Then The cargo record is updated with the new release quantity
R-GCX016E-cbl-02164 Set Release Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Set Release Status Flags' is invoked, and assuming that cargo release quantity has been updated, when release quantity changes require status flag updates, the desired outcome is that appropriate release status flags are set on the cargo record.
💻 Technical Criteria
Given Cargo release quantity has been updated
When Release quantity changes require status flag updates
Then Appropriate release status flags are set on the cargo record
R-GCX016E-cbl-02165 Full Release?
Decision Rules
📊 Business Logic Narrative
When the process 'Full Release?' is invoked, and assuming that cargo has an updated release quantity and known total quantity, when the system needs to determine release completion status, the desired outcome is that if release quantity equals total quantity, cargo is fully released; otherwise cargo is partially released.
💻 Technical Criteria
Given Cargo has an updated release quantity and known total quantity
When The system needs to determine release completion status
Then If release quantity equals total quantity, cargo is fully released; otherwise cargo is partially released
R-GCX016E-cbl-02166 Mark Cargo as Fully Released
Action Rules
📊 Business Logic Narrative
When the process 'Mark Cargo as Fully Released' is invoked, and assuming that cargo release quantity equals the total cargo quantity, when full release status is determined, the desired outcome is that cargo is marked with fully released status.
💻 Technical Criteria
Given Cargo release quantity equals the total cargo quantity
When Full release status is determined
Then Cargo is marked with fully released status
R-GCX016E-cbl-02167 Mark Cargo as Partially Released
Action Rules
📊 Business Logic Narrative
When the process 'Mark Cargo as Partially Released' is invoked, and assuming that cargo release quantity is less than the total cargo quantity, when partial release status is determined, the desired outcome is that cargo is marked with partially released status.
💻 Technical Criteria
Given Cargo release quantity is less than the total cargo quantity
When Partial release status is determined
Then Cargo is marked with partially released status
R-GCX016E-cbl-02168 Log Quantity Change
Process Rules
📊 Business Logic Narrative
When the process 'Log Quantity Change' is invoked, and assuming that cargo release quantity has been successfully updated, when quantity change needs to be recorded for audit purposes, the desired outcome is that a log entry is created with old quantity, new quantity, and change details.
💻 Technical Criteria
Given Cargo release quantity has been successfully updated
When Quantity change needs to be recorded for audit purposes
Then A log entry is created with old quantity, new quantity, and change details
R-GCX016E-cbl-02170 Cargo Hold Status Detected?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Hold Status Detected?' is invoked, and assuming that a cargo has completed status evaluation processing, when the system checks the cargo's current status flags, the desired outcome is that the system identifies if the cargo has any active hold conditions (border hold, destination hold, fda hold, piece count hold, or general hold) and proceeds with hold notification processing if holds are detected, otherwise ends the notification process.
💻 Technical Criteria
Given A cargo has completed status evaluation processing
When The system checks the cargo's current status flags
Then The system identifies if the cargo has any active hold conditions (border hold, destination hold, FDA hold, piece count hold, or general hold) and proceeds with hold notification processing if holds are detected, otherwise ends the notification process
R-GCX016E-cbl-02171 Retrieve Location Information
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Location Information' is invoked, and assuming that a cargo with hold status has been identified for notification, when the system needs to create a detailed hold notification, the desired outcome is that the system retrieves location information from location tables (gcstbrt) including origin, destination, and current location details to provide business context for the hold notification.
💻 Technical Criteria
Given A cargo with hold status has been identified for notification
When The system needs to create a detailed hold notification
Then The system retrieves location information from location tables (GCSTBRT) including origin, destination, and current location details to provide business context for the hold notification
R-GCX016E-cbl-02172 Gather Disposition Code Details
Action Rules
📊 Business Logic Narrative
When the process 'Gather Disposition Code Details' is invoked, and assuming that location information has been retrieved for a held cargo, when the system processes disposition code information, the desired outcome is that the system gathers disposition code details from status segments (gcsuss09) and disposition code tables including code descriptions, entry numbers, quantities, and associated business reasons for the hold.
💻 Technical Criteria
Given Location information has been retrieved for a held cargo
When The system processes disposition code information
Then The system gathers disposition code details from status segments (GCSUSS09) and disposition code tables including code descriptions, entry numbers, quantities, and associated business reasons for the hold
R-GCX016E-cbl-02173 Determine Hold Type
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Hold Type' is invoked, and assuming that disposition code details have been gathered for a held cargo, when the system evaluates the hold conditions and status flags, the desired outcome is that the system determines the specific hold type (border hold, destination hold, fda hold, piece count hold, or general hold) based on the cargo's status flags and disposition codes.
💻 Technical Criteria
Given Disposition code details have been gathered for a held cargo
When The system evaluates the hold conditions and status flags
Then The system determines the specific hold type (Border Hold, Destination Hold, FDA Hold, Piece Count Hold, or General Hold) based on the cargo's status flags and disposition codes
R-GCX016E-cbl-02174 Border Hold Notification
Process Rules
📊 Business Logic Narrative
When the process 'Border Hold Notification' is invoked, and assuming that a cargo has been classified as having a border hold type, when the system processes the border hold notification, the desired outcome is that the system creates a border-specific hold notification with appropriate border location context, regulatory information, and routes the notification to border processing personnel.
💻 Technical Criteria
Given A cargo has been classified as having a border hold type
When The system processes the border hold notification
Then The system creates a border-specific hold notification with appropriate border location context, regulatory information, and routes the notification to border processing personnel
R-GCX016E-cbl-02175 Destination Hold Notification
Process Rules
📊 Business Logic Narrative
When the process 'Destination Hold Notification' is invoked, and assuming that a cargo has been classified as having a destination hold type, when the system processes the destination hold notification, the desired outcome is that the system creates a destination-specific hold notification with destination location details, consignee information, and routes the notification to destination processing personnel.
💻 Technical Criteria
Given A cargo has been classified as having a destination hold type
When The system processes the destination hold notification
Then The system creates a destination-specific hold notification with destination location details, consignee information, and routes the notification to destination processing personnel
R-GCX016E-cbl-02176 FDA Hold Notification
Policy Rules
📊 Business Logic Narrative
When the process 'FDA Hold Notification' is invoked, and assuming that a cargo has been classified as having an fda hold type, when the system processes the fda hold notification, the desired outcome is that the system creates an fda-specific hold notification with regulatory compliance details, fda examination requirements, and routes the notification to fda processing personnel and relevant regulatory contacts.
💻 Technical Criteria
Given A cargo has been classified as having an FDA hold type
When The system processes the FDA hold notification
Then The system creates an FDA-specific hold notification with regulatory compliance details, FDA examination requirements, and routes the notification to FDA processing personnel and relevant regulatory contacts
R-GCX016E-cbl-02177 Piece Count Hold Notification
Process Rules
📊 Business Logic Narrative
When the process 'Piece Count Hold Notification' is invoked, and assuming that a cargo has been classified as having a piece count hold type, when the system processes the piece count hold notification, the desired outcome is that the system creates a piece count-specific hold notification with quantity details, release information, partial hold status, and routes the notification to quantity verification personnel.
💻 Technical Criteria
Given A cargo has been classified as having a piece count hold type
When The system processes the piece count hold notification
Then The system creates a piece count-specific hold notification with quantity details, release information, partial hold status, and routes the notification to quantity verification personnel
R-GCX016E-cbl-02178 General Hold Notification
Process Rules
📊 Business Logic Narrative
When the process 'General Hold Notification' is invoked, and assuming that a cargo has been classified as having a general hold type (not border, destination, fda, or piece count), when the system processes the general hold notification, the desired outcome is that the system creates a general hold notification with standard hold information, disposition code details, and routes the notification to general processing personnel.
💻 Technical Criteria
Given A cargo has been classified as having a general hold type (not border, destination, FDA, or piece count)
When The system processes the general hold notification
Then The system creates a general hold notification with standard hold information, disposition code details, and routes the notification to general processing personnel
R-GCX016E-cbl-02180 Include Equipment Information
Process Rules
📊 Business Logic Narrative
When the process 'Include Equipment Information' is invoked, and assuming that hold details have been formatted for a cargo notification, when the system includes equipment information, the desired outcome is that the system adds equipment details from cargo data (gcsusrt) including car id, equipment type, equipment number, and container information to the hold notification.
💻 Technical Criteria
Given Hold details have been formatted for a cargo notification
When The system includes equipment information
Then The system adds equipment details from cargo data (GCSUSRT) including car ID, equipment type, equipment number, and container information to the hold notification
R-GCX016E-cbl-02188 Retrieve Complete S09A Status Arrays
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Complete S09A Status Arrays' is invoked, and assuming that a cargo record exists with associated status segments, when the system needs to evaluate cargo status, the desired outcome is that all s09a status array segments are retrieved and made available for analysis.
💻 Technical Criteria
Given A cargo record exists with associated status segments
When The system needs to evaluate cargo status
Then All S09A status array segments are retrieved and made available for analysis
R-GCX016E-cbl-02189 Analyze Individual Status Entries
Process Rules
📊 Business Logic Narrative
When the process 'Analyze Individual Status Entries' is invoked, and assuming that s09a status arrays have been retrieved for a cargo, when the system processes the status array, the desired outcome is that each individual status entry is analyzed for disposition code, quantity, and entry number information.
💻 Technical Criteria
Given S09A status arrays have been retrieved for a cargo
When The system processes the status array
Then Each individual status entry is analyzed for disposition code, quantity, and entry number information
R-GCX016E-cbl-02191 Evaluate Hold Types
Definitional Rules
📊 Business Logic Narrative
When the process 'Evaluate Hold Types' is invoked, and assuming that hold disposition codes are present in the status array, when the system evaluates hold types, the desired outcome is that hold codes are categorized as border hold, destination hold, fda hold, piece count hold, or customs intensive hold.
💻 Technical Criteria
Given Hold disposition codes are present in the status array
When The system evaluates hold types
Then Hold codes are categorized as border hold, destination hold, FDA hold, piece count hold, or customs intensive hold
R-GCX016E-cbl-02199 Override Hold Status
Policy Rules
📊 Business Logic Narrative
When the process 'Override Hold Status' is invoked, and assuming that manual release disposition codes are present in the status array, when the system processes manual release override, the desired outcome is that system-generated hold status is overridden and cargo is marked for release processing.
💻 Technical Criteria
Given Manual release disposition codes are present in the status array
When The system processes manual release override
Then System-generated hold status is overridden and cargo is marked for release processing
R-GCX016E-cbl-02203 All Conditions Met for Release?
Validation Rules
📊 Business Logic Narrative
When the process 'All Conditions Met for Release?' is invoked, and assuming that final release quantity has been calculated, when the system validates release conditions, the desired outcome is that all conditions are verified as met if no active holds exist, release quantity equals or exceeds cargo quantity, and all regulatory requirements are satisfied.
💻 Technical Criteria
Given Final release quantity has been calculated
When The system validates release conditions
Then All conditions are verified as met if no active holds exist, release quantity equals or exceeds cargo quantity, and all regulatory requirements are satisfied
R-GCX016E-cbl-02204 Set Status: RELEASED
Action Rules
📊 Business Logic Narrative
When the process 'Set Status: RELEASED' is invoked, and assuming that all conditions for release have been met, when the system sets final cargo status, the desired outcome is that cargo status is set to released and release flags are activated.
💻 Technical Criteria
Given All conditions for release have been met
When The system sets final cargo status
Then Cargo status is set to RELEASED and release flags are activated
R-GCX016E-cbl-02205 Set Status: HELD
Action Rules
📊 Business Logic Narrative
When the process 'Set Status: HELD' is invoked, and assuming that not all conditions for release have been met, when the system sets final cargo status, the desired outcome is that cargo status is set to held with appropriate hold type designation and hold flags are activated.
💻 Technical Criteria
Given Not all conditions for release have been met
When The system sets final cargo status
Then Cargo status is set to HELD with appropriate hold type designation and hold flags are activated
R-GCX016E-cbl-02206 Export Processing Required?
Decision Rules
📊 Business Logic Narrative
When the process 'Export Processing Required?' is invoked, and assuming that cargo status has been set to either released or held, when the system evaluates export processing requirements, the desired outcome is that export processing is required if export disposition codes are present and cargo destination is outside the country.
💻 Technical Criteria
Given Cargo status has been set to either RELEASED or HELD
When The system evaluates export processing requirements
Then Export processing is required if export disposition codes are present and cargo destination is outside the country
R-GCX016E-cbl-02207 Set Status: EXPORTED
Action Rules
📊 Business Logic Narrative
When the process 'Set Status: EXPORTED' is invoked, and assuming that export processing is required for the cargo, when the system processes export status, the desired outcome is that cargo status is set to exported and export flags are activated with appropriate export date.
💻 Technical Criteria
Given Export processing is required for the cargo
When The system processes export status
Then Cargo status is set to EXPORTED and export flags are activated with appropriate export date
R-GCX016E-cbl-02208 Arrival Processing Required?
Decision Rules
📊 Business Logic Narrative
When the process 'Arrival Processing Required?' is invoked, and assuming that export processing evaluation has been completed, when the system evaluates arrival processing requirements, the desired outcome is that arrival processing is required if arrival disposition codes are present and cargo has reached its destination.
💻 Technical Criteria
Given Export processing evaluation has been completed
When The system evaluates arrival processing requirements
Then Arrival processing is required if arrival disposition codes are present and cargo has reached its destination
R-GCX016E-cbl-02209 Set Status: ARRIVED
Action Rules
📊 Business Logic Narrative
When the process 'Set Status: ARRIVED' is invoked, and assuming that arrival processing is required for the cargo, when the system processes arrival status, the desired outcome is that cargo status is set to arrived and arrival flags are activated with appropriate arrival date.
💻 Technical Criteria
Given Arrival processing is required for the cargo
When The system processes arrival status
Then Cargo status is set to ARRIVED and arrival flags are activated with appropriate arrival date
R-GCX016E-cbl-02210 Update Cargo Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status Flags' is invoked, and assuming that final cargo status has been determined (released, held, exported, or arrived), when the system updates cargo status flags, the desired outcome is that all relevant status flags are updated including hold flags, release flags, export flags, arrival flags, and processing flags.
💻 Technical Criteria
Given Final cargo status has been determined (RELEASED, HELD, EXPORTED, or ARRIVED)
When The system updates cargo status flags
Then All relevant status flags are updated including hold flags, release flags, export flags, arrival flags, and processing flags
R-GCX016E-cbl-02211 Generate Status Change Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Status Change Notification' is invoked, and assuming that cargo status flags have been updated, when the system generates status change notifications, the desired outcome is that notifications are sent to brokers, freight forwarders, and other relevant parties based on the status change type and notification preferences.
💻 Technical Criteria
Given Cargo status flags have been updated
When The system generates status change notifications
Then Notifications are sent to brokers, freight forwarders, and other relevant parties based on the status change type and notification preferences
R-GCX016E-cbl-02212 Is Cargo In-Bond Entry?
Validation Rules
📊 Business Logic Narrative
When the process 'Is Cargo In-Bond Entry?' is invoked, and assuming that a proceed disposition code is being processed for a cargo, when the system checks the cargo's entry type, the desired outcome is that the cargo is classified as in-bond if it has entry types 61, 62, 63, or 69, otherwise it is classified as non-in-bond.
💻 Technical Criteria
Given A proceed disposition code is being processed for a cargo
When The system checks the cargo's entry type
Then The cargo is classified as in-bond if it has entry types 61, 62, 63, or 69, otherwise it is classified as non-in-bond
R-GCX016E-cbl-02213 Set Master In-Bond Flag for Entry Types 61,62,63,69
Process Rules
📊 Business Logic Narrative
When the process 'Set Master In-Bond Flag for Entry Types 61,62,63,69' is invoked, and assuming that a cargo has an in-bond entry type and is undergoing proceed disposition processing, when the entry type is 61, 62, 63, or 69, the desired outcome is that the master in-bond flag is set to indicate this is a master in-bond movement.
💻 Technical Criteria
Given A cargo has an in-bond entry type and is undergoing proceed disposition processing
When The entry type is 61, 62, 63, or 69
Then The master in-bond flag is set to indicate this is a master in-bond movement
R-GCX016E-cbl-02214 Bond Information Available?
Decision Rules
📊 Business Logic Narrative
When the process 'Bond Information Available?' is invoked, and assuming that a cargo is being processed for proceed disposition with in-bond requirements, when the system checks for existing bond information, the desired outcome is that bond processing continues if bond data exists, otherwise entry number validation is performed.
💻 Technical Criteria
Given A cargo is being processed for proceed disposition with in-bond requirements
When The system checks for existing bond information
Then Bond processing continues if bond data exists, otherwise entry number validation is performed
R-GCX016E-cbl-02215 Clear Existing Bond Data
Process Rules
📊 Business Logic Narrative
When the process 'Clear Existing Bond Data' is invoked, and assuming that bond information is available for a cargo undergoing proceed disposition processing, when the system processes the bond information, the desired outcome is that all existing bond data fields are cleared to prepare for new bond information updates.
💻 Technical Criteria
Given Bond information is available for a cargo undergoing proceed disposition processing
When The system processes the bond information
Then All existing bond data fields are cleared to prepare for new bond information updates
R-GCX016E-cbl-02216 Update Bond Number Index
Process Rules
📊 Business Logic Narrative
When the process 'Update Bond Number Index' is invoked, and assuming that existing bond data has been cleared for a cargo, when new bond information is being processed, the desired outcome is that the bond number index is updated with the new bond number for tracking purposes.
💻 Technical Criteria
Given Existing bond data has been cleared for a cargo
When New bond information is being processed
Then The bond number index is updated with the new bond number for tracking purposes
R-GCX016E-cbl-02217 Set Broker QP Information
Process Rules
📊 Business Logic Narrative
When the process 'Set Broker QP Information' is invoked, and assuming that bond number index has been updated for a cargo, when broker information is being processed, the desired outcome is that the broker qualifying party information is set to establish broker responsibility for the bond.
💻 Technical Criteria
Given Bond number index has been updated for a cargo
When Broker information is being processed
Then The broker qualifying party information is set to establish broker responsibility for the bond
R-GCX016E-cbl-02218 Update Bond Owner Details
Process Rules
📊 Business Logic Narrative
When the process 'Update Bond Owner Details' is invoked, and assuming that broker qp information has been set for a cargo, when bond owner information is being processed, the desired outcome is that bond owner details are updated to reflect the current bond ownership information.
💻 Technical Criteria
Given Broker QP information has been set for a cargo
When Bond owner information is being processed
Then Bond owner details are updated to reflect the current bond ownership information
R-GCX016E-cbl-02220 Process In-Bond Control Number
Process Rules
📊 Business Logic Narrative
When the process 'Process In-Bond Control Number' is invoked, and assuming that the entry number has been validated as valid, when in-bond control number processing is initiated, the desired outcome is that the in-bond control number is processed and associated with the cargo record.
💻 Technical Criteria
Given The entry number has been validated as valid
When In-bond control number processing is initiated
Then The in-bond control number is processed and associated with the cargo record
R-GCX016E-cbl-02222 Set In-Bond Processing Flags
Process Rules
📊 Business Logic Narrative
When the process 'Set In-Bond Processing Flags' is invoked, and assuming that edi entry type codes have been converted to internal values, when in-bond processing flags need to be set, the desired outcome is that appropriate flags are set to indicate the cargo is undergoing in-bond processing.
💻 Technical Criteria
Given EDI entry type codes have been converted to internal values
When In-bond processing flags need to be set
Then Appropriate flags are set to indicate the cargo is undergoing in-bond processing
R-GCX016E-cbl-02223 Update Cargo Status to Proceed
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status to Proceed' is invoked, and assuming that all in-bond processing flags have been set or the cargo is non-in-bond, when the cargo status needs to be updated, the desired outcome is that the cargo status is updated to proceed to indicate the cargo can move forward in the process.
💻 Technical Criteria
Given All in-bond processing flags have been set or the cargo is non-in-bond
When The cargo status needs to be updated
Then The cargo status is updated to proceed to indicate the cargo can move forward in the process
R-GCX016E-cbl-02224 Log Proceed Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Proceed Action' is invoked, and assuming that the cargo status has been updated to proceed, when action logging is performed, the desired outcome is that the proceed action is logged with relevant details for audit trail and tracking purposes.
💻 Technical Criteria
Given The cargo status has been updated to proceed
When Action logging is performed
Then The proceed action is logged with relevant details for audit trail and tracking purposes
R-GCX016E-cbl-02227 Check Arrival Disposition Codes
Validation Rules
📊 Business Logic Narrative
When the process 'Check Arrival Disposition Codes' is invoked, and assuming that a disposition code is being processed for cargo status management, when the system checks if the disposition code is aad (actual arrival date) or pod (proof of delivery), the desired outcome is that the system identifies the code as an arrival disposition and proceeds with arrival processing.
💻 Technical Criteria
Given A disposition code is being processed for cargo status management
When The system checks if the disposition code is AAD (Actual Arrival Date) or POD (Proof of Delivery)
Then The system identifies the code as an arrival disposition and proceeds with arrival processing
R-GCX016E-cbl-02229 Set Cargo Arrival Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Cargo Arrival Status Flag' is invoked, and assuming that a valid arrival disposition code with valid location has been processed, when the system updates cargo status for arrival, the desired outcome is that the cargo arrival status flag is set to indicate the cargo has arrived.
💻 Technical Criteria
Given A valid arrival disposition code with valid location has been processed
When The system updates cargo status for arrival
Then The cargo arrival status flag is set to indicate the cargo has arrived
R-GCX016E-cbl-02230 Clear Bond Start Date
Action Rules
📊 Business Logic Narrative
When the process 'Clear Bond Start Date' is invoked, and assuming that cargo arrival status has been set, when the system processes the arrival event, the desired outcome is that the bond start date is cleared to reflect that the in-bond movement has ended.
💻 Technical Criteria
Given Cargo arrival status has been set
When The system processes the arrival event
Then The bond start date is cleared to reflect that the in-bond movement has ended
R-GCX016E-cbl-02231 Set Arrival Index
Action Rules
📊 Business Logic Narrative
When the process 'Set Arrival Index' is invoked, and assuming that cargo has arrived at a valid location, when the system processes the arrival status update, the desired outcome is that an arrival index is set to reference the arrival location for tracking purposes.
💻 Technical Criteria
Given Cargo has arrived at a valid location
When The system processes the arrival status update
Then An arrival index is set to reference the arrival location for tracking purposes
R-GCX016E-cbl-02232 Calculate Cargo Age
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Cargo Age' is invoked, and assuming that cargo has arrived and arrival date is recorded, when the system calculates cargo aging metrics, the desired outcome is that the cargo age is computed as the difference between arrival date and original entry date.
💻 Technical Criteria
Given Cargo has arrived and arrival date is recorded
When The system calculates cargo aging metrics
Then The cargo age is computed as the difference between arrival date and original entry date
R-GCX016E-cbl-02233 Check Export Disposition Codes
Validation Rules
📊 Business Logic Narrative
When the process 'Check Export Disposition Codes' is invoked, and assuming that a disposition code is being processed for cargo status management, when the system checks if the disposition code indicates export processing, the desired outcome is that the system identifies the code as an export disposition and proceeds with export processing.
💻 Technical Criteria
Given A disposition code is being processed for cargo status management
When The system checks if the disposition code indicates export processing
Then The system identifies the code as an export disposition and proceeds with export processing
R-GCX016E-cbl-02235 Set Cargo Export Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Cargo Export Status Flag' is invoked, and assuming that a valid export disposition code with valid location has been processed, when the system updates cargo status for export, the desired outcome is that the cargo export status flag is set to indicate the cargo is being exported.
💻 Technical Criteria
Given A valid export disposition code with valid location has been processed
When The system updates cargo status for export
Then The cargo export status flag is set to indicate the cargo is being exported
R-GCX016E-cbl-02236 Clear Destination Index
Action Rules
📊 Business Logic Narrative
When the process 'Clear Destination Index' is invoked, and assuming that cargo export status has been set, when the system processes the export event, the desired outcome is that the destination index is cleared since the cargo is leaving the country.
💻 Technical Criteria
Given Cargo export status has been set
When The system processes the export event
Then The destination index is cleared since the cargo is leaving the country
R-GCX016E-cbl-02237 Update Export Date
Action Rules
📊 Business Logic Narrative
When the process 'Update Export Date' is invoked, and assuming that cargo export status has been set, when the system records the export event, the desired outcome is that the export date is updated to reflect the current processing date and time.
💻 Technical Criteria
Given Cargo export status has been set
When The system records the export event
Then The export date is updated to reflect the current processing date and time
R-GCX016E-cbl-02238 Check Cancel Arrival Codes
Validation Rules
📊 Business Logic Narrative
When the process 'Check Cancel Arrival Codes' is invoked, and assuming that a disposition code is being processed for cargo status management, when the system checks if the disposition code indicates cancellation of arrival, the desired outcome is that the system identifies the code as a cancel arrival disposition and proceeds with arrival cancellation.
💻 Technical Criteria
Given A disposition code is being processed for cargo status management
When The system checks if the disposition code indicates cancellation of arrival
Then The system identifies the code as a cancel arrival disposition and proceeds with arrival cancellation
R-GCX016E-cbl-02239 Reset Arrival Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Reset Arrival Status Flag' is invoked, and assuming that a cancel arrival disposition code has been processed, when the system cancels the arrival status, the desired outcome is that the cargo arrival status flag is reset to indicate the cargo has not arrived.
💻 Technical Criteria
Given A cancel arrival disposition code has been processed
When The system cancels the arrival status
Then The cargo arrival status flag is reset to indicate the cargo has not arrived
R-GCX016E-cbl-02242 Check Cancel Export Codes
Validation Rules
📊 Business Logic Narrative
When the process 'Check Cancel Export Codes' is invoked, and assuming that a disposition code is being processed for cargo status management, when the system checks if the disposition code indicates cancellation of export, the desired outcome is that the system identifies the code as a cancel export disposition and proceeds with export cancellation.
💻 Technical Criteria
Given A disposition code is being processed for cargo status management
When The system checks if the disposition code indicates cancellation of export
Then The system identifies the code as a cancel export disposition and proceeds with export cancellation
R-GCX016E-cbl-02243 Reset Export Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Reset Export Status Flag' is invoked, and assuming that a cancel export disposition code has been processed, when the system cancels the export status, the desired outcome is that the cargo export status flag is reset to indicate the cargo is not being exported.
💻 Technical Criteria
Given A cancel export disposition code has been processed
When The system cancels the export status
Then The cargo export status flag is reset to indicate the cargo is not being exported
R-GCX016E-cbl-02246 Generate Status Change Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Status Change Notification' is invoked, and assuming that cargo arrival or export status has been updated or cancelled, when the system completes the status change processing, the desired outcome is that a status change notification is generated to inform relevant parties of the status update.
💻 Technical Criteria
Given Cargo arrival or export status has been updated or cancelled
When The system completes the status change processing
Then A status change notification is generated to inform relevant parties of the status update
R-GCX016E-cbl-02247 Update Cargo Status Arrays
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status Arrays' is invoked, and assuming that arrival or export status changes have been processed, when the system finalizes the status management, the desired outcome is that the cargo status arrays are updated with the new arrival and export status information.
💻 Technical Criteria
Given Arrival or export status changes have been processed
When The system finalizes the status management
Then The cargo status arrays are updated with the new arrival and export status information
R-GCX016E-cbl-02248 Cancel Arrival Processing
Decision Rules
📊 Business Logic Narrative
When the process 'Cancel Arrival Processing' is invoked, and assuming that a cargo has an active arrival status and a cancel arrival disposition code is processed, when the system processes the cancel arrival disposition code, the desired outcome is that the system initiates cancel arrival processing workflow.
💻 Technical Criteria
Given A cargo has an active arrival status and a cancel arrival disposition code is processed
When The system processes the cancel arrival disposition code
Then The system initiates cancel arrival processing workflow
R-GCX016E-cbl-02249 Cancel Export Processing
Decision Rules
📊 Business Logic Narrative
When the process 'Cancel Export Processing' is invoked, and assuming that a cargo has an active export status and a cancel export disposition code is processed, when the system processes the cancel export disposition code, the desired outcome is that the system initiates cancel export processing workflow.
💻 Technical Criteria
Given A cargo has an active export status and a cancel export disposition code is processed
When The system processes the cancel export disposition code
Then The system initiates cancel export processing workflow
R-GCX016E-cbl-02250 Retrieve Current Cargo Status
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Cargo Status' is invoked, and assuming that a cancellation request is being processed for a cargo, when the system needs to process the cancellation, the desired outcome is that the system retrieves the current cargo status from the cargo root record.
💻 Technical Criteria
Given A cancellation request is being processed for a cargo
When The system needs to process the cancellation
Then The system retrieves the current cargo status from the cargo root record
R-GCX016E-cbl-02251 Save Previous Status for Audit
Process Rules
📊 Business Logic Narrative
When the process 'Save Previous Status for Audit' is invoked, and assuming that a cargo status is about to be changed due to cancellation, when the system processes the status change, the desired outcome is that the system saves the previous status information to maintain audit trail.
💻 Technical Criteria
Given A cargo status is about to be changed due to cancellation
When The system processes the status change
Then The system saves the previous status information to maintain audit trail
R-GCX016E-cbl-02252 Clear Arrival Flag
Action Rules
📊 Business Logic Narrative
When the process 'Clear Arrival Flag' is invoked, and assuming that a cargo has an active arrival flag set and arrival cancellation is being processed, when the system processes the arrival cancellation, the desired outcome is that the system clears the arrival flag in the cargo record.
💻 Technical Criteria
Given A cargo has an active arrival flag set and arrival cancellation is being processed
When The system processes the arrival cancellation
Then The system clears the arrival flag in the cargo record
R-GCX016E-cbl-02253 Clear Export Flag
Action Rules
📊 Business Logic Narrative
When the process 'Clear Export Flag' is invoked, and assuming that a cargo has an active export flag set and export cancellation is being processed, when the system processes the export cancellation, the desired outcome is that the system clears the export flag in the cargo record.
💻 Technical Criteria
Given A cargo has an active export flag set and export cancellation is being processed
When The system processes the export cancellation
Then The system clears the export flag in the cargo record
R-GCX016E-cbl-02254 Reset Arrival Date
Action Rules
📊 Business Logic Narrative
When the process 'Reset Arrival Date' is invoked, and assuming that a cargo has an arrival date set and arrival cancellation is being processed, when the system processes the arrival cancellation, the desired outcome is that the system resets the arrival date to blank or previous value.
💻 Technical Criteria
Given A cargo has an arrival date set and arrival cancellation is being processed
When The system processes the arrival cancellation
Then The system resets the arrival date to blank or previous value
R-GCX016E-cbl-02255 Reset Export Date
Action Rules
📊 Business Logic Narrative
When the process 'Reset Export Date' is invoked, and assuming that a cargo has an export date set and export cancellation is being processed, when the system processes the export cancellation, the desired outcome is that the system resets the export date to blank or previous value.
💻 Technical Criteria
Given A cargo has an export date set and export cancellation is being processed
When The system processes the export cancellation
Then The system resets the export date to blank or previous value
R-GCX016E-cbl-02256 Restore Bond Information
Action Rules
📊 Business Logic Narrative
When the process 'Restore Bond Information' is invoked, and assuming that a cargo had bond information modified during arrival or export processing and cancellation is being processed, when the system processes the cancellation, the desired outcome is that the system restores the bond information to its previous state.
💻 Technical Criteria
Given A cargo had bond information modified during arrival or export processing and cancellation is being processed
When The system processes the cancellation
Then The system restores the bond information to its previous state
R-GCX016E-cbl-02257 Recalculate Cargo Age
Computation Rules
📊 Business Logic Narrative
When the process 'Recalculate Cargo Age' is invoked, and assuming that a cargo status has been changed due to cancellation and dates have been updated, when the system completes the status change processing, the desired outcome is that the system recalculates the cargo age based on the updated information.
💻 Technical Criteria
Given A cargo status has been changed due to cancellation and dates have been updated
When The system completes the status change processing
Then The system recalculates the cargo age based on the updated information
R-GCX016E-cbl-02258 Update Destination Index
Action Rules
📊 Business Logic Narrative
When the process 'Update Destination Index' is invoked, and assuming that a cargo cancellation has been processed and status has been updated, when the system completes the cancellation processing, the desired outcome is that the system updates the destination index to reflect the new status.
💻 Technical Criteria
Given A cargo cancellation has been processed and status has been updated
When The system completes the cancellation processing
Then The system updates the destination index to reflect the new status
R-GCX016E-cbl-02259 Generate Cancel Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Cancel Notification' is invoked, and assuming that a cargo cancellation has been successfully processed, when the system completes the cancellation processing, the desired outcome is that the system generates a cancel notification message for relevant parties.
💻 Technical Criteria
Given A cargo cancellation has been successfully processed
When The system completes the cancellation processing
Then The system generates a cancel notification message for relevant parties
R-GCX016E-cbl-02260 Log Status Change
Process Rules
📊 Business Logic Narrative
When the process 'Log Status Change' is invoked, and assuming that a cargo status has been changed due to cancellation processing, when the system completes the status change, the desired outcome is that the system logs the status change with timestamp and details for audit purposes.
💻 Technical Criteria
Given A cargo status has been changed due to cancellation processing
When The system completes the status change
Then The system logs the status change with timestamp and details for audit purposes
R-GCX016E-cbl-02261 Update Status Arrays
Action Rules
📊 Business Logic Narrative
When the process 'Update Status Arrays' is invoked, and assuming that a cargo cancellation has been processed and status has been determined, when the system updates the cargo record, the desired outcome is that the system updates all relevant status arrays to reflect the cancellation changes.
💻 Technical Criteria
Given A cargo cancellation has been processed and status has been determined
When The system updates the cargo record
Then The system updates all relevant status arrays to reflect the cancellation changes
R-GCX016E-cbl-02262 Verify Status Restoration
Validation Rules
📊 Business Logic Narrative
When the process 'Verify Status Restoration' is invoked, and assuming that a cargo cancellation has been processed and status arrays have been updated, when the system completes the update process, the desired outcome is that the system verifies that the status has been properly restored and is consistent.
💻 Technical Criteria
Given A cargo cancellation has been processed and status arrays have been updated
When The system completes the update process
Then The system verifies that the status has been properly restored and is consistent
R-GCX016E-cbl-02263 Send Cancellation Message
Action Rules
📊 Business Logic Narrative
When the process 'Send Cancellation Message' is invoked, and assuming that a cargo cancellation has been verified and processed successfully, when the system completes all internal processing, the desired outcome is that the system sends cancellation message to external systems and interested parties.
💻 Technical Criteria
Given A cargo cancellation has been verified and processed successfully
When The system completes all internal processing
Then The system sends cancellation message to external systems and interested parties
R-GCX016E-cbl-02269 Set Status Information Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Status Information Flag' is invoked, and assuming that a status information disposition code has been successfully inserted into the s09a array, when the system processes the status information addition, the desired outcome is that the status information flag is set to indicate informational status has been applied to the cargo.
💻 Technical Criteria
Given A status information disposition code has been successfully inserted into the S09A array
When The system processes the status information addition
Then The status information flag is set to indicate informational status has been applied to the cargo
R-GCX016E-cbl-02272 Preserve Status Information for Audit Trail
Policy Rules
📊 Business Logic Narrative
When the process 'Preserve Status Information for Audit Trail' is invoked, and assuming that status information has been logged for a cargo disposition code change, when the system processes audit trail requirements, the desired outcome is that the status information change is preserved in the audit trail with complete context for future reference.
💻 Technical Criteria
Given Status information has been logged for a cargo disposition code change
When The system processes audit trail requirements
Then The status information change is preserved in the audit trail with complete context for future reference
R-GCX016E-cbl-02274 Retrieve Current Cargo Status
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Cargo Status' is invoked, and assuming that a cargo record exists in the system with current status information, when the system needs to preserve cargo status for audit purposes, the desired outcome is that the current cargo status is retrieved from the cargo root record including all status flags and values.
💻 Technical Criteria
Given A cargo record exists in the system with current status information
When The system needs to preserve cargo status for audit purposes
Then The current cargo status is retrieved from the cargo root record including all status flags and values
R-GCX016E-cbl-02275 Save Current Status to Audit Fields
Process Rules
📊 Business Logic Narrative
When the process 'Save Current Status to Audit Fields' is invoked, and assuming that current cargo status has been retrieved from the cargo record, when status preservation process is initiated, the desired outcome is that current status values are copied to corresponding audit fields in the cargo record.
💻 Technical Criteria
Given Current cargo status has been retrieved from the cargo record
When Status preservation process is initiated
Then Current status values are copied to corresponding audit fields in the cargo record
R-GCX016E-cbl-02276 Store Previous Release Quantities
Process Rules
📊 Business Logic Narrative
When the process 'Store Previous Release Quantities' is invoked, and assuming that cargo record contains current release quantity information, when release quantities are about to be modified, the desired outcome is that previous release quantities are stored in audit fields for historical tracking.
💻 Technical Criteria
Given Cargo record contains current release quantity information
When Release quantities are about to be modified
Then Previous release quantities are stored in audit fields for historical tracking
R-GCX016E-cbl-02277 Preserve Hold Status Flags
Process Rules
📊 Business Logic Narrative
When the process 'Preserve Hold Status Flags' is invoked, and assuming that cargo record has current hold status flags set, when hold status is about to be changed, the desired outcome is that all current hold status flags are preserved in audit fields for comparison purposes.
💻 Technical Criteria
Given Cargo record has current hold status flags set
When Hold status is about to be changed
Then All current hold status flags are preserved in audit fields for comparison purposes
R-GCX016E-cbl-02278 Save Arrival/Export Status
Process Rules
📊 Business Logic Narrative
When the process 'Save Arrival/Export Status' is invoked, and assuming that cargo record contains arrival or export status information, when arrival or export status is about to be updated, the desired outcome is that current arrival and export status values including dates are saved to audit fields.
💻 Technical Criteria
Given Cargo record contains arrival or export status information
When Arrival or export status is about to be updated
Then Current arrival and export status values including dates are saved to audit fields
R-GCX016E-cbl-02279 Store Bond Information
Process Rules
📊 Business Logic Narrative
When the process 'Store Bond Information' is invoked, and assuming that cargo record has bond information including bond numbers and broker details, when bond information is about to be modified, the desired outcome is that current bond information is stored in audit fields for historical reference.
💻 Technical Criteria
Given Cargo record has bond information including bond numbers and broker details
When Bond information is about to be modified
Then Current bond information is stored in audit fields for historical reference
R-GCX016E-cbl-02280 Save Disposition Code Arrays
Process Rules
📊 Business Logic Narrative
When the process 'Save Disposition Code Arrays' is invoked, and assuming that cargo record contains disposition code arrays with current status codes, when disposition codes are about to be processed or modified, the desired outcome is that current disposition code arrays are saved to audit fields maintaining sequence and occurrence information.
💻 Technical Criteria
Given Cargo record contains disposition code arrays with current status codes
When Disposition codes are about to be processed or modified
Then Current disposition code arrays are saved to audit fields maintaining sequence and occurrence information
R-GCX016E-cbl-02281 Create Status Snapshot
Process Rules
📊 Business Logic Narrative
When the process 'Create Status Snapshot' is invoked, and assuming that all individual status components have been preserved in audit fields, when complete status preservation is required, the desired outcome is that a comprehensive status snapshot is created capturing all cargo status elements at the current point in time.
💻 Technical Criteria
Given All individual status components have been preserved in audit fields
When Complete status preservation is required
Then A comprehensive status snapshot is created capturing all cargo status elements at the current point in time
R-GCX016E-cbl-02283 Cargo Status Change Detected
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Status Change Detected' is invoked, and assuming that a cargo record exists in the system, when the cargo processing logic is executed and status arrays are updated, the desired outcome is that the system detects that a cargo status change has occurred and triggers status analysis.
💻 Technical Criteria
Given A cargo record exists in the system
When The cargo processing logic is executed and status arrays are updated
Then The system detects that a cargo status change has occurred and triggers status analysis
R-GCX016E-cbl-02284 Save Previous Cargo Status
Process Rules
📊 Business Logic Narrative
When the process 'Save Previous Cargo Status' is invoked, and assuming that a cargo status change is detected, when the system begins processing the status change, the desired outcome is that the previous cargo status and release information is saved for comparison analysis.
💻 Technical Criteria
Given A cargo status change is detected
When The system begins processing the status change
Then The previous cargo status and release information is saved for comparison analysis
R-GCX016E-cbl-02285 Analyze Current Status Arrays
Process Rules
📊 Business Logic Narrative
When the process 'Analyze Current Status Arrays' is invoked, and assuming that previous cargo status has been saved, when the system processes the current cargo status arrays, the desired outcome is that the current cargo status and release information is analyzed and determined.
💻 Technical Criteria
Given Previous cargo status has been saved
When The system processes the current cargo status arrays
Then The current cargo status and release information is analyzed and determined
R-GCX016E-cbl-02286 Release Status Changed?
Decision Rules
📊 Business Logic Narrative
When the process 'Release Status Changed?' is invoked, and assuming that previous cargo status is saved and current status is analyzed, when the system compares the previous and current release status, the desired outcome is that the system determines whether the release status has changed or remained the same.
💻 Technical Criteria
Given Previous cargo status is saved and current status is analyzed
When The system compares the previous and current release status
Then The system determines whether the release status has changed or remained the same
R-GCX016E-cbl-02288 Was Previously Released?
Validation Rules
📊 Business Logic Narrative
When the process 'Was Previously Released?' is invoked, and assuming that release status comparison is performed, when the system evaluates the previous release status, the desired outcome is that the system determines if the cargo was previously in a released state.
💻 Technical Criteria
Given Release status comparison is performed
When The system evaluates the previous release status
Then The system determines if the cargo was previously in a released state
R-GCX016E-cbl-02289 Is Currently Released?
Validation Rules
📊 Business Logic Narrative
When the process 'Is Currently Released?' is invoked, and assuming that the cargo was previously released, when the system evaluates the current release status, the desired outcome is that the system determines if the cargo is currently in a released state.
💻 Technical Criteria
Given The cargo was previously released
When The system evaluates the current release status
Then The system determines if the cargo is currently in a released state
R-GCX016E-cbl-02290 Detect Release Cancellation
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Detect Release Cancellation', assuming that the cargo was previously released and is currently not released, when the system analyzes the status transition, the desired outcome is that the system detects that a release cancellation has occurred.
💻 Technical Criteria
EXCLUDING The cargo was previously released and is currently not released
When The system analyzes the status transition
Then The system detects that a release cancellation has occurred
R-GCX016E-cbl-02292 Format Cancellation Message Details
Process Rules
📊 Business Logic Narrative
When the process 'Format Cancellation Message Details' is invoked, and assuming that a release cancellation notification is being generated, when the system formats the cancellation message, the desired outcome is that the message includes cargo identification, cancellation details, and relevant transaction information.
💻 Technical Criteria
Given A release cancellation notification is being generated
When The system formats the cancellation message
Then The message includes cargo identification, cancellation details, and relevant transaction information
R-GCX016E-cbl-02293 Include Equipment Information
Process Rules
📊 Business Logic Narrative
When the process 'Include Equipment Information' is invoked, and assuming that a cancellation message is being formatted, when the system processes equipment information, the desired outcome is that the message includes car id, equipment type, and other relevant equipment details.
💻 Technical Criteria
Given A cancellation message is being formatted
When The system processes equipment information
Then The message includes car ID, equipment type, and other relevant equipment details
R-GCX016E-cbl-02294 Include Disposition Code Details
Process Rules
📊 Business Logic Narrative
When the process 'Include Disposition Code Details' is invoked, and assuming that equipment information is included in the cancellation message, when the system processes disposition code information, the desired outcome is that the message includes the disposition code that triggered the release cancellation.
💻 Technical Criteria
Given Equipment information is included in the cancellation message
When The system processes disposition code information
Then The message includes the disposition code that triggered the release cancellation
R-GCX016E-cbl-02299 No Cancellation Detected
Process Rules
📊 Business Logic Narrative
When the process 'No Cancellation Detected' is invoked, and assuming that the cargo status change analysis is complete, when no release cancellation is detected, the desired outcome is that the system continues with normal cargo processing without generating cancellation notifications.
💻 Technical Criteria
Given The cargo status change analysis is complete
When No release cancellation is detected
Then The system continues with normal cargo processing without generating cancellation notifications
R-GCX016E-cbl-02300 Initialize Status Flags
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Status Flags' is invoked, and assuming that a cargo record requires status evaluation, when the complex status logic evaluation process begins, the desired outcome is that all status flags (hold, release, proceed, arrival, export) are set to false or initial values.
💻 Technical Criteria
Given A cargo record requires status evaluation
When The complex status logic evaluation process begins
Then All status flags (hold, release, proceed, arrival, export) are set to false or initial values
R-GCX016E-cbl-02301 Retrieve S09A Status Arrays
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve S09A Status Arrays' is invoked, and assuming that a cargo record exists with associated disposition codes, when status evaluation process starts, the desired outcome is that all s09a status array entries are loaded for analysis.
💻 Technical Criteria
Given A cargo record exists with associated disposition codes
When Status evaluation process starts
Then All S09A status array entries are loaded for analysis
R-GCX016E-cbl-02313 Analyze Combined Status Flags
Process Rules
📊 Business Logic Narrative
When the process 'Analyze Combined Status Flags' is invoked, and assuming that all disposition codes have been processed and status flags are set, when determining the final cargo status, the desired outcome is that analyze the combination of status flags according to business priority hierarchy.
💻 Technical Criteria
Given All disposition codes have been processed and status flags are set
When Determining the final cargo status
Then Analyze the combination of status flags according to business priority hierarchy
R-GCX016E-cbl-02317 Set Final Status: HELD
Action Rules
📊 Business Logic Narrative
When the process 'Set Final Status: HELD' is invoked, and assuming that hold status is active and no manual release is present, when determining final status, the desired outcome is that set the cargo status to held.
💻 Technical Criteria
Given Hold status is active and no manual release is present
When Determining final status
Then Set the cargo status to HELD
R-GCX016E-cbl-02320 Set Final Status: PROCEED
Action Rules
📊 Business Logic Narrative
When the process 'Set Final Status: PROCEED' is invoked, and assuming that proceed status is active and in-bond entry conditions are met, when determining final status, the desired outcome is that set the cargo status to proceed.
💻 Technical Criteria
Given Proceed status is active and in-bond entry conditions are met
When Determining final status
Then Set the cargo status to PROCEED
R-GCX016E-cbl-02322 Set Final Status: ARRIVED
Action Rules
📊 Business Logic Narrative
When the process 'Set Final Status: ARRIVED' is invoked, and assuming that arrival status is active and no higher priority conditions exist, when determining final status, the desired outcome is that set the cargo status to arrived.
💻 Technical Criteria
Given Arrival status is active and no higher priority conditions exist
When Determining final status
Then Set the cargo status to ARRIVED
R-GCX016E-cbl-02324 Set Final Status: EXPORTED
Action Rules
📊 Business Logic Narrative
When the process 'Set Final Status: EXPORTED' is invoked, and assuming that export status is active and no higher priority conditions exist, when determining final status, the desired outcome is that set the cargo status to exported.
💻 Technical Criteria
Given Export status is active and no higher priority conditions exist
When Determining final status
Then Set the cargo status to EXPORTED
R-GCX016E-cbl-02325 Set Final Status: RELEASED
Action Rules
📊 Business Logic Narrative
When the process 'Set Final Status: RELEASED' is invoked, and assuming that no specific status conditions (hold, proceed, arrival, export) are active, when determining final status, the desired outcome is that set the cargo status to released as the default.
💻 Technical Criteria
Given No specific status conditions (hold, proceed, arrival, export) are active
When Determining final status
Then Set the cargo status to RELEASED as the default
R-GCX016E-cbl-02326 Update Cargo Status
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status' is invoked, and assuming that final cargo status has been determined, when updating cargo information, the desired outcome is that the cargo record is updated with the new status.
💻 Technical Criteria
Given Final cargo status has been determined
When Updating cargo information
Then The cargo record is updated with the new status
R-GCX016E-cbl-02327 Generate Status Change Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Status Change Notification' is invoked, and assuming that cargo status has been updated, when status change processing is complete, the desired outcome is that generate notifications to relevant parties about the status change.
💻 Technical Criteria
Given Cargo status has been updated
When Status change processing is complete
Then Generate notifications to relevant parties about the status change
R-GCX016E-cbl-02328 Save Current Cargo Status
Process Rules
📊 Business Logic Narrative
When the process 'Save Current Cargo Status' is invoked, and assuming that a cargo record exists with current status information, when the system begins cargo status processing, the desired outcome is that the current cargo status is saved to backup storage for potential restoration.
💻 Technical Criteria
Given A cargo record exists with current status information
When The system begins cargo status processing
Then The current cargo status is saved to backup storage for potential restoration
R-GCX016E-cbl-02329 Store Previous Status Information
Process Rules
📊 Business Logic Narrative
When the process 'Store Previous Status Information' is invoked, and assuming that current cargo status has been backed up, when the system prepares for status updates, the desired outcome is that previous status information including dates and codes is stored in audit storage.
💻 Technical Criteria
Given Current cargo status has been backed up
When The system prepares for status updates
Then Previous status information including dates and codes is stored in audit storage
R-GCX016E-cbl-02330 Status Update Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Status Update Successful?' is invoked, and assuming that cargo status updates have been attempted, when the system evaluates the update results, the desired outcome is that the system determines if updates were successful based on completion codes and data validation.
💻 Technical Criteria
Given Cargo status updates have been attempted
When The system evaluates the update results
Then The system determines if updates were successful based on completion codes and data validation
R-GCX016E-cbl-02331 Maintain Updated Status
Process Rules
📊 Business Logic Narrative
When the process 'Maintain Updated Status' is invoked, and assuming that cargo status updates completed successfully, when the system confirms successful update validation, the desired outcome is that the updated cargo status is maintained and processing continues normally.
💻 Technical Criteria
Given Cargo status updates completed successfully
When The system confirms successful update validation
Then The updated cargo status is maintained and processing continues normally
R-GCX016E-cbl-02332 Error Detected During Update
Validation Rules
📊 Business Logic Narrative
When the process 'Error Detected During Update' is invoked, and assuming that cargo status updates are in progress, when an error or failure occurs during the update process, the desired outcome is that the system detects the error condition and initiates error handling procedures.
💻 Technical Criteria
Given Cargo status updates are in progress
When An error or failure occurs during the update process
Then The system detects the error condition and initiates error handling procedures
R-GCX016E-cbl-02333 Restore Previous Cargo Status
Process Rules
📊 Business Logic Narrative
When the process 'Restore Previous Cargo Status' is invoked, and assuming that an error has been detected during cargo status updates and previous status backup exists, when the system initiates error recovery procedures, the desired outcome is that the cargo status is restored to its previous state from backup storage.
💻 Technical Criteria
Given An error has been detected during cargo status updates and previous status backup exists
When The system initiates error recovery procedures
Then The cargo status is restored to its previous state from backup storage
R-GCX016E-cbl-02334 Rollback Status Changes
Process Rules
📊 Business Logic Narrative
When the process 'Rollback Status Changes' is invoked, and assuming that previous cargo status has been restored from backup, when the system performs rollback operations, the desired outcome is that all status changes made during the failed update are reversed and data consistency is maintained.
💻 Technical Criteria
Given Previous cargo status has been restored from backup
When The system performs rollback operations
Then All status changes made during the failed update are reversed and data consistency is maintained
R-GCX016E-cbl-02335 Log Status Restoration Event
Process Rules
📊 Business Logic Narrative
When the process 'Log Status Restoration Event' is invoked, and assuming that status rollback operations have been completed, when the system finalizes the restoration process, the desired outcome is that a status restoration event is logged with timestamp, cargo identifier, and restoration details.
💻 Technical Criteria
Given Status rollback operations have been completed
When The system finalizes the restoration process
Then A status restoration event is logged with timestamp, cargo identifier, and restoration details
R-GCX016E-cbl-02336 Maintain Data Integrity
Validation Rules
📊 Business Logic Narrative
When the process 'Maintain Data Integrity' is invoked, and assuming that status processing has completed either successfully or through error recovery, when the system validates final data state, the desired outcome is that data integrity is confirmed and cargo information remains consistent across all related records.
💻 Technical Criteria
Given Status processing has completed either successfully or through error recovery
When The system validates final data state
Then Data integrity is confirmed and cargo information remains consistent across all related records
R-GCX016E-cbl-02337 Generate Error Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Error Notification' is invoked, and assuming that status restoration has been completed due to update errors, when the system generates error notifications, the desired outcome is that error notifications are created with cargo details, error description, and recovery actions taken.
💻 Technical Criteria
Given Status restoration has been completed due to update errors
When The system generates error notifications
Then Error notifications are created with cargo details, error description, and recovery actions taken
R-GCX016E-cbl-02338 Clear Bond Start Dates
Process Rules
📊 Business Logic Narrative
When the process 'Clear Bond Start Dates' is invoked, and assuming that a cargo is being processed for arrival and bond information exists in the cargo record, when the arrival processing is triggered, the desired outcome is that the bond start date should be reset to zero to clear previous bond timing.
💻 Technical Criteria
Given A cargo is being processed for arrival AND bond information exists in the cargo record
When The arrival processing is triggered
Then The bond start date should be reset to zero to clear previous bond timing
R-GCX016E-cbl-02339 Clear Bond Start Dates
Process Rules
📊 Business Logic Narrative
When the process 'Clear Bond Start Dates' is invoked, and assuming that a cargo is being processed for arrival and no bond information exists in the cargo record, when the arrival processing is triggered, the desired outcome is that the existing bond start date should be maintained without modification.
💻 Technical Criteria
Given A cargo is being processed for arrival AND no bond information exists in the cargo record
When The arrival processing is triggered
Then The existing bond start date should be maintained without modification
R-GCX016E-cbl-02340 Set Arrival Index
Process Rules
📊 Business Logic Narrative
When the process 'Set Arrival Index' is invoked, and assuming that a cargo is being processed for arrival and the current location is determined, when the arrival index needs to be set, the desired outcome is that the arrival index should be updated with the current location identifier.
💻 Technical Criteria
Given A cargo is being processed for arrival AND the current location is determined
When The arrival index needs to be set
Then The arrival index should be updated with the current location identifier
R-GCX016E-cbl-02341 Set Arrival Index
Process Rules
📊 Business Logic Narrative
When the process 'Set Arrival Index' is invoked, and assuming that a cargo has completed arrival index assignment, when the arrival processing procedures are finalized, the desired outcome is that the arrival processing flag should be set to indicate completion.
💻 Technical Criteria
Given A cargo has completed arrival index assignment
When The arrival processing procedures are finalized
Then The arrival processing flag should be set to indicate completion
R-GCX016E-cbl-02342 Calculate Cargo Age
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Cargo Age' is invoked, and assuming that a cargo has a valid bond start date, when cargo age calculation is required during arrival processing, the desired outcome is that the system should calculate the number of days between the bond start date and current date.
💻 Technical Criteria
Given A cargo has a valid bond start date
When Cargo age calculation is required during arrival processing
Then The system should calculate the number of days between the bond start date and current date
R-GCX016E-cbl-02343 Calculate Cargo Age
Process Rules
📊 Business Logic Narrative
When the process 'Calculate Cargo Age' is invoked, and assuming that the cargo age has been successfully calculated, when the age calculation is complete and valid, the desired outcome is that the cargo age field should be updated with the calculated number of days.
💻 Technical Criteria
Given The cargo age has been successfully calculated
When The age calculation is complete and valid
Then The cargo age field should be updated with the calculated number of days
R-GCX016E-cbl-02344 Validate Age Calculation
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Age Calculation' is invoked, and assuming that a cargo age has been calculated from bond start date, when the calculated age value needs validation, the desired outcome is that the system should verify that the age calculation is valid and within acceptable ranges.
💻 Technical Criteria
Given A cargo age has been calculated from bond start date
When The calculated age value needs validation
Then The system should verify that the age calculation is valid and within acceptable ranges
R-GCX016E-cbl-02345 Set Default Age Value
Validation Rules
📊 Business Logic Narrative
When the process 'Set Default Age Value' is invoked, and assuming that the cargo age calculation has failed validation or produced an invalid result, when a default age value is needed, the desired outcome is that the system should set a predefined default age value for the cargo.
💻 Technical Criteria
Given The cargo age calculation has failed validation OR produced an invalid result
When A default age value is needed
Then The system should set a predefined default age value for the cargo
R-GCX016E-cbl-02346 Clear Destination Index
Action Rules
📊 Business Logic Narrative
When the process 'Clear Destination Index' is invoked, and assuming that a cargo has an export disposition code, when the export processing is triggered, the desired outcome is that the destination index field is cleared to spaces.
💻 Technical Criteria
Given A cargo has an export disposition code
When The export processing is triggered
Then The destination index field is cleared to spaces
R-GCX016E-cbl-02347 Reset Bond Start Date
Process Rules
📊 Business Logic Narrative
When the process 'Reset Bond Start Date' is invoked, and assuming that a cargo is being processed for export, when the destination index has been cleared, the desired outcome is that the bond start date is reset to zeros.
💻 Technical Criteria
Given A cargo is being processed for export
When The destination index has been cleared
Then The bond start date is reset to zeros
R-GCX016E-cbl-02348 Update Export Flag
Action Rules
📊 Business Logic Narrative
When the process 'Update Export Flag' is invoked, and assuming that a cargo is undergoing export processing, when the bond start date has been reset, the desired outcome is that the export flag is set to 'y' to indicate export status.
💻 Technical Criteria
Given A cargo is undergoing export processing
When The bond start date has been reset
Then The export flag is set to 'Y' to indicate export status
R-GCX016E-cbl-02349 Calculate Cargo Age
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Cargo Age' is invoked, and assuming that a cargo has an arrival date and current processing date, when export processing is being performed, the desired outcome is that the cargo age is calculated as the difference between current date and arrival date.
💻 Technical Criteria
Given A cargo has an arrival date and current processing date
When Export processing is being performed
Then The cargo age is calculated as the difference between current date and arrival date
R-GCX016E-cbl-02350 Validate Export Location
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Export Location' is invoked, and assuming that a cargo has a specified export location, when export processing validation is performed, the desired outcome is that the system verifies the export location exists in the valid location table.
💻 Technical Criteria
Given A cargo has a specified export location
When Export processing validation is performed
Then The system verifies the export location exists in the valid location table
R-GCX016E-cbl-02351 Set Export Status to Active
Action Rules
📊 Business Logic Narrative
When the process 'Set Export Status to Active' is invoked, and assuming that a cargo has a valid export location, when export location validation is successful, the desired outcome is that the cargo export status is set to 'export' and marked as active.
💻 Technical Criteria
Given A cargo has a valid export location
When Export location validation is successful
Then The cargo export status is set to 'EXPORT' and marked as active
R-GCX016E-cbl-02352 Generate Export Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Export Notification' is invoked, and assuming that a cargo has been successfully set to export status, when export status is active, the desired outcome is that an export notification message is generated and sent to appropriate recipients.
💻 Technical Criteria
Given A cargo has been successfully set to export status
When Export status is active
Then An export notification message is generated and sent to appropriate recipients
R-GCX016E-cbl-02353 Update Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Record' is invoked, and assuming that a cargo has completed export processing steps, when all export data has been prepared, the desired outcome is that the cargo record is updated in the database with export status, cleared destination index, and reset bond date.
💻 Technical Criteria
Given A cargo has completed export processing steps
When All export data has been prepared
Then The cargo record is updated in the database with export status, cleared destination index, and reset bond date
R-GCX016E-cbl-02354 Log Export Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Export Action' is invoked, and assuming that a cargo has been processed for export, when the cargo record has been updated, the desired outcome is that an audit log entry is created recording the export action with timestamp and cargo details.
💻 Technical Criteria
Given A cargo has been processed for export
When The cargo record has been updated
Then An audit log entry is created recording the export action with timestamp and cargo details
R-GCX016E-cbl-02355 Generate Error Message
Validation Rules
📊 Business Logic Narrative
When the process 'Generate Error Message' is invoked, and assuming that a cargo has an invalid export location, when export location validation fails, the desired outcome is that an error message is generated indicating invalid export location and export processing is not completed.
💻 Technical Criteria
Given A cargo has an invalid export location
When Export location validation fails
Then An error message is generated indicating invalid export location and export processing is not completed
R-GCX016E-cbl-02356 Maintain Previous Status
Process Rules
📊 Business Logic Narrative
When the process 'Maintain Previous Status' is invoked, and assuming that export processing has encountered an error, when an error message has been generated, the desired outcome is that the cargo retains its previous status and no export changes are applied.
💻 Technical Criteria
Given Export processing has encountered an error
When An error message has been generated
Then The cargo retains its previous status and no export changes are applied
R-GCX016E-cbl-02357 Bond Information Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Bond Information Available?' is invoked, and assuming that a cargo status change has been detected, when the system checks for existing bond information, the desired outcome is that the system determines if bond data is available and routes processing accordingly.
💻 Technical Criteria
Given A cargo status change has been detected
When The system checks for existing bond information
Then The system determines if bond data is available and routes processing accordingly
R-GCX016E-cbl-02358 Retrieve Previous Bond Data
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Previous Bond Data' is invoked, and assuming that bond information is available for the cargo, when the system needs to restore bond information, the desired outcome is that the system retrieves the previous bond data from the cargo record.
💻 Technical Criteria
Given Bond information is available for the cargo
When The system needs to restore bond information
Then The system retrieves the previous bond data from the cargo record
R-GCX016E-cbl-02363 Calculate Current Date
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Current Date' is invoked, and assuming that broker qp information has been restored, when the system needs to calculate cargo age, the desired outcome is that the system calculates the current system date.
💻 Technical Criteria
Given Broker QP information has been restored
When The system needs to calculate cargo age
Then The system calculates the current system date
R-GCX016E-cbl-02364 Calculate Cargo Age in Days
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Cargo Age in Days' is invoked, and assuming that the current date has been calculated and bond start date is available, when the system calculates cargo age, the desired outcome is that the system computes the difference in days between current date and bond start date.
💻 Technical Criteria
Given The current date has been calculated and bond start date is available
When The system calculates cargo age
Then The system computes the difference in days between current date and bond start date
R-GCX016E-cbl-02365 Age Calculation Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Age Calculation Valid?' is invoked, and assuming that cargo age has been calculated in days, when the system validates the age calculation, the desired outcome is that the system determines if the calculated age is valid and within business rules.
💻 Technical Criteria
Given Cargo age has been calculated in days
When The system validates the age calculation
Then The system determines if the calculated age is valid and within business rules
R-GCX016E-cbl-02366 Update Cargo Age Field
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo Age Field' is invoked, and assuming that the age calculation is valid, when the system updates cargo information, the desired outcome is that the system updates the cargo age field with the calculated age in days.
💻 Technical Criteria
Given The age calculation is valid
When The system updates cargo information
Then The system updates the cargo age field with the calculated age in days
R-GCX016E-cbl-02367 Set Bond Restoration Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Bond Restoration Flag' is invoked, and assuming that cargo age has been updated or age calculation was invalid, when the system completes bond restoration processing, the desired outcome is that the system sets the bond restoration completion flag.
💻 Technical Criteria
Given Cargo age has been updated or age calculation was invalid
When The system completes bond restoration processing
Then The system sets the bond restoration completion flag
R-GCX016E-cbl-02369 Update Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Record' is invoked, and assuming that bond restoration action has been logged, when the system finalizes the restoration process, the desired outcome is that the system updates the cargo record with all restored bond information, age calculation, and restoration flags.
💻 Technical Criteria
Given Bond restoration action has been logged
When The system finalizes the restoration process
Then The system updates the cargo record with all restored bond information, age calculation, and restoration flags
R-GCX016E-cbl-02373 Update Cargo Status and Disposition Codes
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status and Disposition Codes' is invoked, and assuming that an individual cargo record is being processed with current disposition code context, when the system updates the cargo record, the desired outcome is that the system applies the disposition code to the cargo's status array and updates the cargo status according to disposition code processing rules.
💻 Technical Criteria
Given An individual cargo record is being processed with current disposition code context
When The system updates the cargo record
Then The system applies the disposition code to the cargo's status array and updates the cargo status according to disposition code processing rules
R-GCX016E-cbl-02380 Generate Export Notification if Applicable
Action Rules
📊 Business Logic Narrative
When the process 'Generate Export Notification if Applicable' is invoked, and assuming that cargo records have been processed and comprehensive release notification generated, when the system evaluates export notification requirements, the desired outcome is that if any cargo records have export status or export-related disposition codes, generate appropriate export notifications.
💻 Technical Criteria
Given Cargo records have been processed and comprehensive release notification generated
When The system evaluates export notification requirements
Then If any cargo records have export status or export-related disposition codes, generate appropriate export notifications
R-GCX016E-cbl-02381 Generate Arrival Notification if Applicable
Action Rules
📊 Business Logic Narrative
When the process 'Generate Arrival Notification if Applicable' is invoked, and assuming that export notifications have been processed for applicable cargo records, when the system evaluates arrival notification requirements, the desired outcome is that if any cargo records have arrival status or arrival-related disposition codes, generate appropriate arrival notifications.
💻 Technical Criteria
Given Export notifications have been processed for applicable cargo records
When The system evaluates arrival notification requirements
Then If any cargo records have arrival status or arrival-related disposition codes, generate appropriate arrival notifications
R-GCX016E-cbl-03095 Start Multi-Cargo Status Verification
Process Rules
📊 Business Logic Narrative
When the process 'Start Multi-Cargo Status Verification' is invoked, and assuming that a cargo record requires multi-cargo status verification, when the multi-cargo status verification process is initiated, the desired outcome is that the verification process begins and prepares to retrieve related cargo records.
💻 Technical Criteria
Given A cargo record requires multi-cargo status verification
When The multi-cargo status verification process is initiated
Then The verification process begins and prepares to retrieve related cargo records
R-GCX016E-cbl-03098 Process Individual Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Process Individual Cargo Record' is invoked, and assuming that an individual cargo record is selected for processing, when the record processing begins, the desired outcome is that the cargo record is prepared for hold status analysis.
💻 Technical Criteria
Given An individual cargo record is selected for processing
When The record processing begins
Then The cargo record is prepared for hold status analysis
R-GCX016E-cbl-03099 Analyze Cargo Hold Status
Process Rules
📊 Business Logic Narrative
When the process 'Analyze Cargo Hold Status' is invoked, and assuming that a cargo record is being processed for status verification, when the hold status analysis is performed, the desired outcome is that the system evaluates all hold conditions and release status for the cargo.
💻 Technical Criteria
Given A cargo record is being processed for status verification
When The hold status analysis is performed
Then The system evaluates all hold conditions and release status for the cargo
R-GCX016E-cbl-03100 Check Manual Release Status
Decision Rules
📊 Business Logic Narrative
When the process 'Check Manual Release Status' is invoked, and assuming that a cargo record is being analyzed for release status, when the system checks for manual release indicators, the desired outcome is that if manual release is found, skip other hold checks and mark as released, otherwise continue with hold type evaluation.
💻 Technical Criteria
Given A cargo record is being analyzed for release status
When The system checks for manual release indicators
Then If manual release is found, skip other hold checks and mark as released, otherwise continue with hold type evaluation
R-GCX016E-cbl-03101 Check Various Hold Types
Process Rules
📊 Business Logic Narrative
When the process 'Check Various Hold Types' is invoked, and assuming that a cargo record without manual release is being processed, when hold type evaluation begins, the desired outcome is that the system proceeds to check border holds, destination holds, fda holds, and piece count holds.
💻 Technical Criteria
Given A cargo record without manual release is being processed
When Hold type evaluation begins
Then The system proceeds to check border holds, destination holds, FDA holds, and piece count holds
R-GCX016E-cbl-03102 Evaluate Border Hold
Validation Rules
📊 Business Logic Narrative
When the process 'Evaluate Border Hold' is invoked, and assuming that a cargo record is being evaluated for hold conditions, when border hold status is checked, the desired outcome is that the system determines if border hold conditions apply to the cargo.
💻 Technical Criteria
Given A cargo record is being evaluated for hold conditions
When Border hold status is checked
Then The system determines if border hold conditions apply to the cargo
R-GCX016E-cbl-03103 Evaluate Destination Hold
Validation Rules
📊 Business Logic Narrative
When the process 'Evaluate Destination Hold' is invoked, and assuming that a cargo record is being evaluated for hold conditions, when destination hold status is checked, the desired outcome is that the system determines if destination hold conditions apply to the cargo.
💻 Technical Criteria
Given A cargo record is being evaluated for hold conditions
When Destination hold status is checked
Then The system determines if destination hold conditions apply to the cargo
R-GCX016E-cbl-03104 Evaluate FDA Hold
Validation Rules
📊 Business Logic Narrative
When the process 'Evaluate FDA Hold' is invoked, and assuming that a cargo record is being evaluated for hold conditions, when fda hold status is checked, the desired outcome is that the system determines if fda hold conditions apply to the cargo.
💻 Technical Criteria
Given A cargo record is being evaluated for hold conditions
When FDA hold status is checked
Then The system determines if FDA hold conditions apply to the cargo
R-GCX016E-cbl-03105 Evaluate Piece Count Hold
Validation Rules
📊 Business Logic Narrative
When the process 'Evaluate Piece Count Hold' is invoked, and assuming that a cargo record is being evaluated for hold conditions, when piece count hold status is checked, the desired outcome is that the system determines if piece count hold conditions apply based on quantity validation.
💻 Technical Criteria
Given A cargo record is being evaluated for hold conditions
When Piece count hold status is checked
Then The system determines if piece count hold conditions apply based on quantity validation
R-GCX016E-cbl-03106 Determine Individual Record Release Status
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Individual Record Release Status' is invoked, and assuming that all hold conditions have been evaluated for a cargo record, when the final release status is determined, the desired outcome is that the cargo record is classified as either released or held based on the evaluation results.
💻 Technical Criteria
Given All hold conditions have been evaluated for a cargo record
When The final release status is determined
Then The cargo record is classified as either released or held based on the evaluation results
R-GCX016E-cbl-03107 Store Record Status in Verification Array
Process Rules
📊 Business Logic Narrative
When the process 'Store Record Status in Verification Array' is invoked, and assuming that an individual cargo record's release status has been determined, when the status is stored in the verification array, the desired outcome is that the record's release status is added to the array for later comparison with other related records.
💻 Technical Criteria
Given An individual cargo record's release status has been determined
When The status is stored in the verification array
Then The record's release status is added to the array for later comparison with other related records
R-GCX016E-cbl-03108 Compare All Record Statuses
Process Rules
📊 Business Logic Narrative
When the process 'Compare All Record Statuses' is invoked, and assuming that all related cargo records have been processed and their statuses stored, when status comparison is performed, the desired outcome is that the system compares all record statuses to determine if they are consistent.
💻 Technical Criteria
Given All related cargo records have been processed and their statuses stored
When Status comparison is performed
Then The system compares all record statuses to determine if they are consistent
R-GCX016E-cbl-03109 All Records Have Consistent Release Status?
Decision Rules
📊 Business Logic Narrative
When the process 'All Records Have Consistent Release Status?' is invoked, and assuming that all related cargo record statuses have been compared, when consistency verification is performed, the desired outcome is that if all records have consistent release status, generate comprehensive release notification, otherwise create status mismatch warning.
💻 Technical Criteria
Given All related cargo record statuses have been compared
When Consistency verification is performed
Then If all records have consistent release status, generate comprehensive release notification, otherwise create status mismatch warning
R-GCX016E-cbl-03110 Generate Comprehensive Release Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Comprehensive Release Notification' is invoked, and assuming that all related cargo records have consistent release status, when comprehensive release notification is generated, the desired outcome is that a notification is created confirming the consistent release status across all related records.
💻 Technical Criteria
Given All related cargo records have consistent release status
When Comprehensive release notification is generated
Then A notification is created confirming the consistent release status across all related records
R-GCX016E-cbl-03111 Create Release Status Mismatch Warning
Action Rules
📊 Business Logic Narrative
When the process 'Create Release Status Mismatch Warning' is invoked, and assuming that related cargo records have inconsistent release statuses, when status mismatch warning is created, the desired outcome is that a warning is generated indicating the inconsistency in release statuses among related records.
💻 Technical Criteria
Given Related cargo records have inconsistent release statuses
When Status mismatch warning is created
Then A warning is generated indicating the inconsistency in release statuses among related records
R-GCX016E-cbl-03112 Update Multi-Cargo Release Flag
Process Rules
📊 Business Logic Narrative
When the process 'Update Multi-Cargo Release Flag' is invoked, and assuming that multi-cargo status verification has been completed, when the multi-cargo release flag is updated, the desired outcome is that the flag is set to reflect the overall release status of all related cargo records.
💻 Technical Criteria
Given Multi-cargo status verification has been completed
When The multi-cargo release flag is updated
Then The flag is set to reflect the overall release status of all related cargo records
R-GCX016E-cbl-03113 Log Status Verification Results
Process Rules
📊 Business Logic Narrative
When the process 'Log Status Verification Results' is invoked, and assuming that multi-cargo status verification has been completed, when results logging is performed, the desired outcome is that the verification results, including any warnings or notifications, are logged for audit purposes.
💻 Technical Criteria
Given Multi-cargo status verification has been completed
When Results logging is performed
Then The verification results, including any warnings or notifications, are logged for audit purposes
R-GCX016E-cbl-03114 End Multi-Cargo Status Verification
Process Rules
📊 Business Logic Narrative
When the process 'End Multi-Cargo Status Verification' is invoked, and assuming that all multi-cargo status verification activities have been completed, when the verification process ends, the desired outcome is that the process is completed and control is returned to the calling procedure.
💻 Technical Criteria
Given All multi-cargo status verification activities have been completed
When The verification process ends
Then The process is completed and control is returned to the calling procedure
R-GCX016E-cbl-03301 Is Cargo Record Deleted?
Validation Rules
📊 Business Logic Narrative
When the process 'Is Cargo Record Deleted?' is invoked, and assuming that a cargo record is being evaluated for status analysis, when the cargo record has a deleted status indicator, the desired outcome is that the cargo record is excluded from further processing and analysis.
💻 Technical Criteria
Given A cargo record is being evaluated for status analysis
When The cargo record has a deleted status indicator
Then The cargo record is excluded from further processing and analysis
R-GCX016E-cbl-03302 Check Manual Release Status
Decision Rules
📊 Business Logic Narrative
When the process 'Check Manual Release Status' is invoked, and assuming that a non-deleted cargo record is being analyzed, when the system checks the cargo's release status indicators, the desired outcome is that the manual release status is determined and recorded for subsequent processing.
💻 Technical Criteria
Given A non-deleted cargo record is being analyzed
When The system checks the cargo's release status indicators
Then The manual release status is determined and recorded for subsequent processing
R-GCX016E-cbl-03303 Set Manual Release Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Manual Release Flag' is invoked, and assuming that a cargo record has been identified as manually released, when the manual release detection process completes, the desired outcome is that the manual release flag is set for the cargo record.
💻 Technical Criteria
Given A cargo record has been identified as manually released
When The manual release detection process completes
Then The manual release flag is set for the cargo record
R-GCX016E-cbl-03304 Border Hold Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Border Hold Present?' is invoked, and assuming that a cargo record is undergoing hold type evaluation, when the system checks for border hold indicators in the cargo status, the desired outcome is that the presence or absence of border hold is determined.
💻 Technical Criteria
Given A cargo record is undergoing hold type evaluation
When The system checks for border hold indicators in the cargo status
Then The presence or absence of border hold is determined
R-GCX016E-cbl-03305 Set Border Hold Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Border Hold Flag' is invoked, and assuming that a cargo record has been identified with border hold conditions, when the border hold evaluation completes, the desired outcome is that the border hold flag is set for the cargo record.
💻 Technical Criteria
Given A cargo record has been identified with border hold conditions
When The border hold evaluation completes
Then The border hold flag is set for the cargo record
R-GCX016E-cbl-03306 Destination Hold Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Destination Hold Present?' is invoked, and assuming that a cargo record is being evaluated for hold types, when the system checks for destination hold indicators in the cargo status, the desired outcome is that the presence or absence of destination hold is determined.
💻 Technical Criteria
Given A cargo record is being evaluated for hold types
When The system checks for destination hold indicators in the cargo status
Then The presence or absence of destination hold is determined
R-GCX016E-cbl-03307 Set Destination Hold Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Destination Hold Flag' is invoked, and assuming that a cargo record has been identified with destination hold conditions, when the destination hold evaluation completes, the desired outcome is that the destination hold flag is set for the cargo record.
💻 Technical Criteria
Given A cargo record has been identified with destination hold conditions
When The destination hold evaluation completes
Then The destination hold flag is set for the cargo record
R-GCX016E-cbl-03308 FDA Hold Present?
Policy Rules
📊 Business Logic Narrative
When the process 'FDA Hold Present?' is invoked, and assuming that a cargo record is being evaluated for regulatory hold types, when the system checks for fda hold indicators in the cargo status, the desired outcome is that the presence or absence of fda hold is determined.
💻 Technical Criteria
Given A cargo record is being evaluated for regulatory hold types
When The system checks for FDA hold indicators in the cargo status
Then The presence or absence of FDA hold is determined
R-GCX016E-cbl-03309 Set FDA Hold Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set FDA Hold Flag' is invoked, and assuming that a cargo record has been identified with fda hold conditions, when the fda hold evaluation completes, the desired outcome is that the fda hold flag is set for the cargo record.
💻 Technical Criteria
Given A cargo record has been identified with FDA hold conditions
When The FDA hold evaluation completes
Then The FDA hold flag is set for the cargo record
R-GCX016E-cbl-03310 Piece Count Hold Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Piece Count Hold Present?' is invoked, and assuming that a cargo record is being evaluated for quantity-related hold types, when the system checks for piece count hold indicators in the cargo status, the desired outcome is that the presence or absence of piece count hold is determined.
💻 Technical Criteria
Given A cargo record is being evaluated for quantity-related hold types
When The system checks for piece count hold indicators in the cargo status
Then The presence or absence of piece count hold is determined
R-GCX016E-cbl-03311 Validate Piece Count
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Piece Count' is invoked, and assuming that a cargo record has piece count hold indicators, when the system validates the piece count against expected quantities, the desired outcome is that the piece count validation result is determined.
💻 Technical Criteria
Given A cargo record has piece count hold indicators
When The system validates the piece count against expected quantities
Then The piece count validation result is determined
R-GCX016E-cbl-03312 Set Piece Count Hold Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Piece Count Hold Flag' is invoked, and assuming that a cargo record has invalid piece count validation results, when the piece count validation process completes, the desired outcome is that the piece count hold flag is set for the cargo record.
💻 Technical Criteria
Given A cargo record has invalid piece count validation results
When The piece count validation process completes
Then The piece count hold flag is set for the cargo record
R-GCX016E-cbl-03313 All Holds Cleared?
Decision Rules
📊 Business Logic Narrative
When the process 'All Holds Cleared?' is invoked, and assuming that a cargo record has completed hold type evaluation, when the system checks all hold flags (border, destination, fda, piece count), the desired outcome is that the overall hold clearance status is determined.
💻 Technical Criteria
Given A cargo record has completed hold type evaluation
When The system checks all hold flags (border, destination, FDA, piece count)
Then The overall hold clearance status is determined
R-GCX016E-cbl-03314 Set Release Eligible Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Release Eligible Flag' is invoked, and assuming that a cargo record has all hold conditions cleared, when the release eligibility evaluation completes, the desired outcome is that the release eligible flag is set for the cargo record.
💻 Technical Criteria
Given A cargo record has all hold conditions cleared
When The release eligibility evaluation completes
Then The release eligible flag is set for the cargo record
R-GCX016E-cbl-03315 Set Hold Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Hold Status Flag' is invoked, and assuming that a cargo record has one or more active hold conditions, when the release eligibility evaluation completes, the desired outcome is that the hold status flag is set for the cargo record.
💻 Technical Criteria
Given A cargo record has one or more active hold conditions
When The release eligibility evaluation completes
Then The hold status flag is set for the cargo record
R-GCX016E-cbl-03316 Update Cargo Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status Flags' is invoked, and assuming that individual cargo record analysis has completed with all flags determined, when the system updates the cargo record status information, the desired outcome is that all status flags are updated to reflect the current cargo state.
💻 Technical Criteria
Given Individual cargo record analysis has completed with all flags determined
When The system updates the cargo record status information
Then All status flags are updated to reflect the current cargo state
R-GCX016E-cbl-03432 Initialize Hold Status Flags
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Hold Status Flags' is invoked, and assuming that a cargo record requires hold status evaluation, when the hold type evaluation process begins, the desired outcome is that all hold status flags (border hold, destination hold, fda hold, piece count hold) are set to false and overall hold status is cleared.
💻 Technical Criteria
Given A cargo record requires hold status evaluation
When The hold type evaluation process begins
Then All hold status flags (border hold, destination hold, FDA hold, piece count hold) are set to false and overall hold status is cleared
R-GCX016E-cbl-03433 Check Border Hold Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check Border Hold Status' is invoked, and assuming that a cargo has a status array with disposition codes, when the system checks for border hold status, the desired outcome is that the system searches the status array for border hold disposition codes and identifies if border hold is active.
💻 Technical Criteria
Given A cargo has a status array with disposition codes
When The system checks for border hold status
Then The system searches the status array for border hold disposition codes and identifies if border hold is active
R-GCX016E-cbl-03434 Border Hold Active?
Decision Rules
📊 Business Logic Narrative
When the process 'Border Hold Active?' is invoked, and assuming that the system has checked cargo status array for border hold codes, when border hold disposition codes are found in the status array, the desired outcome is that the border hold active flag is set to true, otherwise it remains false.
💻 Technical Criteria
Given The system has checked cargo status array for border hold codes
When Border hold disposition codes are found in the status array
Then The border hold active flag is set to true, otherwise it remains false
R-GCX016E-cbl-03435 Set Border Hold Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Border Hold Flag' is invoked, and assuming that border hold status has been determined to be active, when the system processes the border hold determination, the desired outcome is that the border hold flag is set to true to indicate cargo is held at border.
💻 Technical Criteria
Given Border hold status has been determined to be active
When The system processes the border hold determination
Then The border hold flag is set to true to indicate cargo is held at border
R-GCX016E-cbl-03436 Check Destination Hold Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check Destination Hold Status' is invoked, and assuming that a cargo has a status array with disposition codes, when the system checks for destination hold status, the desired outcome is that the system searches the status array for destination hold disposition codes and identifies if destination hold is active.
💻 Technical Criteria
Given A cargo has a status array with disposition codes
When The system checks for destination hold status
Then The system searches the status array for destination hold disposition codes and identifies if destination hold is active
R-GCX016E-cbl-03437 Destination Hold Active?
Decision Rules
📊 Business Logic Narrative
When the process 'Destination Hold Active?' is invoked, and assuming that the system has checked cargo status array for destination hold codes, when destination hold disposition codes are found in the status array, the desired outcome is that the destination hold active flag is set to true, otherwise it remains false.
💻 Technical Criteria
Given The system has checked cargo status array for destination hold codes
When Destination hold disposition codes are found in the status array
Then The destination hold active flag is set to true, otherwise it remains false
R-GCX016E-cbl-03438 Set Destination Hold Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Destination Hold Flag' is invoked, and assuming that destination hold status has been determined to be active, when the system processes the destination hold determination, the desired outcome is that the destination hold flag is set to true to indicate cargo is held at destination.
💻 Technical Criteria
Given Destination hold status has been determined to be active
When The system processes the destination hold determination
Then The destination hold flag is set to true to indicate cargo is held at destination
R-GCX016E-cbl-03439 Check FDA Hold Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check FDA Hold Status' is invoked, and assuming that a cargo has a status array with disposition codes, when the system checks for fda hold status, the desired outcome is that the system searches the status array for fda hold disposition codes and identifies if fda hold is active.
💻 Technical Criteria
Given A cargo has a status array with disposition codes
When The system checks for FDA hold status
Then The system searches the status array for FDA hold disposition codes and identifies if FDA hold is active
R-GCX016E-cbl-03440 FDA Hold Active?
Decision Rules
📊 Business Logic Narrative
When the process 'FDA Hold Active?' is invoked, and assuming that the system has checked cargo status array for fda hold codes, when fda hold disposition codes are found in the status array, the desired outcome is that the fda hold active flag is set to true, otherwise it remains false.
💻 Technical Criteria
Given The system has checked cargo status array for FDA hold codes
When FDA hold disposition codes are found in the status array
Then The FDA hold active flag is set to true, otherwise it remains false
R-GCX016E-cbl-03441 Set FDA Hold Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set FDA Hold Flag' is invoked, and assuming that fda hold status has been determined to be active, when the system processes the fda hold determination, the desired outcome is that the fda hold flag is set to true to indicate cargo is held by fda.
💻 Technical Criteria
Given FDA hold status has been determined to be active
When The system processes the FDA hold determination
Then The FDA hold flag is set to true to indicate cargo is held by FDA
R-GCX016E-cbl-03442 Check Piece Count Hold Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check Piece Count Hold Status' is invoked, and assuming that a cargo has a status array with disposition codes and quantity information, when the system checks for piece count hold status, the desired outcome is that the system evaluates release quantities against total quantities to identify if piece count hold is active.
💻 Technical Criteria
Given A cargo has a status array with disposition codes and quantity information
When The system checks for piece count hold status
Then The system evaluates release quantities against total quantities to identify if piece count hold is active
R-GCX016E-cbl-03443 Piece Count Hold Active?
Decision Rules
📊 Business Logic Narrative
When the process 'Piece Count Hold Active?' is invoked, and assuming that the system has checked cargo quantities for piece count hold conditions, when released quantity is less than total quantity or partial release conditions exist, the desired outcome is that the piece count hold active flag is set to true, otherwise it remains false.
💻 Technical Criteria
Given The system has checked cargo quantities for piece count hold conditions
When Released quantity is less than total quantity or partial release conditions exist
Then The piece count hold active flag is set to true, otherwise it remains false
R-GCX016E-cbl-03444 Set Piece Count Hold Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Piece Count Hold Flag' is invoked, and assuming that piece count hold status has been determined to be active, when the system processes the piece count hold determination, the desired outcome is that the piece count hold flag is set to true to indicate cargo has quantity-related holds.
💻 Technical Criteria
Given Piece count hold status has been determined to be active
When The system processes the piece count hold determination
Then The piece count hold flag is set to true to indicate cargo has quantity-related holds
R-GCX016E-cbl-03445 Evaluate Combined Hold Status
Process Rules
📊 Business Logic Narrative
When the process 'Evaluate Combined Hold Status' is invoked, and assuming that all individual hold type flags have been evaluated (border, destination, fda, piece count), when the system evaluates the combined hold status, the desired outcome is that the system analyzes all hold flags to determine the overall hold condition.
💻 Technical Criteria
Given All individual hold type flags have been evaluated (border, destination, FDA, piece count)
When The system evaluates the combined hold status
Then The system analyzes all hold flags to determine the overall hold condition
R-GCX016E-cbl-03446 Any Hold Type Active?
Decision Rules
📊 Business Logic Narrative
When the process 'Any Hold Type Active?' is invoked, and assuming that all hold type flags have been set (border hold, destination hold, fda hold, piece count hold), when the system checks if any hold type is active, the desired outcome is that if any hold flag is true, then overall hold status is active, otherwise cargo is not held.
💻 Technical Criteria
Given All hold type flags have been set (border hold, destination hold, FDA hold, piece count hold)
When The system checks if any hold type is active
Then If any hold flag is true, then overall hold status is active, otherwise cargo is not held
R-GCX016E-cbl-03447 Set Overall Hold Status
Action Rules
📊 Business Logic Narrative
When the process 'Set Overall Hold Status' is invoked, and assuming that at least one hold type flag is active (border, destination, fda, or piece count), when the system processes the overall hold determination, the desired outcome is that the overall hold status is set to indicate cargo is held with appropriate hold type designation.
💻 Technical Criteria
Given At least one hold type flag is active (border, destination, FDA, or piece count)
When The system processes the overall hold determination
Then The overall hold status is set to indicate cargo is held with appropriate hold type designation
R-GCX016E-cbl-03448 Set Release Status
Action Rules
📊 Business Logic Narrative
When the process 'Set Release Status' is invoked, and assuming that no hold type flags are active (border, destination, fda, and piece count are all false), when the system processes the overall hold determination, the desired outcome is that the release status is set to indicate cargo is released and available for processing.
💻 Technical Criteria
Given No hold type flags are active (border, destination, FDA, and piece count are all false)
When The system processes the overall hold determination
Then The release status is set to indicate cargo is released and available for processing
R-GCX016E-cbl-03449 Apply Hold Validation Rules
Policy Rules
📊 Business Logic Narrative
When the process 'Apply Hold Validation Rules' is invoked, and assuming that hold status has been determined for the cargo, when the system applies hold validation rules, the desired outcome is that the system validates hold status against business rules and regulatory requirements to ensure compliance.
💻 Technical Criteria
Given Hold status has been determined for the cargo
When The system applies hold validation rules
Then The system validates hold status against business rules and regulatory requirements to ensure compliance
R-GCX016E-cbl-03450 Update Cargo Hold Status
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Hold Status' is invoked, and assuming that hold status has been determined and validated for the cargo, when the system updates the cargo hold status, the desired outcome is that the cargo record is updated with the final hold status and all related status fields are set appropriately.
💻 Technical Criteria
Given Hold status has been determined and validated for the cargo
When The system updates the cargo hold status
Then The cargo record is updated with the final hold status and all related status fields are set appropriately
R-GCX016E-cbl-03551 Retrieve Current Hold Status Array
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Hold Status Array' is invoked, and assuming that a cargo record exists with associated status information, when the hold validation process is initiated, the desired outcome is that the system retrieves the current s09 status array containing all active disposition codes and hold statuses for the cargo.
💻 Technical Criteria
Given A cargo record exists with associated status information
When The hold validation process is initiated
Then The system retrieves the current S09 status array containing all active disposition codes and hold statuses for the cargo
R-GCX016E-cbl-03552 Check for Multiple Hold Types
Validation Rules
📊 Business Logic Narrative
When the process 'Check for Multiple Hold Types' is invoked, and assuming that a cargo status array has been retrieved, when the system processes the status array for hold validation, the desired outcome is that the system identifies and flags the presence of multiple concurrent hold types.
💻 Technical Criteria
Given A cargo status array has been retrieved
When The system processes the status array for hold validation
Then The system identifies and flags the presence of multiple concurrent hold types
R-GCX016E-cbl-03553 Border Hold Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Border Hold Present?' is invoked, and assuming that a cargo status array contains disposition codes, when the system evaluates hold types, the desired outcome is that the system returns true if a border hold disposition code is found, false otherwise.
💻 Technical Criteria
Given A cargo status array contains disposition codes
When The system evaluates hold types
Then The system returns true if a border hold disposition code is found, false otherwise
R-GCX016E-cbl-03554 Destination Hold Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Destination Hold Present?' is invoked, and assuming that a cargo status array contains disposition codes, when the system evaluates hold types, the desired outcome is that the system returns true if a destination hold disposition code is found, false otherwise.
💻 Technical Criteria
Given A cargo status array contains disposition codes
When The system evaluates hold types
Then The system returns true if a destination hold disposition code is found, false otherwise
R-GCX016E-cbl-03555 FDA Hold Present?
Decision Rules
📊 Business Logic Narrative
When the process 'FDA Hold Present?' is invoked, and assuming that a cargo status array contains disposition codes, when the system evaluates hold types, the desired outcome is that the system returns true if an fda hold disposition code is found, false otherwise.
💻 Technical Criteria
Given A cargo status array contains disposition codes
When The system evaluates hold types
Then The system returns true if an FDA hold disposition code is found, false otherwise
R-GCX016E-cbl-03556 Piece Count Hold Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Piece Count Hold Present?' is invoked, and assuming that a cargo status array contains disposition codes, when the system evaluates hold types, the desired outcome is that the system returns true if a piece count hold disposition code is found, false otherwise.
💻 Technical Criteria
Given A cargo status array contains disposition codes
When The system evaluates hold types
Then The system returns true if a piece count hold disposition code is found, false otherwise
R-GCX016E-cbl-03557 Manual Release Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Manual Release Present?' is invoked, and assuming that a cargo status array contains disposition codes, when the system evaluates for manual release overrides, the desired outcome is that the system returns true if a manual release disposition code is found, false otherwise.
💻 Technical Criteria
Given A cargo status array contains disposition codes
When The system evaluates for manual release overrides
Then The system returns true if a manual release disposition code is found, false otherwise
R-GCX016E-cbl-03558 Evaluate Hold Combination Rules
Policy Rules
📊 Business Logic Narrative
When the process 'Evaluate Hold Combination Rules' is invoked, and assuming that multiple hold types have been identified in the cargo status, when the system validates hold combinations, the desired outcome is that the system determines if the combination of holds is valid based on business rules and regulatory requirements.
💻 Technical Criteria
Given Multiple hold types have been identified in the cargo status
When The system validates hold combinations
Then The system determines if the combination of holds is valid based on business rules and regulatory requirements
R-GCX016E-cbl-03560 Apply Regulatory Priority Rules
Policy Rules
📊 Business Logic Narrative
When the process 'Apply Regulatory Priority Rules' is invoked, and assuming that multiple valid holds are present on a cargo, when the system applies regulatory priority rules, the desired outcome is that the system determines the priority order of holds based on regulatory requirements.
💻 Technical Criteria
Given Multiple valid holds are present on a cargo
When The system applies regulatory priority rules
Then The system determines the priority order of holds based on regulatory requirements
R-GCX016E-cbl-03563 Piece Count Hold Active?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Piece Count Hold Active?', assuming that piece count hold is present and higher priority holds do not apply, when the system evaluates remaining hold types, the desired outcome is that the system returns true if piece count hold is active, false otherwise.
💻 Technical Criteria
EXCLUDING Piece count hold is present and higher priority holds do not apply
When The system evaluates remaining hold types
Then The system returns true if piece count hold is active, false otherwise
R-GCX016E-cbl-03564 Set Final Hold Status - FDA Priority
Action Rules
📊 Business Logic Narrative
When the process 'Set Final Hold Status - FDA Priority' is invoked, and assuming that fda hold has been determined to take priority, when the system sets the final hold status, the desired outcome is that the system sets the cargo status to fda hold and updates all related status flags.
💻 Technical Criteria
Given FDA hold has been determined to take priority
When The system sets the final hold status
Then The system sets the cargo status to FDA hold and updates all related status flags
R-GCX016E-cbl-03565 Set Final Hold Status - Border Priority
Action Rules
📊 Business Logic Narrative
When the process 'Set Final Hold Status - Border Priority' is invoked, and assuming that border hold has been determined to take priority, when the system sets the final hold status, the desired outcome is that the system sets the cargo status to border hold and updates all related status flags.
💻 Technical Criteria
Given Border hold has been determined to take priority
When The system sets the final hold status
Then The system sets the cargo status to border hold and updates all related status flags
R-GCX016E-cbl-03566 Set Final Hold Status - Destination Hold
Action Rules
📊 Business Logic Narrative
When the process 'Set Final Hold Status - Destination Hold' is invoked, and assuming that destination hold is present and no higher priority holds apply, when the system sets the final hold status, the desired outcome is that the system sets the cargo status to destination hold and updates all related status flags.
💻 Technical Criteria
Given Destination hold is present and no higher priority holds apply
When The system sets the final hold status
Then The system sets the cargo status to destination hold and updates all related status flags
R-GCX016E-cbl-03567 Set Final Hold Status - Piece Count Hold
Action Rules
📊 Business Logic Narrative
When the process 'Set Final Hold Status - Piece Count Hold' is invoked, and assuming that piece count hold is active and no higher priority holds apply, when the system sets the final hold status, the desired outcome is that the system sets the cargo status to piece count hold and updates all related status flags.
💻 Technical Criteria
Given Piece count hold is active and no higher priority holds apply
When The system sets the final hold status
Then The system sets the cargo status to piece count hold and updates all related status flags
R-GCX016E-cbl-03568 Set Final Hold Status - Manual Release Override
Action Rules
📊 Business Logic Narrative
When the process 'Set Final Hold Status - Manual Release Override' is invoked, and assuming that manual release disposition code is present, when the system processes manual release override, the desired outcome is that the system overrides system holds and sets the cargo status to released with manual release flag.
💻 Technical Criteria
Given Manual release disposition code is present
When The system processes manual release override
Then The system overrides system holds and sets the cargo status to released with manual release flag
R-GCX016E-cbl-03573 Update Hold Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Update Hold Status Flags' is invoked, and assuming that final hold status has been validated, when the system updates status flags, the desired outcome is that the system updates all hold status flags, indicators, and related cargo status information.
💻 Technical Criteria
Given Final hold status has been validated
When The system updates status flags
Then The system updates all hold status flags, indicators, and related cargo status information
R-GCX016E-cbl-02385 More Cargo Records?
Decision Rules
📊 Business Logic Narrative
When the process 'More Cargo Records?' is invoked, and assuming that a collection of cargo records has been retrieved for processing, when the system evaluates the collection status, the desired outcome is that the system returns true if more records exist to process, false if all records have been processed.
💻 Technical Criteria
Given A collection of cargo records has been retrieved for processing
When The system evaluates the collection status
Then The system returns true if more records exist to process, false if all records have been processed
R-GCX016E-cbl-02386 Analyze Individual Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Analyze Individual Cargo Record' is invoked, and assuming that an individual cargo record from the collection, when the system processes the cargo record, the desired outcome is that the cargo record's status, hold conditions, and release eligibility are evaluated.
💻 Technical Criteria
Given An individual cargo record from the collection
When The system processes the cargo record
Then The cargo record's status, hold conditions, and release eligibility are evaluated
R-GCX016E-cbl-02387 Check Hold Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check Hold Status' is invoked, and assuming that a cargo record under analysis, when the system checks for hold conditions, the desired outcome is that the system identifies any active holds including border holds, destination holds, fda holds, or other regulatory holds.
💻 Technical Criteria
Given A cargo record under analysis
When The system checks for hold conditions
Then The system identifies any active holds including border holds, destination holds, FDA holds, or other regulatory holds
R-GCX016E-cbl-02388 Hold Status Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Hold Status Found?' is invoked, and assuming that hold status check has been completed on a cargo record, when the system evaluates the hold check results, the desired outcome is that if any hold status is found, proceed to manual release check; if no holds found, proceed to release eligibility evaluation.
💻 Technical Criteria
Given Hold status check has been completed on a cargo record
When The system evaluates the hold check results
Then If any hold status is found, proceed to manual release check; if no holds found, proceed to release eligibility evaluation
R-GCX016E-cbl-02389 Check Manual Release Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check Manual Release Status' is invoked, and assuming that a cargo record with identified hold status, when the system checks for manual release authorization, the desired outcome is that the system determines if manual release disposition codes or authorizations have been applied to the cargo.
💻 Technical Criteria
Given A cargo record with identified hold status
When The system checks for manual release authorization
Then The system determines if manual release disposition codes or authorizations have been applied to the cargo
R-GCX016E-cbl-02390 Manual Release Applied?
Decision Rules
📊 Business Logic Narrative
When the process 'Manual Release Applied?' is invoked, and assuming that manual release status check has been completed, when the system evaluates manual release results, the desired outcome is that if manual release is applied, proceed to piece count hold check; if not applied, proceed to other hold type checks.
💻 Technical Criteria
Given Manual release status check has been completed
When The system evaluates manual release results
Then If manual release is applied, proceed to piece count hold check; if not applied, proceed to other hold type checks
R-GCX016E-cbl-02391 Check Piece Count Holds
Validation Rules
📊 Business Logic Narrative
When the process 'Check Piece Count Holds' is invoked, and assuming that a cargo record with manual release applied, when the system checks piece count status, the desired outcome is that the system identifies any piece count holds, partial release conditions, or quantity discrepancies.
💻 Technical Criteria
Given A cargo record with manual release applied
When The system checks piece count status
Then The system identifies any piece count holds, partial release conditions, or quantity discrepancies
R-GCX016E-cbl-02392 Piece Count Issues?
Decision Rules
📊 Business Logic Narrative
When the process 'Piece Count Issues?' is invoked, and assuming that piece count hold check has been completed, when the system evaluates piece count results, the desired outcome is that if piece count issues exist, proceed to other hold type checks; if no issues, proceed to release eligibility evaluation.
💻 Technical Criteria
Given Piece count hold check has been completed
When The system evaluates piece count results
Then If piece count issues exist, proceed to other hold type checks; if no issues, proceed to release eligibility evaluation
R-GCX016E-cbl-02393 Check Various Hold Types
Validation Rules
📊 Business Logic Narrative
When the process 'Check Various Hold Types' is invoked, and assuming that a cargo record requiring comprehensive hold analysis, when the system checks for various hold types, the desired outcome is that the system identifies examination holds, regulatory holds, security holds, or other specialized hold conditions.
💻 Technical Criteria
Given A cargo record requiring comprehensive hold analysis
When The system checks for various hold types
Then The system identifies examination holds, regulatory holds, security holds, or other specialized hold conditions
R-GCX016E-cbl-02395 Evaluate Release Eligibility
Decision Rules
📊 Business Logic Narrative
When the process 'Evaluate Release Eligibility' is invoked, and assuming that a cargo record with completed hold status analysis, when the system evaluates overall release eligibility, the desired outcome is that the cargo is marked as release-eligible if no blocking holds exist, or marked as held if blocking conditions remain.
💻 Technical Criteria
Given A cargo record with completed hold status analysis
When The system evaluates overall release eligibility
Then The cargo is marked as release-eligible if no blocking holds exist, or marked as held if blocking conditions remain
R-GCX016E-cbl-02399 Include Disposition Code Information
Process Rules
📊 Business Logic Narrative
When the process 'Include Disposition Code Information' is invoked, and assuming that a release message with equipment details, when the system includes disposition code information, the desired outcome is that the message contains relevant disposition codes, processing actions, and regulatory compliance information.
💻 Technical Criteria
Given A release message with equipment details
When The system includes disposition code information
Then The message contains relevant disposition codes, processing actions, and regulatory compliance information
R-GCX016E-cbl-02400 Add Quantity Impact Analysis
Computation Rules
📊 Business Logic Narrative
When the process 'Add Quantity Impact Analysis' is invoked, and assuming that a release message with disposition code information, when the system adds quantity impact analysis, the desired outcome is that the message shows released quantities, remaining quantities, and impact on total cargo counts.
💻 Technical Criteria
Given A release message with disposition code information
When The system adds quantity impact analysis
Then The message shows released quantities, remaining quantities, and impact on total cargo counts
R-GCX016E-cbl-02401 Send Release Notification to Recipients
Action Rules
📊 Business Logic Narrative
When the process 'Send Release Notification to Recipients' is invoked, and assuming that a complete release notification message, when the system sends the notification, the desired outcome is that the notification is delivered to brokers, freight forwarders, and other authorized recipients based on cargo ownership and processing requirements.
💻 Technical Criteria
Given A complete release notification message
When The system sends the notification
Then The notification is delivered to brokers, freight forwarders, and other authorized recipients based on cargo ownership and processing requirements
R-GCX016E-cbl-02402 Update Cargo Status Arrays
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status Arrays' is invoked, and assuming that release notification has been sent successfully, when the system updates cargo status arrays, the desired outcome is that all cargo records in the group have their status arrays updated to reflect released status and notification completion.
💻 Technical Criteria
Given Release notification has been sent successfully
When The system updates cargo status arrays
Then All cargo records in the group have their status arrays updated to reflect released status and notification completion
R-GCX016E-cbl-02403 Log Release Verification Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Release Verification Action' is invoked, and assuming that cargo status arrays have been updated, when the system logs the release verification action, the desired outcome is that an audit record is created with timestamp, cargo details, release status, and notification recipients for compliance tracking.
💻 Technical Criteria
Given Cargo status arrays have been updated
When The system logs the release verification action
Then An audit record is created with timestamp, cargo details, release status, and notification recipients for compliance tracking
R-GCX016E-cbl-02404 Check Manual Release Flag
Decision Rules
📊 Business Logic Narrative
When the process 'Check Manual Release Flag' is invoked, and assuming that a cargo record with status array containing disposition codes, when the system analyzes the cargo status for manual release indicators, the desired outcome is that the manual release flag is set if manual release disposition codes are present in the status array.
💻 Technical Criteria
Given A cargo record with status array containing disposition codes
When The system analyzes the cargo status for manual release indicators
Then The manual release flag is set if manual release disposition codes are present in the status array
R-GCX016E-cbl-02405 Set Manual Release Status
Action Rules
📊 Business Logic Narrative
When the process 'Set Manual Release Status' is invoked, and assuming that a cargo with manual release flag set to true, when the system processes the cargo status determination, the desired outcome is that the cargo status is set to 'relsd' (released) and manual release processing is applied.
💻 Technical Criteria
Given A cargo with manual release flag set to true
When The system processes the cargo status determination
Then The cargo status is set to 'RELSD' (Released) and manual release processing is applied
R-GCX016E-cbl-02406 Process Border Hold Status
Decision Rules
📊 Business Logic Narrative
When the process 'Process Border Hold Status' is invoked, and assuming that a cargo record with status array containing disposition codes, when the system checks for border hold indicators in the status array, the desired outcome is that the border hold flag is set if border hold disposition codes are present.
💻 Technical Criteria
Given A cargo record with status array containing disposition codes
When The system checks for border hold indicators in the status array
Then The border hold flag is set if border hold disposition codes are present
R-GCX016E-cbl-02407 Process Destination Hold Status
Decision Rules
📊 Business Logic Narrative
When the process 'Process Destination Hold Status' is invoked, and assuming that a cargo record with status array containing disposition codes, when the system checks for destination hold indicators in the status array, the desired outcome is that the destination hold flag is set if destination hold disposition codes are present.
💻 Technical Criteria
Given A cargo record with status array containing disposition codes
When The system checks for destination hold indicators in the status array
Then The destination hold flag is set if destination hold disposition codes are present
R-GCX016E-cbl-02408 Process FDA Hold Status
Decision Rules
📊 Business Logic Narrative
When the process 'Process FDA Hold Status' is invoked, and assuming that a cargo record with status array containing disposition codes, when the system checks for fda hold indicators in the status array, the desired outcome is that the fda hold flag is set and cargo status is set to 'holdfda' if fda hold disposition codes are present.
💻 Technical Criteria
Given A cargo record with status array containing disposition codes
When The system checks for FDA hold indicators in the status array
Then The FDA hold flag is set and cargo status is set to 'HOLDFDA' if FDA hold disposition codes are present
R-GCX016E-cbl-02409 Process Piece Count Hold Status
Decision Rules
📊 Business Logic Narrative
When the process 'Process Piece Count Hold Status' is invoked, and assuming that a cargo record with status array containing disposition codes, when the system checks for piece count hold indicators in the status array, the desired outcome is that the piece count hold flag is set if piece count hold disposition codes are present.
💻 Technical Criteria
Given A cargo record with status array containing disposition codes
When The system checks for piece count hold indicators in the status array
Then The piece count hold flag is set if piece count hold disposition codes are present
R-GCX016E-cbl-02410 Evaluate Release Quantities
Computation Rules
📊 Business Logic Narrative
When the process 'Evaluate Release Quantities' is invoked, and assuming that a cargo record with total quantity and released quantity values, when the system evaluates the release quantities for completeness, the desired outcome is that the system determines if the cargo is fully released, partially released, or not released based on quantity comparison.
💻 Technical Criteria
Given A cargo record with total quantity and released quantity values
When The system evaluates the release quantities for completeness
Then The system determines if the cargo is fully released, partially released, or not released based on quantity comparison
R-GCX016E-cbl-02411 Set Full Release Eligible
Decision Rules
📊 Business Logic Narrative
When the process 'Set Full Release Eligible' is invoked, and assuming that a cargo with released quantity equal to total quantity, when the system evaluates release eligibility, the desired outcome is that the cargo is marked as fully released and eligible for complete release processing.
💻 Technical Criteria
Given A cargo with released quantity equal to total quantity
When The system evaluates release eligibility
Then The cargo is marked as fully released and eligible for complete release processing
R-GCX016E-cbl-02412 Set Partial Release Status
Action Rules
📊 Business Logic Narrative
When the process 'Set Partial Release Status' is invoked, and assuming that a cargo with released quantity less than total quantity, when the system evaluates release status, the desired outcome is that the cargo is marked with partial release status and appropriate hold status is maintained.
💻 Technical Criteria
Given A cargo with released quantity less than total quantity
When The system evaluates release status
Then The cargo is marked with partial release status and appropriate hold status is maintained
R-GCX016E-cbl-02413 Determine Highest Priority Hold
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Highest Priority Hold' is invoked, and assuming that a cargo with multiple active hold conditions (border, destination, fda, piece count), when the system evaluates hold priority hierarchy, the desired outcome is that the highest priority hold status is determined based on predefined hold precedence rules.
💻 Technical Criteria
Given A cargo with multiple active hold conditions (border, destination, FDA, piece count)
When The system evaluates hold priority hierarchy
Then The highest priority hold status is determined based on predefined hold precedence rules
R-GCX016E-cbl-02414 Set Final Hold Status
Action Rules
📊 Business Logic Narrative
When the process 'Set Final Hold Status' is invoked, and assuming that a cargo with determined highest priority hold type, when the system sets the final cargo status, the desired outcome is that the cargo status is set to the appropriate hold status (hold, hold-b, hold-d, holdfda, holdpcs) based on the priority determination.
💻 Technical Criteria
Given A cargo with determined highest priority hold type
When The system sets the final cargo status
Then The cargo status is set to the appropriate hold status (HOLD, HOLD-B, HOLD-D, HOLDFDA, HOLDPCS) based on the priority determination
R-GCX016E-cbl-02415 Determine Release Eligibility
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Release Eligibility' is invoked, and assuming that a cargo with analyzed hold conditions and quantity comparisons, when the system performs final release eligibility assessment, the desired outcome is that the cargo is determined to be either release eligible or hold eligible based on the comprehensive analysis.
💻 Technical Criteria
Given A cargo with analyzed hold conditions and quantity comparisons
When The system performs final release eligibility assessment
Then The cargo is determined to be either release eligible or hold eligible based on the comprehensive analysis
R-GCX016E-cbl-02416 Set Cargo Release Status
Action Rules
📊 Business Logic Narrative
When the process 'Set Cargo Release Status' is invoked, and assuming that a cargo determined to be release eligible, when the system assigns final cargo status, the desired outcome is that the cargo status is set to 'relsd' (released) or 'holdpcs' (hold pieces) based on quantity analysis.
💻 Technical Criteria
Given A cargo determined to be release eligible
When The system assigns final cargo status
Then The cargo status is set to 'RELSD' (Released) or 'HOLDPCS' (Hold Pieces) based on quantity analysis
R-GCX016E-cbl-02417 Set Cargo Hold Status
Action Rules
📊 Business Logic Narrative
When the process 'Set Cargo Hold Status' is invoked, and assuming that a cargo determined to have active hold conditions, when the system assigns final cargo status, the desired outcome is that the cargo status is set to the appropriate hold status based on the type and priority of active holds.
💻 Technical Criteria
Given A cargo determined to have active hold conditions
When The system assigns final cargo status
Then The cargo status is set to the appropriate hold status based on the type and priority of active holds
R-GCX016E-cbl-02418 Update Cargo Status Flags
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status Flags' is invoked, and assuming that a cargo with final status determination completed, when the system updates cargo status flags, the desired outcome is that all relevant status flags (hold flags, release flags, processing flags) are updated to reflect the final cargo status.
💻 Technical Criteria
Given A cargo with final status determination completed
When The system updates cargo status flags
Then All relevant status flags (hold flags, release flags, processing flags) are updated to reflect the final cargo status
R-GCX016E-cbl-02420 Initialize New Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Initialize New Cargo Record' is invoked, and assuming that a new cargo record needs to be created for a foreign bill, when the initialization process begins, the desired outcome is that the system should clear all cargo record fields and set default values for status, dates, and counters.
💻 Technical Criteria
Given A new cargo record needs to be created for a foreign bill
When The initialization process begins
Then The system should clear all cargo record fields and set default values for status, dates, and counters
R-GCX016E-cbl-02421 Set Up Cargo Record with X4 Segment Data
Process Rules
📊 Business Logic Narrative
When the process 'Set Up Cargo Record with X4 Segment Data' is invoked, and assuming that a new cargo record is being created and x4 segment data is available, when the system processes the x4 segment information, the desired outcome is that the cargo record should be populated with disposition code, entry number, quantity, and related x4 segment data.
💻 Technical Criteria
Given A new cargo record is being created and X4 segment data is available
When The system processes the X4 segment information
Then The cargo record should be populated with disposition code, entry number, quantity, and related X4 segment data
R-GCX016E-cbl-02422 Set Up Cargo Record with N7 Segment Data
Process Rules
📊 Business Logic Narrative
When the process 'Set Up Cargo Record with N7 Segment Data' is invoked, and assuming that a new cargo record is being created and n7 segment data is available, when the system processes the n7 segment information, the desired outcome is that the cargo record should be populated with equipment initial, equipment number, and formatted car id information.
💻 Technical Criteria
Given A new cargo record is being created and N7 segment data is available
When The system processes the N7 segment information
Then The cargo record should be populated with equipment initial, equipment number, and formatted car ID information
R-GCX016E-cbl-02424 Extract SCAC Code
Validation Rules
📊 Business Logic Narrative
When the process 'Extract SCAC Code' is invoked, and assuming that manifest data is available for a new foreign cargo record, when the system processes the manifest information, the desired outcome is that the system should extract and validate the scac code from the manifest data.
💻 Technical Criteria
Given Manifest data is available for a new foreign cargo record
When The system processes the manifest information
Then The system should extract and validate the SCAC code from the manifest data
R-GCX016E-cbl-02425 Extract Transport Type
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Transport Type' is invoked, and assuming that manifest data is available for a new foreign cargo record, when the system processes the transportation information, the desired outcome is that the system should extract and set the appropriate transport type code.
💻 Technical Criteria
Given Manifest data is available for a new foreign cargo record
When The system processes the transportation information
Then The system should extract and set the appropriate transport type code
R-GCX016E-cbl-02426 Extract Country Code
Validation Rules
📊 Business Logic Narrative
When the process 'Extract Country Code' is invoked, and assuming that manifest data is available for a new foreign cargo record, when the system processes the origin information, the desired outcome is that the system should extract and validate the country code from the manifest data.
💻 Technical Criteria
Given Manifest data is available for a new foreign cargo record
When The system processes the origin information
Then The system should extract and validate the country code from the manifest data
R-GCX016E-cbl-02427 Extract Vessel Details
Process Rules
📊 Business Logic Narrative
When the process 'Extract Vessel Details' is invoked, and assuming that m10 segment data is available for a new foreign cargo record, when the system processes the vessel information, the desired outcome is that the system should extract vessel name, voyage number, and other vessel identification details.
💻 Technical Criteria
Given M10 segment data is available for a new foreign cargo record
When The system processes the vessel information
Then The system should extract vessel name, voyage number, and other vessel identification details
R-GCX016E-cbl-02428 Format Car ID for Database
Computation Rules
📊 Business Logic Narrative
When the process 'Format Car ID for Database' is invoked, and assuming that equipment initial and equipment number are available from n7 segment, when the system formats the car identification for database storage, the desired outcome is that the system should concatenate equipment initial and number with proper formatting and padding.
💻 Technical Criteria
Given Equipment initial and equipment number are available from N7 segment
When The system formats the car identification for database storage
Then The system should concatenate equipment initial and number with proper formatting and padding
R-GCX016E-cbl-02429 Validate Cargo Record Data
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Cargo Record Data' is invoked, and assuming that a new cargo record has been populated with segment data, when the system validates the cargo record before insertion, the desired outcome is that the system should verify all required fields are present and data formats are correct.
💻 Technical Criteria
Given A new cargo record has been populated with segment data
When The system validates the cargo record before insertion
Then The system should verify all required fields are present and data formats are correct
R-GCX016E-cbl-02430 Insert New Cargo Record into Database
Action Rules
📊 Business Logic Narrative
When the process 'Insert New Cargo Record into Database' is invoked, and assuming that a validated new cargo record is ready for insertion, when the system attempts to insert the record into the database, the desired outcome is that the system should successfully add the new cargo record to the database.
💻 Technical Criteria
Given A validated new cargo record is ready for insertion
When The system attempts to insert the record into the database
Then The system should successfully add the new cargo record to the database
R-GCX016E-cbl-02431 Database Insert Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'Database Insert Successful?' is invoked, and assuming that a new cargo record insertion has been attempted, when the database operation completes, the desired outcome is that the system should check the operation status and determine if the insertion was successful.
💻 Technical Criteria
Given A new cargo record insertion has been attempted
When The database operation completes
Then The system should check the operation status and determine if the insertion was successful
R-GCX016E-cbl-02432 Log Cargo Creation Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Cargo Creation Action' is invoked, and assuming that a new cargo record has been successfully inserted into the database, when the insertion operation completes successfully, the desired outcome is that the system should log the cargo creation action with relevant details and timestamps.
💻 Technical Criteria
Given A new cargo record has been successfully inserted into the database
When The insertion operation completes successfully
Then The system should log the cargo creation action with relevant details and timestamps
R-GCX016E-cbl-02433 Generate Error Message
Action Rules
📊 Business Logic Narrative
When the process 'Generate Error Message' is invoked, and assuming that a new cargo record insertion has failed, when the database operation returns an error status, the desired outcome is that the system should generate an error message indicating the insertion failure.
💻 Technical Criteria
Given A new cargo record insertion has failed
When The database operation returns an error status
Then The system should generate an error message indicating the insertion failure
R-GCX016E-cbl-02434 Continue Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue Processing' is invoked, and assuming that cargo record creation process has completed (either successfully or with error), when the creation process finishes, the desired outcome is that the system should continue with the next step in the message processing workflow.
💻 Technical Criteria
Given Cargo record creation process has completed (either successfully or with error)
When The creation process finishes
Then The system should continue with the next step in the message processing workflow
R-GCX016E-cbl-03115 Initialize New Cargo Record Structure
Process Rules
📊 Business Logic Narrative
When the process 'Initialize New Cargo Record Structure' is invoked, and assuming that a foreign cargo processing request is initiated, when the system begins foreign cargo record setup, the desired outcome is that a new cargo record structure is initialized with default values and prepared for data population.
💻 Technical Criteria
Given A foreign cargo processing request is initiated
When The system begins foreign cargo record setup
Then A new cargo record structure is initialized with default values and prepared for data population
R-GCX016E-cbl-03116 Extract Equipment Data from N7 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment Data from N7 Segment' is invoked, and assuming that an n7 segment containing equipment data is available, when the system processes the n7 segment for foreign cargo setup, the desired outcome is that equipment information including equipment initial and number are extracted and prepared for cargo record population.
💻 Technical Criteria
Given An N7 segment containing equipment data is available
When The system processes the N7 segment for foreign cargo setup
Then Equipment information including equipment initial and number are extracted and prepared for cargo record population
R-GCX016E-cbl-03117 Set Car ID and Equipment Type
Computation Rules
📊 Business Logic Narrative
When the process 'Set Car ID and Equipment Type' is invoked, and assuming that equipment data has been extracted from n7 segment, when the system processes equipment information for cargo record setup, the desired outcome is that car id is formatted by combining equipment initial and number, and equipment type is assigned to the cargo record.
💻 Technical Criteria
Given Equipment data has been extracted from N7 segment
When The system processes equipment information for cargo record setup
Then Car ID is formatted by combining equipment initial and number, and equipment type is assigned to the cargo record
R-GCX016E-cbl-03120 Set Disposition Code Information
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Disposition Code Information' is invoked, and assuming that disposition code data has been extracted from x4 segment, when the system processes disposition information for cargo setup, the desired outcome is that disposition code information is assigned to the cargo record for subsequent processing and status tracking.
💻 Technical Criteria
Given Disposition code data has been extracted from X4 segment
When The system processes disposition information for cargo setup
Then Disposition code information is assigned to the cargo record for subsequent processing and status tracking
R-GCX016E-cbl-03121 Build Foreign Manifest from M10 Segment
Process Rules
📊 Business Logic Narrative
When the process 'Build Foreign Manifest from M10 Segment' is invoked, and assuming that an m10 segment containing manifest data is available, when the system processes manifest information for foreign cargo setup, the desired outcome is that foreign manifest information is extracted and prepared for cargo record population including transport and vessel details.
💻 Technical Criteria
Given An M10 segment containing manifest data is available
When The system processes manifest information for foreign cargo setup
Then Foreign manifest information is extracted and prepared for cargo record population including transport and vessel details
R-GCX016E-cbl-03122 Extract SCAC Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract SCAC Code' is invoked, and assuming that manifest data from m10 segment is being processed, when the system extracts carrier identification information, the desired outcome is that scac code is extracted and assigned to identify the transportation carrier for the foreign cargo.
💻 Technical Criteria
Given Manifest data from M10 segment is being processed
When The system extracts carrier identification information
Then SCAC code is extracted and assigned to identify the transportation carrier for the foreign cargo
R-GCX016E-cbl-03123 Set Transport Type
Decision Rules
📊 Business Logic Narrative
When the process 'Set Transport Type' is invoked, and assuming that manifest information has been processed from m10 segment, when the system determines transport method for foreign cargo, the desired outcome is that transport type is assigned to the cargo record based on the mode of transportation indicated in the manifest.
💻 Technical Criteria
Given Manifest information has been processed from M10 segment
When The system determines transport method for foreign cargo
Then Transport type is assigned to the cargo record based on the mode of transportation indicated in the manifest
R-GCX016E-cbl-03124 Set Country Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Country Code' is invoked, and assuming that foreign cargo manifest information is being processed, when the system determines country of origin, the desired outcome is that country code is assigned to the cargo record to identify the foreign origin country.
💻 Technical Criteria
Given Foreign cargo manifest information is being processed
When The system determines country of origin
Then Country code is assigned to the cargo record to identify the foreign origin country
R-GCX016E-cbl-03125 Set Vessel/Train Details
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Vessel/Train Details' is invoked, and assuming that transport type and manifest information have been processed, when the system assigns conveyance details to foreign cargo, the desired outcome is that vessel or train identification details are assigned to the cargo record based on the transport method.
💻 Technical Criteria
Given Transport type and manifest information have been processed
When The system assigns conveyance details to foreign cargo
Then Vessel or train identification details are assigned to the cargo record based on the transport method
R-GCX016E-cbl-03126 Format Car ID for Database
Computation Rules
📊 Business Logic Narrative
When the process 'Format Car ID for Database' is invoked, and assuming that car id information has been assembled from equipment data, when the system prepares car id for database storage, the desired outcome is that car id is formatted according to database requirements for proper storage and future retrieval operations.
💻 Technical Criteria
Given Car ID information has been assembled from equipment data
When The system prepares car ID for database storage
Then Car ID is formatted according to database requirements for proper storage and future retrieval operations
R-GCX016E-cbl-03127 Insert New Cargo Record to Database
Action Rules
📊 Business Logic Narrative
When the process 'Insert New Cargo Record to Database' is invoked, and assuming that a complete foreign cargo record has been assembled with all required data, when the system stores the new cargo record, the desired outcome is that the foreign cargo record is inserted into the gcsusrt us cargo database for subsequent processing and status tracking.
💻 Technical Criteria
Given A complete foreign cargo record has been assembled with all required data
When The system stores the new cargo record
Then The foreign cargo record is inserted into the GCSUSRT US cargo database for subsequent processing and status tracking
R-GCX016E-cbl-03128 Log Cargo Creation Action
Process Rules
📊 Business Logic Narrative
When the process 'Log Cargo Creation Action' is invoked, and assuming that a new foreign cargo record has been successfully inserted into the database, when the system completes cargo record creation, the desired outcome is that the cargo creation action is logged with appropriate details for audit trail and processing history tracking.
💻 Technical Criteria
Given A new foreign cargo record has been successfully inserted into the database
When The system completes cargo record creation
Then The cargo creation action is logged with appropriate details for audit trail and processing history tracking
R-GCX016E-cbl-03331 Store Manifest Data
Process Rules
📊 Business Logic Narrative
When the process 'Store Manifest Data' is invoked, and assuming that a complete and validated manifest has been created, when the system stores the manifest data, the desired outcome is that the manifest data is stored in the system for subsequent cargo and customs processing.
💻 Technical Criteria
Given A complete and validated manifest has been created
When The system stores the manifest data
Then The manifest data is stored in the system for subsequent cargo and customs processing
R-GCX016E-cbl-02448 Finalize Foreign Manifest
Process Rules
📊 Business Logic Narrative
When the process 'Finalize Foreign Manifest' is invoked, and assuming that a foreign manifest structure has been built and validated (either complete or with logged warnings), when the system finalizes the foreign manifest, the desired outcome is that the foreign manifest is prepared for return to the cargo creation process.
💻 Technical Criteria
Given A foreign manifest structure has been built and validated (either complete or with logged warnings)
When The system finalizes the foreign manifest
Then The foreign manifest is prepared for return to the cargo creation process
R-GCX016E-cbl-02455 Validate Location Identifier
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Location Identifier' is invoked, and assuming that a station has been found in the station table, when the system validates the location identifier for the station, the desired outcome is that the system determines if the location identifier is valid for cargo routing purposes.
💻 Technical Criteria
Given A station has been found in the station table
When The system validates the location identifier for the station
Then The system determines if the location identifier is valid for cargo routing purposes
R-GCX016E-cbl-02456 Location Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Location Valid?' is invoked, and assuming that a location identifier has been validated, when the system checks the validation results, the desired outcome is that the system routes to either station information setup for cargo routing or invalid location error processing.
💻 Technical Criteria
Given A location identifier has been validated
When The system checks the validation results
Then The system routes to either station information setup for cargo routing or invalid location error processing
R-GCX016E-cbl-02457 Set Station Information for Cargo Routing
Process Rules
📊 Business Logic Narrative
When the process 'Set Station Information for Cargo Routing' is invoked, and assuming that a station has been found and its location identifier is valid, when the system sets up station information, the desired outcome is that the system configures the station data for cargo routing operations and completes the station lookup process.
💻 Technical Criteria
Given A station has been found and its location identifier is valid
When The system sets up station information
Then The system configures the station data for cargo routing operations and completes the station lookup process
R-GCX016E-cbl-02461 Initialize Merlin Message Structure
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Merlin Message Structure' is invoked, and assuming that a cargo disposition code processing event requires merlin notification, when the system begins formatting a comprehensive merlin message, the desired outcome is that the merlin message structure is initialized with default values and prepared for content population.
💻 Technical Criteria
Given A cargo disposition code processing event requires Merlin notification
When The system begins formatting a comprehensive Merlin message
Then The Merlin message structure is initialized with default values and prepared for content population
R-GCX016E-cbl-02462 Format Equipment Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment Information' is invoked, and assuming that a merlin message is being formatted for cargo processing, when equipment information needs to be included in the message, the desired outcome is that the system formats equipment initial, number, and type into the message structure.
💻 Technical Criteria
Given A Merlin message is being formatted for cargo processing
When Equipment information needs to be included in the message
Then The system formats equipment initial, number, and type into the message structure
R-GCX016E-cbl-02467 Calculate Release Quantity Impact
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Release Quantity Impact' is invoked, and assuming that a disposition code has been processed for cargo, when the disposition code affects release quantities, the desired outcome is that the system calculates the before and after quantities to determine the impact.
💻 Technical Criteria
Given A disposition code has been processed for cargo
When The disposition code affects release quantities
Then The system calculates the before and after quantities to determine the impact
R-GCX016E-cbl-02473 Include Cargo Status Information
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Include Cargo Status Information', assuming that quantity impact processing is complete or not applicable, when cargo status information is available, the desired outcome is that the system includes current cargo status details in the message.
💻 Technical Criteria
EXCLUDING Quantity impact processing is complete or not applicable
When Cargo status information is available
Then The system includes current cargo status details in the message
R-GCX016E-cbl-02474 Add Current Cargo Status
Process Rules
📊 Business Logic Narrative
When the process 'Add Current Cargo Status' is invoked, and assuming that cargo status information is being included, when current cargo status is available in the system, the desired outcome is that the system adds the current status code and description to the message.
💻 Technical Criteria
Given Cargo status information is being included
When Current cargo status is available in the system
Then The system adds the current status code and description to the message
R-GCX016E-cbl-02475 Include Hold/Release Flags
Process Rules
📊 Business Logic Narrative
When the process 'Include Hold/Release Flags' is invoked, and assuming that current cargo status has been added to the message, when hold or release flags are set for the cargo, the desired outcome is that the system includes the relevant hold/release flag information in the message.
💻 Technical Criteria
Given Current cargo status has been added to the message
When Hold or release flags are set for the cargo
Then The system includes the relevant hold/release flag information in the message
R-GCX016E-cbl-02480 Add Special Comments
Process Rules
📊 Business Logic Narrative
When the process 'Add Special Comments' is invoked, and assuming that processing details have been included in the message, when special comments are available for the cargo or processing event, the desired outcome is that the system adds the special comments to enhance message content.
💻 Technical Criteria
Given Processing details have been included in the message
When Special comments are available for the cargo or processing event
Then The system adds the special comments to enhance message content
R-GCX016E-cbl-02499 Retrieve Current Cargo Release Quantity
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Cargo Release Quantity' is invoked, and assuming that a cargo record exists with release quantity information, when release quantity impact analysis is initiated, the desired outcome is that the current cargo release quantity is retrieved and stored for comparison calculations.
💻 Technical Criteria
Given A cargo record exists with release quantity information
When Release quantity impact analysis is initiated
Then The current cargo release quantity is retrieved and stored for comparison calculations
R-GCX016E-cbl-02500 Identify Disposition Code Action Type
Decision Rules
📊 Business Logic Narrative
When the process 'Identify Disposition Code Action Type' is invoked, and assuming that a disposition code is being processed for cargo, when the system evaluates the disposition code's quantity impact characteristics, the desired outcome is that the action type is classified as add action, subtract action, or status info only based on the disposition code properties.
💻 Technical Criteria
Given A disposition code is being processed for cargo
When The system evaluates the disposition code's quantity impact characteristics
Then The action type is classified as Add Action, Subtract Action, or Status Info Only based on the disposition code properties
R-GCX016E-cbl-02501 Add to Release Quantity
Computation Rules
📊 Business Logic Narrative
When the process 'Add to Release Quantity' is invoked, and assuming that a disposition code with add action type is being processed, when the quantity impact calculation is performed, the desired outcome is that the disposition code quantity is added to the current cargo release quantity.
💻 Technical Criteria
Given A disposition code with Add Action type is being processed
When The quantity impact calculation is performed
Then The disposition code quantity is added to the current cargo release quantity
R-GCX016E-cbl-02502 Subtract from Release Quantity
Computation Rules
📊 Business Logic Narrative
When the process 'Subtract from Release Quantity' is invoked, and assuming that a disposition code with subtract action type is being processed, when the quantity impact calculation is performed, the desired outcome is that the disposition code quantity is subtracted from the current cargo release quantity.
💻 Technical Criteria
Given A disposition code with Subtract Action type is being processed
When The quantity impact calculation is performed
Then The disposition code quantity is subtracted from the current cargo release quantity
R-GCX016E-cbl-02510 Initialize New Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Initialize New Cargo Record' is invoked, and assuming that a new cargo record needs to be created in the system, when the cargo record initialization process is triggered, the desired outcome is that a new cargo record structure is created with all fields initialized to default values and ready for data population.
💻 Technical Criteria
Given A new cargo record needs to be created in the system
When The cargo record initialization process is triggered
Then A new cargo record structure is created with all fields initialized to default values and ready for data population
R-GCX016E-cbl-02511 Set Up Cargo Record with X4 Segment Data
Process Rules
📊 Business Logic Narrative
When the process 'Set Up Cargo Record with X4 Segment Data' is invoked, and assuming that a cargo record exists and x4 segment data is available with disposition codes and quantities, when x4 segment data is processed for cargo record setup, the desired outcome is that the cargo record is populated with disposition code, entry number, quantity information, and processing flags from the x4 segment.
💻 Technical Criteria
Given A cargo record exists and X4 segment data is available with disposition codes and quantities
When X4 segment data is processed for cargo record setup
Then The cargo record is populated with disposition code, entry number, quantity information, and processing flags from the X4 segment
R-GCX016E-cbl-02512 Set Up Cargo Record with N7 Segment Data
Process Rules
📊 Business Logic Narrative
When the process 'Set Up Cargo Record with N7 Segment Data' is invoked, and assuming that a cargo record exists and n7 segment data is available with equipment details, when n7 segment data is processed for cargo record setup, the desired outcome is that the cargo record is populated with equipment initial, equipment number, car id, and equipment type information from the n7 segment.
💻 Technical Criteria
Given A cargo record exists and N7 segment data is available with equipment details
When N7 segment data is processed for cargo record setup
Then The cargo record is populated with equipment initial, equipment number, car ID, and equipment type information from the N7 segment
R-GCX016E-cbl-02513 CPRS Traffic?
Decision Rules
📊 Business Logic Narrative
When the process 'CPRS Traffic?' is invoked, and assuming that a cargo record with equipment and routing information is being processed, when the system evaluates the cargo type for cprs classification, the desired outcome is that the system identifies whether the cargo is cprs traffic or standard traffic based on predefined cprs indicators.
💻 Technical Criteria
Given A cargo record with equipment and routing information is being processed
When The system evaluates the cargo type for CPRS classification
Then The system identifies whether the cargo is CPRS traffic or standard traffic based on predefined CPRS indicators
R-GCX016E-cbl-02514 Apply CPRS Special Handling
Process Rules
📊 Business Logic Narrative
When the process 'Apply CPRS Special Handling' is invoked, and assuming that a cargo record is identified as cprs traffic, when cprs special handling is applied to the cargo record, the desired outcome is that the car id information is cleared and cprs-specific processing rules are applied to the cargo record.
💻 Technical Criteria
Given A cargo record is identified as CPRS traffic
When CPRS special handling is applied to the cargo record
Then The car ID information is cleared and CPRS-specific processing rules are applied to the cargo record
R-GCX016E-cbl-02515 Apply Standard Car ID Formatting
Process Rules
📊 Business Logic Narrative
When the process 'Apply Standard Car ID Formatting' is invoked, and assuming that a cargo record is identified as non-cprs traffic with equipment initial and number available, when standard car id formatting is applied, the desired outcome is that the car id is formatted according to standard rules combining equipment initial and equipment number.
💻 Technical Criteria
Given A cargo record is identified as non-CPRS traffic with equipment initial and number available
When Standard car ID formatting is applied
Then The car ID is formatted according to standard rules combining equipment initial and equipment number
R-GCX016E-cbl-02516 Format Car ID According to Standards
Validation Rules
📊 Business Logic Narrative
When the process 'Format Car ID According to Standards' is invoked, and assuming that a cargo record has car id information that needs formatting, when car id formatting standards are applied, the desired outcome is that the car id is formatted according to system standards with proper spacing, character positioning, and validation.
💻 Technical Criteria
Given A cargo record has car ID information that needs formatting
When Car ID formatting standards are applied
Then The car ID is formatted according to system standards with proper spacing, character positioning, and validation
R-GCX016E-cbl-02517 Validate Cargo Record Data
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Cargo Record Data' is invoked, and assuming that a cargo record is populated with x4 and n7 segment data and formatted car id, when cargo record validation is performed, the desired outcome is that all required fields are validated for completeness, data integrity, and business rule compliance, and any validation errors are identified.
💻 Technical Criteria
Given A cargo record is populated with X4 and N7 segment data and formatted car ID
When Cargo record validation is performed
Then All required fields are validated for completeness, data integrity, and business rule compliance, and any validation errors are identified
R-GCX016E-cbl-02518 Insert Cargo Record into Database
Action Rules
📊 Business Logic Narrative
When the process 'Insert Cargo Record into Database' is invoked, and assuming that a validated cargo record is ready for database insertion, when the database insertion operation is executed, the desired outcome is that the cargo record is inserted into the gcsusrt database table and the operation result is captured.
💻 Technical Criteria
Given A validated cargo record is ready for database insertion
When The database insertion operation is executed
Then The cargo record is inserted into the GCSUSRT database table and the operation result is captured
R-GCX016E-cbl-02519 Database Insert Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'Database Insert Successful?' is invoked, and assuming that a cargo record insertion operation has been attempted, when the database insertion result is evaluated, the desired outcome is that the system determines whether the insertion was successful or failed based on database response codes.
💻 Technical Criteria
Given A cargo record insertion operation has been attempted
When The database insertion result is evaluated
Then The system determines whether the insertion was successful or failed based on database response codes
R-GCX016E-cbl-02520 Log Successful Insertion
Process Rules
📊 Business Logic Narrative
When the process 'Log Successful Insertion' is invoked, and assuming that a cargo record has been successfully inserted into the database, when success logging is performed, the desired outcome is that the successful insertion is logged with cargo record details, timestamp, and confirmation of database update.
💻 Technical Criteria
Given A cargo record has been successfully inserted into the database
When Success logging is performed
Then The successful insertion is logged with cargo record details, timestamp, and confirmation of database update
R-GCX016E-cbl-02521 Handle Database Insert Error
Process Rules
📊 Business Logic Narrative
When the process 'Handle Database Insert Error' is invoked, and assuming that a cargo record insertion operation has failed, when database insert error handling is triggered, the desired outcome is that the insertion failure is logged with error details and appropriate error recovery or notification procedures are initiated.
💻 Technical Criteria
Given A cargo record insertion operation has failed
When Database insert error handling is triggered
Then The insertion failure is logged with error details and appropriate error recovery or notification procedures are initiated
R-GCX016E-cbl-02539 Set Station Data for Cargo Routing
Process Rules
📊 Business Logic Narrative
When the process 'Set Station Data for Cargo Routing' is invoked, and assuming that station name and details have been extracted from the ds table record, when the system prepares cargo routing information, the desired outcome is that the station data is set and made available for cargo routing purposes.
💻 Technical Criteria
Given Station name and details have been extracted from the DS table record
When The system prepares cargo routing information
Then The station data is set and made available for cargo routing purposes
R-GCX016E-cbl-02568 Initialize Message Fields
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Message Fields' is invoked, and assuming that a cargo processing event requires merlin notification, when the system begins message creation process, the desired outcome is that all message fields, counters, and data structures are reset to initial state.
💻 Technical Criteria
Given A cargo processing event requires Merlin notification
When The system begins message creation process
Then All message fields, counters, and data structures are reset to initial state
R-GCX016E-cbl-02569 Format Equipment Information
Computation Rules
📊 Business Logic Narrative
When the process 'Format Equipment Information' is invoked, and assuming that equipment information exists in the cargo record, when creating a merlin message for cargo disposition, the desired outcome is that equipment type, identification number, and related cargo details are formatted and included in the message.
💻 Technical Criteria
Given Equipment information exists in the cargo record
When Creating a Merlin message for cargo disposition
Then Equipment type, identification number, and related cargo details are formatted and included in the message
R-GCX016E-cbl-02572 Format Disposition Code Details
Computation Rules
📊 Business Logic Narrative
When the process 'Format Disposition Code Details' is invoked, and assuming that a disposition code is being processed for cargo, when creating comprehensive merlin message, the desired outcome is that disposition code details are formatted with proper context and included in the message.
💻 Technical Criteria
Given A disposition code is being processed for cargo
When Creating comprehensive Merlin message
Then Disposition code details are formatted with proper context and included in the message
R-GCX016E-cbl-02574 Calculate Release Quantity Impact
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Release Quantity Impact' is invoked, and assuming that cargo has existing release quantities and a new disposition is being applied, when processing disposition code that affects quantities, the desired outcome is that system calculates the impact on release quantities (increase, decrease, or no change).
💻 Technical Criteria
Given Cargo has existing release quantities and a new disposition is being applied
When Processing disposition code that affects quantities
Then System calculates the impact on release quantities (increase, decrease, or no change)
R-GCX016E-cbl-02577 Include Processing Timestamps
Computation Rules
📊 Business Logic Narrative
When the process 'Include Processing Timestamps' is invoked, and assuming that cargo processing events have occurred with recorded timestamps, when creating comprehensive merlin message, the desired outcome is that processing timestamps are included to provide audit trail information.
💻 Technical Criteria
Given Cargo processing events have occurred with recorded timestamps
When Creating comprehensive Merlin message
Then Processing timestamps are included to provide audit trail information
R-GCX016E-cbl-02578 Add USCS Processing Time
Computation Rules
📊 Business Logic Narrative
When the process 'Add USCS Processing Time' is invoked, and assuming that uscs processing time is available for the cargo event, when building comprehensive message content, the desired outcome is that uscs processing time is added to the message for tracking purposes.
💻 Technical Criteria
Given USCS processing time is available for the cargo event
When Building comprehensive message content
Then USCS processing time is added to the message for tracking purposes
R-GCX016E-cbl-02579 Add System Processing Time
Computation Rules
📊 Business Logic Narrative
When the process 'Add System Processing Time' is invoked, and assuming that system processing time is recorded for the cargo event, when creating merlin notification message, the desired outcome is that system processing time is included in the message for complete audit trail.
💻 Technical Criteria
Given System processing time is recorded for the cargo event
When Creating Merlin notification message
Then System processing time is included in the message for complete audit trail
R-GCX016E-cbl-02580 Process K1 Comments
Process Rules
📊 Business Logic Narrative
When the process 'Process K1 Comments' is invoked, and assuming that k1 segment data exists for the cargo, when building comprehensive merlin message, the desired outcome is that k1 comments are processed and evaluated for inclusion in the message.
💻 Technical Criteria
Given K1 segment data exists for the cargo
When Building comprehensive Merlin message
Then K1 comments are processed and evaluated for inclusion in the message
R-GCX016E-cbl-02583 Add Special Comments
Computation Rules
📊 Business Logic Narrative
When the process 'Add Special Comments' is invoked, and assuming that special comments exist for the cargo or processing event, when building comprehensive message content, the desired outcome is that special comments are added to provide additional context and information.
💻 Technical Criteria
Given Special comments exist for the cargo or processing event
When Building comprehensive message content
Then Special comments are added to provide additional context and information
R-GCX016E-cbl-02584 Canadian Pacific Railway Bond?
Decision Rules
📊 Business Logic Narrative
When the process 'Canadian Pacific Railway Bond?' is invoked, and assuming that cargo processing involves bond-related activities, when evaluating special processing requirements, the desired outcome is that if canadian pacific railway bond processing is detected, special bond notification is added; otherwise, standard processing continues.
💻 Technical Criteria
Given Cargo processing involves bond-related activities
When Evaluating special processing requirements
Then If Canadian Pacific Railway bond processing is detected, special bond notification is added; otherwise, standard processing continues
R-GCX016E-cbl-02591 Extract Bond Information
Action Rules
📊 Business Logic Narrative
When the process 'Extract Bond Information' is invoked, and assuming that a cpr bond creation message has been identified, when the system processes the k1 segment content, the desired outcome is that bond-related information including bond numbers, amounts, and related cargo details are extracted from the message.
💻 Technical Criteria
Given A CPR bond creation message has been identified
When The system processes the K1 segment content
Then Bond-related information including bond numbers, amounts, and related cargo details are extracted from the message
R-GCX016E-cbl-02594 Format CPR Bond Notification
Process Rules
📊 Business Logic Narrative
When the process 'Format CPR Bond Notification' is invoked, and assuming that cpr bond creation has been validated and approved, when the system formats the bond notification message, the desired outcome is that a structured notification message is created containing bond details, cargo information, and cpr-specific formatting requirements.
💻 Technical Criteria
Given CPR bond creation has been validated and approved
When The system formats the bond notification message
Then A structured notification message is created containing bond details, cargo information, and CPR-specific formatting requirements
R-GCX016E-cbl-02601 Retrieve Current Cargo Release Quantity
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Cargo Release Quantity' is invoked, and assuming that a cargo record exists with release quantity information, when the system needs to calculate quantity impact for disposition code processing, the desired outcome is that the current cargo release quantity is retrieved and stored for comparison calculations.
💻 Technical Criteria
Given A cargo record exists with release quantity information
When The system needs to calculate quantity impact for disposition code processing
Then The current cargo release quantity is retrieved and stored for comparison calculations
R-GCX016E-cbl-02602 Identify Disposition Code Action Type
Decision Rules
📊 Business Logic Narrative
When the process 'Identify Disposition Code Action Type' is invoked, and assuming that a disposition code is being processed for a cargo, when the system evaluates the disposition code's impact on quantities, the desired outcome is that the action type is identified as either quantity addition, quantity subtraction, or no quantity change.
💻 Technical Criteria
Given A disposition code is being processed for a cargo
When The system evaluates the disposition code's impact on quantities
Then The action type is identified as either quantity addition, quantity subtraction, or no quantity change
R-GCX016E-cbl-02604 Calculate Quantity Addition
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Quantity Addition' is invoked, and assuming that a disposition code that adds to cargo release quantities and the current release amount, when the system processes a quantity-increasing disposition code, the desired outcome is that the additional quantity amount is calculated based on the disposition code rules and cargo specifications.
💻 Technical Criteria
Given A disposition code that adds to cargo release quantities and the current release amount
When The system processes a quantity-increasing disposition code
Then The additional quantity amount is calculated based on the disposition code rules and cargo specifications
R-GCX016E-cbl-02605 Calculate Quantity Subtraction
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Quantity Subtraction' is invoked, and assuming that a disposition code that subtracts from cargo release quantities and the current release amount, when the system processes a quantity-decreasing disposition code, the desired outcome is that the subtraction quantity amount is calculated based on the disposition code rules and current cargo quantities.
💻 Technical Criteria
Given A disposition code that subtracts from cargo release quantities and the current release amount
When The system processes a quantity-decreasing disposition code
Then The subtraction quantity amount is calculated based on the disposition code rules and current cargo quantities
R-GCX016E-cbl-02606 Determine New Release Quantity
Computation Rules
📊 Business Logic Narrative
When the process 'Determine New Release Quantity' is invoked, and assuming that current cargo release quantity and calculated quantity change amount from disposition code processing, when the system applies the disposition code quantity impact, the desired outcome is that the new release quantity is determined by applying the calculated addition, subtraction, or no change to the current quantity.
💻 Technical Criteria
Given Current cargo release quantity and calculated quantity change amount from disposition code processing
When The system applies the disposition code quantity impact
Then The new release quantity is determined by applying the calculated addition, subtraction, or no change to the current quantity
R-GCX016E-cbl-02607 Format Before Quantity Display
Process Rules
📊 Business Logic Narrative
When the process 'Format Before Quantity Display' is invoked, and assuming that current cargo release quantity retrieved from cargo record, when the system prepares quantity impact messaging, the desired outcome is that the current quantity is formatted for display as the 'before' quantity in impact messages.
💻 Technical Criteria
Given Current cargo release quantity retrieved from cargo record
When The system prepares quantity impact messaging
Then The current quantity is formatted for display as the 'before' quantity in impact messages
R-GCX016E-cbl-02613 Include K1 Comments if Present
Process Rules
📊 Business Logic Narrative
When the process 'Include K1 Comments if Present' is invoked, and assuming that a quantity impact message and k1 segment comments associated with the cargo, when the system finalizes impact messaging and k1 comments exist, the desired outcome is that the k1 comments are included in the impact message to provide additional context.
💻 Technical Criteria
Given A quantity impact message and K1 segment comments associated with the cargo
When The system finalizes impact messaging and K1 comments exist
Then The K1 comments are included in the impact message to provide additional context
R-GCX016E-cbl-02615 Cargo Status Changed?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Status Changed?' is invoked, and assuming that a cargo processing transaction is being executed, when the system evaluates whether cargo status has been modified during processing, the desired outcome is that the system proceeds with gcciis integration if status changed, otherwise skips integration.
💻 Technical Criteria
Given A cargo processing transaction is being executed
When The system evaluates whether cargo status has been modified during processing
Then The system proceeds with GCCIIS integration if status changed, otherwise skips integration
R-GCX016E-cbl-02616 Map Internal Status to GCCIIS Status
Definitional Rules
📊 Business Logic Narrative
When the process 'Map Internal Status to GCCIIS Status' is invoked, and assuming that a cargo has an internal status that needs to be communicated to gcciis, when the system processes the status mapping transformation, the desired outcome is that the internal status is converted to the appropriate gcciis status format.
💻 Technical Criteria
Given A cargo has an internal status that needs to be communicated to GCCIIS
When The system processes the status mapping transformation
Then The internal status is converted to the appropriate GCCIIS status format
R-GCX016E-cbl-02617 Equipment Type Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Equipment Type Valid?' is invoked, and assuming that a cargo has associated equipment information, when the system checks if the equipment type is valid for gcciis processing, the desired outcome is that the system continues processing if equipment type is container, trailer, chassis, or other valid equipment, otherwise skips gcciis integration.
💻 Technical Criteria
Given A cargo has associated equipment information
When The system checks if the equipment type is valid for GCCIIS processing
Then The system continues processing if equipment type is container, trailer, chassis, or other valid equipment, otherwise skips GCCIIS integration
R-GCX016E-cbl-02618 Validate Equipment Type
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Equipment Type' is invoked, and assuming that equipment information is available for a cargo, when the system validates the equipment type against acceptable categories, the desired outcome is that the equipment is classified as container, trailer, chassis, or other valid equipment type for further processing.
💻 Technical Criteria
Given Equipment information is available for a cargo
When The system validates the equipment type against acceptable categories
Then The equipment is classified as container, trailer, chassis, or other valid equipment type for further processing
R-GCX016E-cbl-02619 Release Quantity Check
Decision Rules
📊 Business Logic Narrative
When the process 'Release Quantity Check' is invoked, and assuming that a cargo has a status that may require quantity validation, when the system evaluates whether full release validation is needed, the desired outcome is that the system either requires full release quantity check or allows partial release processing.
💻 Technical Criteria
Given A cargo has a status that may require quantity validation
When The system evaluates whether full release validation is needed
Then The system either requires full release quantity check or allows partial release processing
R-GCX016E-cbl-02620 Check Released vs Total Quantity
Validation Rules
📊 Business Logic Narrative
When the process 'Check Released vs Total Quantity' is invoked, and assuming that a cargo requires full release validation and has released and total quantity values, when the system compares the released quantity to the total quantity, the desired outcome is that the system continues processing if released equals total quantity, otherwise skips gcciis integration.
💻 Technical Criteria
Given A cargo requires full release validation and has released and total quantity values
When The system compares the released quantity to the total quantity
Then The system continues processing if released equals total quantity, otherwise skips GCCIIS integration
R-GCX016E-cbl-02621 Prepare GCCIIS Status Update
Process Rules
📊 Business Logic Narrative
When the process 'Prepare GCCIIS Status Update' is invoked, and assuming that a cargo has passed validation checks and requires gcciis status update, when the system prepares the status update message, the desired outcome is that the system formats the cargo and equipment information for gcciis transmission.
💻 Technical Criteria
Given A cargo has passed validation checks and requires GCCIIS status update
When The system prepares the status update message
Then The system formats the cargo and equipment information for GCCIIS transmission
R-GCX016E-cbl-02622 Status Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Status Type?' is invoked, and assuming that a cargo status update is ready for gcciis transmission, when the system evaluates the cargo status to determine gcciis status type, the desired outcome is that the system selects hold, release, ptt, or ptt-ex status based on cargo conditions.
💻 Technical Criteria
Given A cargo status update is ready for GCCIIS transmission
When The system evaluates the cargo status to determine GCCIIS status type
Then The system selects HOLD, RELEASE, PTT, or PTT-EX status based on cargo conditions
R-GCX016E-cbl-02623 Set GCCIIS Status: HOLD
Action Rules
📊 Business Logic Narrative
When the process 'Set GCCIIS Status: HOLD' is invoked, and assuming that a cargo has hold conditions that need to be communicated to gcciis, when the system processes hold status assignment, the desired outcome is that the system sets gcciis status to hold for held cargo conditions.
💻 Technical Criteria
Given A cargo has hold conditions that need to be communicated to GCCIIS
When The system processes hold status assignment
Then The system sets GCCIIS status to HOLD for held cargo conditions
R-GCX016E-cbl-02624 Set GCCIIS Status: RELEASE
Action Rules
📊 Business Logic Narrative
When the process 'Set GCCIIS Status: RELEASE' is invoked, and assuming that a cargo has been fully released and meets release criteria, when the system processes release status assignment, the desired outcome is that the system sets gcciis status to release for released cargo.
💻 Technical Criteria
Given A cargo has been fully released and meets release criteria
When The system processes release status assignment
Then The system sets GCCIIS status to RELEASE for released cargo
R-GCX016E-cbl-02625 Set GCCIIS Status: PTT
Action Rules
📊 Business Logic Narrative
When the process 'Set GCCIIS Status: PTT' is invoked, and assuming that a cargo has permit to transfer status that needs to be communicated to gcciis, when the system processes ptt status assignment, the desired outcome is that the system sets gcciis status to ptt for cargo with transit permission.
💻 Technical Criteria
Given A cargo has Permit to Transfer status that needs to be communicated to GCCIIS
When The system processes PTT status assignment
Then The system sets GCCIIS status to PTT for cargo with transit permission
R-GCX016E-cbl-02626 Set GCCIIS Status: PTT-EX
Action Rules
📊 Business Logic Narrative
When the process 'Set GCCIIS Status: PTT-EX' is invoked, and assuming that a cargo has permit to transfer with examination requirements that need to be communicated to gcciis, when the system processes ptt-ex status assignment, the desired outcome is that the system sets gcciis status to ptt-ex for cargo requiring examination.
💻 Technical Criteria
Given A cargo has Permit to Transfer with examination requirements that need to be communicated to GCCIIS
When The system processes PTT-EX status assignment
Then The system sets GCCIIS status to PTT-EX for cargo requiring examination
R-GCX016E-cbl-02627 Send Status Update to GCCIIS
Action Rules
📊 Business Logic Narrative
When the process 'Send Status Update to GCCIIS' is invoked, and assuming that a gcciis status update is prepared and ready for transmission, when the system sends the status update to gcciis, the desired outcome is that the system transmits the cargo status information to the gcciis equipment tracking system.
💻 Technical Criteria
Given A GCCIIS status update is prepared and ready for transmission
When The system sends the status update to GCCIIS
Then The system transmits the cargo status information to the GCCIIS equipment tracking system
R-GCX016E-cbl-02632 Retrieve Cargo Segment Data from GCSUSS03
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Cargo Segment Data from GCSUSS03' is invoked, and assuming that a disposition code is identified as freight forwarder-related, when the system needs cargo information for freight forwarder processing, the desired outcome is that the system retrieves cargo segment data from the primary cargo database.
💻 Technical Criteria
Given A disposition code is identified as freight forwarder-related
When The system needs cargo information for freight forwarder processing
Then The system retrieves cargo segment data from the primary cargo database
R-GCX016E-cbl-02633 Retrieve Additional Cargo Data from GCSUSS07
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Additional Cargo Data from GCSUSS07' is invoked, and assuming that primary cargo segment data has been retrieved for freight forwarder processing, when additional cargo details are needed for complete freight forwarder information, the desired outcome is that the system retrieves supplementary cargo data from the extended cargo database.
💻 Technical Criteria
Given Primary cargo segment data has been retrieved for freight forwarder processing
When Additional cargo details are needed for complete freight forwarder information
Then The system retrieves supplementary cargo data from the extended cargo database
R-GCX016E-cbl-02634 Extract Freight Forwarder Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Freight Forwarder Information' is invoked, and assuming that cargo segment data and additional cargo data are available, when the system processes freight forwarder disposition codes, the desired outcome is that the system extracts freight forwarder identification and contact details from the cargo records.
💻 Technical Criteria
Given Cargo segment data and additional cargo data are available
When The system processes freight forwarder disposition codes
Then The system extracts freight forwarder identification and contact details from the cargo records
R-GCX016E-cbl-02635 Lookup Freight Forwarder Name in Broker Tables
Action Rules
📊 Business Logic Narrative
When the process 'Lookup Freight Forwarder Name in Broker Tables' is invoked, and assuming that freight forwarder identification has been extracted from cargo data, when the system needs complete freight forwarder contact information, the desired outcome is that the system searches the broker name tables to retrieve freight forwarder name and contact details.
💻 Technical Criteria
Given Freight forwarder identification has been extracted from cargo data
When The system needs complete freight forwarder contact information
Then The system searches the broker name tables to retrieve freight forwarder name and contact details
R-GCX016E-cbl-02639 Access Cargo Record
Action Rules
📊 Business Logic Narrative
When the process 'Access Cargo Record' is invoked, and assuming that a cargo processing request is initiated for freight forwarder identification, when the system needs to retrieve freight forwarder information, the desired outcome is that the cargo record is accessed and made available for segment processing.
💻 Technical Criteria
Given A cargo processing request is initiated for freight forwarder identification
When The system needs to retrieve freight forwarder information
Then The cargo record is accessed and made available for segment processing
R-GCX016E-cbl-02640 Retrieve GCSUSS03 Segment
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve GCSUSS03 Segment' is invoked, and assuming that a cargo record is being processed for freight forwarder identification, when the system attempts to retrieve the gcsuss03 segment from the cargo record, the desired outcome is that the gcsuss03 segment is retrieved from the cargo segments data source.
💻 Technical Criteria
Given A cargo record is being processed for freight forwarder identification
When The system attempts to retrieve the GCSUSS03 segment from the cargo record
Then The GCSUSS03 segment is retrieved from the cargo segments data source
R-GCX016E-cbl-02643 Retrieve GCSUSS07 Segment
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve GCSUSS07 Segment' is invoked, and assuming that the system is processing freight forwarder identification regardless of gcsuss03 availability, when the system attempts to retrieve the gcsuss07 segment from the cargo record, the desired outcome is that the gcsuss07 segment is retrieved from the cargo segments data source.
💻 Technical Criteria
Given The system is processing freight forwarder identification regardless of GCSUSS03 availability
When The system attempts to retrieve the GCSUSS07 segment from the cargo record
Then The GCSUSS07 segment is retrieved from the cargo segments data source
R-GCX016E-cbl-02647 Validate Freight Forwarder Data
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Freight Forwarder Data' is invoked, and assuming that freight forwarder information has been compiled from cargo segments, when the system validates the compiled data, the desired outcome is that the freight forwarder data is checked for validity and completeness.
💻 Technical Criteria
Given Freight forwarder information has been compiled from cargo segments
When The system validates the compiled data
Then The freight forwarder data is checked for validity and completeness
R-GCX016E-cbl-02652 Retrieve Cargo Segment Data
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Cargo Segment Data' is invoked, and assuming that a cargo record exists with segment data, when the system processes freight forwarder broker lookup request, the desired outcome is that the freight forwarder code is extracted from the cargo segment data for further processing.
💻 Technical Criteria
Given A cargo record exists with segment data
When The system processes freight forwarder broker lookup request
Then The freight forwarder code is extracted from the cargo segment data for further processing
R-GCX016E-cbl-02653 Freight Forwarder Code Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Freight Forwarder Code Found?' is invoked, and assuming that cargo segment data has been retrieved, when the system checks for freight forwarder code presence, the desired outcome is that if freight forwarder code exists, proceed to broker database search; otherwise set lookup failed flag.
💻 Technical Criteria
Given Cargo segment data has been retrieved
When The system checks for freight forwarder code presence
Then If freight forwarder code exists, proceed to broker database search; otherwise set lookup failed flag
R-GCX016E-cbl-02664 Retrieve Cargo Segment Data
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Cargo Segment Data' is invoked, and assuming that a cargo record exists with segment data, when the system needs to process freight forwarder notifications, the desired outcome is that the system retrieves cargo segment data including freight forwarder and consignee information from gcsuss03 and gcsuss07 segments.
💻 Technical Criteria
Given A cargo record exists with segment data
When The system needs to process freight forwarder notifications
Then The system retrieves cargo segment data including freight forwarder and consignee information from GCSUSS03 and GCSUSS07 segments
R-GCX016E-cbl-02665 Freight Forwarder Information Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Freight Forwarder Information Available?' is invoked, and assuming that cargo segment data has been retrieved, when the system evaluates freight forwarder information, the desired outcome is that the system determines if freight forwarder information is available and proceeds with lookup or logs missing information warning.
💻 Technical Criteria
Given Cargo segment data has been retrieved
When The system evaluates freight forwarder information
Then The system determines if freight forwarder information is available and proceeds with lookup or logs missing information warning
R-GCX016E-cbl-02666 Look up Freight Forwarder Name from Broker Database
Action Rules
📊 Business Logic Narrative
When the process 'Look up Freight Forwarder Name from Broker Database' is invoked, and assuming that freight forwarder information is available in cargo segment, when the system needs to retrieve freight forwarder details, the desired outcome is that the system searches gcst2rt broker name segments table using freight forwarder identifier.
💻 Technical Criteria
Given Freight forwarder information is available in cargo segment
When The system needs to retrieve freight forwarder details
Then The system searches GCST2RT broker name segments table using freight forwarder identifier
R-GCX016E-cbl-02675 Search Broker Database for Freight Forwarder Disposition Codes
Action Rules
📊 Business Logic Narrative
When the process 'Search Broker Database for Freight Forwarder Disposition Codes' is invoked, and assuming that a cargo disposition code needs to be processed for cih hold notification, when the system searches the broker name table for freight forwarder disposition codes, the desired outcome is that the system identifies if the disposition code corresponds to a freight forwarder.
💻 Technical Criteria
Given A cargo disposition code needs to be processed for CIH hold notification
When The system searches the broker name table for freight forwarder disposition codes
Then The system identifies if the disposition code corresponds to a freight forwarder
R-GCX016E-cbl-02677 Retrieve Cargo Segment Data from GCSUSS03/GCSUSS07
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Cargo Segment Data from GCSUSS03/GCSUSS07' is invoked, and assuming that a valid freight forwarder disposition code has been identified, when the system accesses gcsuss03 and gcsuss07 cargo segments, the desired outcome is that the system retrieves forwarder and consignee information for email content.
💻 Technical Criteria
Given A valid freight forwarder disposition code has been identified
When The system accesses GCSUSS03 and GCSUSS07 cargo segments
Then The system retrieves forwarder and consignee information for email content
R-GCX016E-cbl-02678 Extract Freight Forwarder Information from Cargo Segments
Process Rules
📊 Business Logic Narrative
When the process 'Extract Freight Forwarder Information from Cargo Segments' is invoked, and assuming that cargo segment data has been successfully retrieved from gcsuss03/gcsuss07, when the system processes the cargo segments to extract freight forwarder information, the desired outcome is that the system obtains freight forwarder identification and contact details.
💻 Technical Criteria
Given Cargo segment data has been successfully retrieved from GCSUSS03/GCSUSS07
When The system processes the cargo segments to extract freight forwarder information
Then The system obtains freight forwarder identification and contact details
R-GCX016E-cbl-02679 Lookup Freight Forwarder Name in Broker Database
Validation Rules
📊 Business Logic Narrative
When the process 'Lookup Freight Forwarder Name in Broker Database' is invoked, and assuming that freight forwarder information has been extracted from cargo segments, when the system searches the broker database for the freight forwarder name, the desired outcome is that the system validates the freight forwarder's existence in the broker database.
💻 Technical Criteria
Given Freight forwarder information has been extracted from cargo segments
When The system searches the broker database for the freight forwarder name
Then The system validates the freight forwarder's existence in the broker database
R-GCX016E-cbl-02683 Build Comprehensive Email Content
Process Rules
📊 Business Logic Narrative
When the process 'Build Comprehensive Email Content' is invoked, and assuming that a valid email address has been confirmed for the freight forwarder, when the system builds the email notification content, the desired outcome is that the system creates comprehensive email content with cargo details, equipment information, and hold reasons.
💻 Technical Criteria
Given A valid email address has been confirmed for the freight forwarder
When The system builds the email notification content
Then The system creates comprehensive email content with cargo details, equipment information, and hold reasons
R-GCX016E-cbl-02684 Include Equipment Information
Process Rules
📊 Business Logic Narrative
When the process 'Include Equipment Information' is invoked, and assuming that email content building has been initiated, when the system processes equipment information for inclusion in the email, the desired outcome is that the system adds equipment details including car id, equipment type, and related information to the email content.
💻 Technical Criteria
Given Email content building has been initiated
When The system processes equipment information for inclusion in the email
Then The system adds equipment details including car ID, equipment type, and related information to the email content
R-GCX016E-cbl-02712 Log Cargo Status Before Processing
Process Rules
📊 Business Logic Narrative
When the process 'Log Cargo Status Before Processing' is invoked, and assuming that a cargo requires status processing and debug logging is enabled, when the system begins cargo status processing, the desired outcome is that the current cargo status, quantities, and disposition codes are captured and logged as baseline information.
💻 Technical Criteria
Given A cargo requires status processing and debug logging is enabled
When The system begins cargo status processing
Then The current cargo status, quantities, and disposition codes are captured and logged as baseline information
R-GCX016E-cbl-02713 Capture Current Status Information
Decision Rules
📊 Business Logic Narrative
When the process 'Capture Current Status Information' is invoked, and assuming that debug logging is requested for cargo status processing, when the system attempts to capture current status information, the desired outcome is that if status information is available, proceed with detailed logging, otherwise skip to message formatting.
💻 Technical Criteria
Given Debug logging is requested for cargo status processing
When The system attempts to capture current status information
Then If status information is available, proceed with detailed logging, otherwise skip to message formatting
R-GCX016E-cbl-02714 Log RT10/RT11 Cargo Status
Process Rules
📊 Business Logic Narrative
When the process 'Log RT10/RT11 Cargo Status' is invoked, and assuming that cargo status information is available for logging, when the system processes rt10/rt11 cargo status records, the desired outcome is that rt10 and rt11 status details are captured and included in the debug log.
💻 Technical Criteria
Given Cargo status information is available for logging
When The system processes RT10/RT11 cargo status records
Then RT10 and RT11 status details are captured and included in the debug log
R-GCX016E-cbl-02715 Log Cargo Quantities
Process Rules
📊 Business Logic Narrative
When the process 'Log Cargo Quantities' is invoked, and assuming that cargo status processing requires quantity tracking, when the system logs cargo information, the desired outcome is that current cargo quantities, released quantities, and any pending quantity changes are documented in the debug log.
💻 Technical Criteria
Given Cargo status processing requires quantity tracking
When The system logs cargo information
Then Current cargo quantities, released quantities, and any pending quantity changes are documented in the debug log
R-GCX016E-cbl-02716 Log Disposition Codes
Process Rules
📊 Business Logic Narrative
When the process 'Log Disposition Codes' is invoked, and assuming that cargo has associated disposition codes, when the system performs debug logging, the desired outcome is that all current disposition codes, their entry numbers, and associated quantities are documented in the debug log.
💻 Technical Criteria
Given Cargo has associated disposition codes
When The system performs debug logging
Then All current disposition codes, their entry numbers, and associated quantities are documented in the debug log
R-GCX016E-cbl-02717 Dump Complete S09A Status Array
Process Rules
📊 Business Logic Narrative
When the process 'Dump Complete S09A Status Array' is invoked, and assuming that cargo has an s09a status array with multiple entries, when debug logging requires complete status visibility, the desired outcome is that the entire s09a status array is dumped showing all status codes, sequences, and occurrence data.
💻 Technical Criteria
Given Cargo has an S09A status array with multiple entries
When Debug logging requires complete status visibility
Then The entire S09A status array is dumped showing all status codes, sequences, and occurrence data
R-GCX016E-cbl-02718 Log Cargo Status After Processing
Process Rules
📊 Business Logic Narrative
When the process 'Log Cargo Status After Processing' is invoked, and assuming that cargo status processing has been completed, when the system finalizes debug logging, the desired outcome is that the final cargo status, updated quantities, and new disposition codes are captured and logged.
💻 Technical Criteria
Given Cargo status processing has been completed
When The system finalizes debug logging
Then The final cargo status, updated quantities, and new disposition codes are captured and logged
R-GCX016E-cbl-02726 EXPORT Message Type
Decision Rules
📊 Business Logic Narrative
When the process 'EXPORT Message Type' is invoked, and assuming that a merlin message is ready for distribution and message type is export, when the system evaluates the equipment type for routing decisions, the desired outcome is that the message should be routed according to equipment-specific routing rules.
💻 Technical Criteria
Given A Merlin message is ready for distribution and message type is EXPORT
When The system evaluates the equipment type for routing decisions
Then The message should be routed according to equipment-specific routing rules
R-GCX016E-cbl-02741 Route EXPORT Message
Decision Rules
📊 Business Logic Narrative
When the process 'Route EXPORT Message' is invoked, and assuming that a merlin message needs to be delivered, when the message type is export, the desired outcome is that the message should be routed based on equipment type settings.
💻 Technical Criteria
Given A Merlin message needs to be delivered
When The message type is EXPORT
Then The message should be routed based on equipment type settings
R-GCX016E-cbl-02750 Prepare Audit Log Entry
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Audit Log Entry' is invoked, and assuming that a cargo processing action has occurred that requires audit logging, when the system initiates audit log preparation, the desired outcome is that an audit log entry structure is prepared to capture the cargo processing action details.
💻 Technical Criteria
Given A cargo processing action has occurred that requires audit logging
When The system initiates audit log preparation
Then An audit log entry structure is prepared to capture the cargo processing action details
R-GCX016E-cbl-02751 Capture Timestamp Information
Policy Rules
📊 Business Logic Narrative
When the process 'Capture Timestamp Information' is invoked, and assuming that an audit log entry is being prepared for a cargo processing action, when the system captures timestamp information, the desired outcome is that the current date and time are recorded in the audit log entry for tracking when the action occurred.
💻 Technical Criteria
Given An audit log entry is being prepared for a cargo processing action
When The system captures timestamp information
Then The current date and time are recorded in the audit log entry for tracking when the action occurred
R-GCX016E-cbl-02757 Handle Logging Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Handle Logging Error', assuming that the gct1051e transaction spawn was not successful, when the system handles the logging error, the desired outcome is that the logging error is processed and handled appropriately without stopping the main cargo processing flow.
💻 Technical Criteria
EXCLUDING The GCT1051E transaction spawn was not successful
When The system handles the logging error
Then The logging error is processed and handled appropriately without stopping the main cargo processing flow
R-GCX016E-cbl-02758 Continue Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue Processing' is invoked, and assuming that either the audit log entry was successfully created or the logging error was handled, when the audit logging process is complete, the desired outcome is that the system continues with the main cargo processing workflow without interruption.
💻 Technical Criteria
Given Either the audit log entry was successfully created or the logging error was handled
When The audit logging process is complete
Then The system continues with the main cargo processing workflow without interruption
R-GCX016E-cbl-02759 Format Equipment Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment Information' is invoked, and assuming that a cargo record contains equipment information, when the system processes merlin report field management, the desired outcome is that the equipment information is formatted and prepared for report inclusion.
💻 Technical Criteria
Given A cargo record contains equipment information
When The system processes Merlin report field management
Then The equipment information is formatted and prepared for report inclusion
R-GCX016E-cbl-02760 Extract Car ID from Cargo Record
Process Rules
📊 Business Logic Narrative
When the process 'Extract Car ID from Cargo Record' is invoked, and assuming that a cargo record exists with car identification data, when the system needs car id information for merlin reporting, the desired outcome is that the car id is extracted from the cargo record and made available for formatting.
💻 Technical Criteria
Given A cargo record exists with car identification data
When The system needs car ID information for Merlin reporting
Then The car ID is extracted from the cargo record and made available for formatting
R-GCX016E-cbl-02763 Format Disposition Code Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Disposition Code Information' is invoked, and assuming that a disposition code exists for the cargo, when the system processes disposition code data for merlin reporting, the desired outcome is that the disposition code information is formatted for report inclusion.
💻 Technical Criteria
Given A disposition code exists for the cargo
When The system processes disposition code data for Merlin reporting
Then The disposition code information is formatted for report inclusion
R-GCX016E-cbl-02766 Format Date and Time Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Date and Time Information' is invoked, and assuming that date and time information is available for the cargo transaction, when the system processes temporal data for merlin reporting, the desired outcome is that the date and time information is formatted according to report requirements.
💻 Technical Criteria
Given Date and time information is available for the cargo transaction
When The system processes temporal data for Merlin reporting
Then The date and time information is formatted according to report requirements
R-GCX016E-cbl-02785 Initialize X4 Segment Array
Process Rules
📊 Business Logic Narrative
When the process 'Initialize X4 Segment Array' is invoked, and assuming that a cargo processing request is received, when the system begins message array initialization for cargo, the desired outcome is that the x4 segment array is initialized with proper structure and default values.
💻 Technical Criteria
Given A cargo processing request is received
When The system begins message array initialization for cargo
Then The X4 segment array is initialized with proper structure and default values
R-GCX016E-cbl-02786 Set Equipment Information in X4
Action Rules
📊 Business Logic Narrative
When the process 'Set Equipment Information in X4' is invoked, and assuming that an x4 segment array is initialized and cargo equipment data is available, when the system processes equipment information for the cargo, the desired outcome is that equipment identification details are populated into the x4 segment structure.
💻 Technical Criteria
Given An X4 segment array is initialized and cargo equipment data is available
When The system processes equipment information for the cargo
Then Equipment identification details are populated into the X4 segment structure
R-GCX016E-cbl-02787 Set Cargo Disposition Code in X4
Action Rules
📊 Business Logic Narrative
When the process 'Set Cargo Disposition Code in X4' is invoked, and assuming that an x4 segment is prepared and disposition code data is available, when the system processes cargo disposition requirements, the desired outcome is that the appropriate disposition code is assigned to the x4 segment.
💻 Technical Criteria
Given An X4 segment is prepared and disposition code data is available
When The system processes cargo disposition requirements
Then The appropriate disposition code is assigned to the X4 segment
R-GCX016E-cbl-02788 Set Date/Time Information in X4
Action Rules
📊 Business Logic Narrative
When the process 'Set Date/Time Information in X4' is invoked, and assuming that an x4 segment is being populated and current date/time is available, when the system processes timing information for the cargo transaction, the desired outcome is that current date and time information is populated into the x4 segment.
💻 Technical Criteria
Given An X4 segment is being populated and current date/time is available
When The system processes timing information for the cargo transaction
Then Current date and time information is populated into the X4 segment
R-GCX016E-cbl-02789 Set Location Information in X4
Action Rules
📊 Business Logic Narrative
When the process 'Set Location Information in X4' is invoked, and assuming that an x4 segment is being populated and location data is available, when the system processes location requirements for the cargo, the desired outcome is that location information is assigned to the x4 segment.
💻 Technical Criteria
Given An X4 segment is being populated and location data is available
When The system processes location requirements for the cargo
Then Location information is assigned to the X4 segment
R-GCX016E-cbl-02790 Initialize N7 Segment Array
Process Rules
📊 Business Logic Narrative
When the process 'Initialize N7 Segment Array' is invoked, and assuming that cargo processing requires equipment data handling, when the system begins n7 segment initialization, the desired outcome is that the n7 segment array is initialized with proper structure and default values.
💻 Technical Criteria
Given Cargo processing requires equipment data handling
When The system begins N7 segment initialization
Then The N7 segment array is initialized with proper structure and default values
R-GCX016E-cbl-02791 Set Equipment ID in N7
Action Rules
📊 Business Logic Narrative
When the process 'Set Equipment ID in N7' is invoked, and assuming that an n7 segment is initialized and equipment id data is available, when the system processes equipment identification for the cargo, the desired outcome is that equipment id is populated into the n7 segment.
💻 Technical Criteria
Given An N7 segment is initialized and equipment ID data is available
When The system processes equipment identification for the cargo
Then Equipment ID is populated into the N7 segment
R-GCX016E-cbl-02792 Set Equipment Type in N7
Action Rules
📊 Business Logic Narrative
When the process 'Set Equipment Type in N7' is invoked, and assuming that an n7 segment is being populated and equipment type data is available, when the system processes equipment classification for the cargo, the desired outcome is that equipment type is assigned to the n7 segment.
💻 Technical Criteria
Given An N7 segment is being populated and equipment type data is available
When The system processes equipment classification for the cargo
Then Equipment type is assigned to the N7 segment
R-GCX016E-cbl-02793 Set Quantity Information in N7
Action Rules
📊 Business Logic Narrative
When the process 'Set Quantity Information in N7' is invoked, and assuming that an n7 segment is being populated and quantity data is available, when the system processes cargo quantity information, the desired outcome is that quantity information is populated into the n7 segment.
💻 Technical Criteria
Given An N7 segment is being populated and quantity data is available
When The system processes cargo quantity information
Then Quantity information is populated into the N7 segment
R-GCX016E-cbl-02794 Set Weight Information in N7
Action Rules
📊 Business Logic Narrative
When the process 'Set Weight Information in N7' is invoked, and assuming that an n7 segment is being populated and weight data is available, when the system processes cargo weight information, the desired outcome is that weight information is assigned to the n7 segment.
💻 Technical Criteria
Given An N7 segment is being populated and weight data is available
When The system processes cargo weight information
Then Weight information is assigned to the N7 segment
R-GCX016E-cbl-02796 Validate Segment Data
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Segment Data' is invoked, and assuming that x4 and n7 segments have been populated with cargo and equipment data, when the system performs data validation on the segments, the desired outcome is that all required data elements are verified for completeness and accuracy.
💻 Technical Criteria
Given X4 and N7 segments have been populated with cargo and equipment data
When The system performs data validation on the segments
Then All required data elements are verified for completeness and accuracy
R-GCX016E-cbl-02798 Mark Segments Ready for Processing
Action Rules
📊 Business Logic Narrative
When the process 'Mark Segments Ready for Processing' is invoked, and assuming that segment data validation has been successful, when the system processes the validation success outcome, the desired outcome is that x4 and n7 segments are marked as ready for cargo processing.
💻 Technical Criteria
Given Segment data validation has been successful
When The system processes the validation success outcome
Then X4 and N7 segments are marked as ready for cargo processing
R-GCX016E-cbl-02802 Return to Cargo Processing
Process Rules
📊 Business Logic Narrative
When the process 'Return to Cargo Processing' is invoked, and assuming that message array initialization process has completed (either successfully or with errors), when the system finishes the initialization workflow, the desired outcome is that control is returned to the main cargo processing workflow.
💻 Technical Criteria
Given Message array initialization process has completed (either successfully or with errors)
When The system finishes the initialization workflow
Then Control is returned to the main cargo processing workflow
R-GCX016E-cbl-02823 Format Equipment Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment Information' is invoked, and assuming that a cargo record with equipment information exists, when the system processes merlin report field formatting, the desired outcome is that the equipment information is formatted and prepared for report inclusion.
💻 Technical Criteria
Given A cargo record with equipment information exists
When The system processes Merlin report field formatting
Then The equipment information is formatted and prepared for report inclusion
R-GCX016E-cbl-02824 Format Car ID
Computation Rules
📊 Business Logic Narrative
When the process 'Format Car ID' is invoked, and assuming that a cargo record contains car id information, when the car id formatting process is executed, the desired outcome is that the car id is formatted with appropriate spacing and alignment for report display.
💻 Technical Criteria
Given A cargo record contains car ID information
When The car ID formatting process is executed
Then The car ID is formatted with appropriate spacing and alignment for report display
R-GCX016E-cbl-02827 Format Disposition Code Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Disposition Code Information' is invoked, and assuming that a disposition code exists for the cargo, when the disposition code information formatting is processed, the desired outcome is that the disposition code and its description are retrieved and formatted for report inclusion.
💻 Technical Criteria
Given A disposition code exists for the cargo
When The disposition code information formatting is processed
Then The disposition code and its description are retrieved and formatted for report inclusion
R-GCX016E-cbl-02828 Retrieve Disposition Code
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Disposition Code' is invoked, and assuming that a cargo is being processed with a disposition code, when the disposition code retrieval is executed, the desired outcome is that the current disposition code is retrieved from the processing context.
💻 Technical Criteria
Given A cargo is being processed with a disposition code
When The disposition code retrieval is executed
Then The current disposition code is retrieved from the processing context
R-GCX016E-cbl-02830 Format Date/Time Information
Computation Rules
📊 Business Logic Narrative
When the process 'Format Date/Time Information' is invoked, and assuming that processing timestamps are available for the cargo, when the date/time formatting process is executed, the desired outcome is that the date and time information is formatted for consistent display in the report.
💻 Technical Criteria
Given Processing timestamps are available for the cargo
When The date/time formatting process is executed
Then The date and time information is formatted for consistent display in the report
R-GCX016E-cbl-02833 Apply Release Quantity Impact Logic
Decision Rules
📊 Business Logic Narrative
When the process 'Apply Release Quantity Impact Logic' is invoked, and assuming that a disposition code is being processed for a cargo, when the release quantity impact logic is applied, the desired outcome is that the system determines if the disposition code affects release quantities.
💻 Technical Criteria
Given A disposition code is being processed for a cargo
When The release quantity impact logic is applied
Then The system determines if the disposition code affects release quantities
R-GCX016E-cbl-02840 Retrieve In-Bond Type Code from Cargo
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve In-Bond Type Code from Cargo' is invoked, and assuming that a valid shiproot record exists and cargo records are available, when the system retrieves in-bond type code from the cargo record, the desired outcome is that the in-bond type code should be extracted from the cargo record and made available for u1 segment population.
💻 Technical Criteria
Given A valid shiproot record exists and cargo records are available
When The system retrieves in-bond type code from the cargo record
Then The in-bond type code should be extracted from the cargo record and made available for U1 segment population
R-GCX016E-cbl-02841 Extract Entry Number Information
Action Rules
📊 Business Logic Narrative
When the process 'Extract Entry Number Information' is invoked, and assuming that in-bond type code has been successfully retrieved from cargo records, when the system extracts entry number information from cargo records, the desired outcome is that entry number information should be extracted and prepared for u1 segment population.
💻 Technical Criteria
Given In-bond type code has been successfully retrieved from cargo records
When The system extracts entry number information from cargo records
Then Entry number information should be extracted and prepared for U1 segment population
R-GCX016E-cbl-02852 Extract Equipment ID from US Cargo
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment ID from US Cargo' is invoked, and assuming that a us cargo record exists with equipment information, when the system processes the cargo for canadian manifest matching, the desired outcome is that the equipment id is extracted and formatted for canadian system lookup.
💻 Technical Criteria
Given A US cargo record exists with equipment information
When The system processes the cargo for Canadian manifest matching
Then The equipment ID is extracted and formatted for Canadian system lookup
R-GCX016E-cbl-02853 Search Canadian Cargo Database
Action Rules
📊 Business Logic Narrative
When the process 'Search Canadian Cargo Database' is invoked, and assuming that an equipment id has been extracted from us cargo, when the system searches the canadian cargo database, the desired outcome is that all canadian cargo records with matching equipment id are retrieved.
💻 Technical Criteria
Given An equipment ID has been extracted from US cargo
When The system searches the Canadian cargo database
Then All Canadian cargo records with matching equipment ID are retrieved
R-GCX016E-cbl-02854 Canadian Cargo Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Canadian Cargo Found?' is invoked, and assuming that a search has been performed on the canadian cargo database, when the system evaluates the search results, the desired outcome is that the system determines if canadian cargo was found or not found.
💻 Technical Criteria
Given A search has been performed on the Canadian cargo database
When The system evaluates the search results
Then The system determines if Canadian cargo was found or not found
R-GCX016E-cbl-02855 Validate Canadian Cargo Status
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Canadian Cargo Status' is invoked, and assuming that canadian cargo records have been found for the equipment id, when the system validates the cargo status, the desired outcome is that the cargo status is checked to ensure it is not deleted or marked as new bond created.
💻 Technical Criteria
Given Canadian cargo records have been found for the equipment ID
When The system validates the cargo status
Then The cargo status is checked to ensure it is not deleted or marked as new bond created
R-GCX016E-cbl-02856 Status Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Status Valid?' is invoked, and assuming that canadian cargo status has been retrieved and validated, when the system determines status validity, the desired outcome is that the status is classified as valid, deleted, or new bond created based on cargo state.
💻 Technical Criteria
Given Canadian cargo status has been retrieved and validated
When The system determines status validity
Then The status is classified as valid, deleted, or new bond created based on cargo state
R-GCX016E-cbl-02857 Match Equipment IDs Between Systems
Process Rules
📊 Business Logic Narrative
When the process 'Match Equipment IDs Between Systems' is invoked, and assuming that valid canadian cargo has been found with matching equipment id, when the system matches equipment ids between systems, the desired outcome is that equipment id correspondence is established between us and canadian cargo records.
💻 Technical Criteria
Given Valid Canadian cargo has been found with matching equipment ID
When The system matches equipment IDs between systems
Then Equipment ID correspondence is established between US and Canadian cargo records
R-GCX016E-cbl-02858 Create Cross-Border Tracking Link
Action Rules
📊 Business Logic Narrative
When the process 'Create Cross-Border Tracking Link' is invoked, and assuming that equipment ids have been successfully matched between systems, when the system creates cross-border tracking links, the desired outcome is that a tracking relationship is established linking us and canadian cargo records.
💻 Technical Criteria
Given Equipment IDs have been successfully matched between systems
When The system creates cross-border tracking links
Then A tracking relationship is established linking US and Canadian cargo records
R-GCX016E-cbl-02859 Log Canadian Manifest Match
Process Rules
📊 Business Logic Narrative
When the process 'Log Canadian Manifest Match' is invoked, and assuming that cross-border tracking links have been created successfully, when the system logs the manifest match, the desired outcome is that match results are recorded with cargo details and timestamp information.
💻 Technical Criteria
Given Cross-border tracking links have been created successfully
When The system logs the manifest match
Then Match results are recorded with cargo details and timestamp information
R-GCX016E-cbl-02860 Exclude Deleted Cargo Records
Validation Rules
📊 Business Logic Narrative
When the process 'Exclude Deleted Cargo Records' is invoked, and assuming that canadian cargo records have been found but have invalid deleted status, when the system processes cargo status validation, the desired outcome is that deleted cargo records are excluded from further cross-border processing.
💻 Technical Criteria
Given Canadian cargo records have been found but have invalid deleted status
When The system processes cargo status validation
Then Deleted cargo records are excluded from further cross-border processing
R-GCX016E-cbl-02861 Exclude New Bond Created Records
Validation Rules
📊 Business Logic Narrative
When the process 'Exclude New Bond Created Records' is invoked, and assuming that canadian cargo records have been found but have invalid new bond created status, when the system processes cargo status validation, the desired outcome is that new bond created cargo records are excluded from further cross-border processing.
💻 Technical Criteria
Given Canadian cargo records have been found but have invalid new bond created status
When The system processes cargo status validation
Then New bond created cargo records are excluded from further cross-border processing
R-GCX016E-cbl-02862 Update Cargo with Canadian Reference
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo with Canadian Reference' is invoked, and assuming that valid canadian cargo has been matched and cross-border links created, when the system updates us cargo with canadian reference, the desired outcome is that us cargo record is updated with canadian manifest reference information.
💻 Technical Criteria
Given Valid Canadian cargo has been matched and cross-border links created
When The system updates US cargo with Canadian reference
Then US cargo record is updated with Canadian manifest reference information
R-GCX016E-cbl-02863 Generate Cross-Border Audit Trail
Process Rules
📊 Business Logic Narrative
When the process 'Generate Cross-Border Audit Trail' is invoked, and assuming that us cargo has been updated with canadian reference information, when the system generates cross-border audit trail, the desired outcome is that audit records are created documenting the cross-border manifest matching process.
💻 Technical Criteria
Given US cargo has been updated with Canadian reference information
When The system generates cross-border audit trail
Then Audit records are created documenting the cross-border manifest matching process
R-GCX016E-cbl-02864 No Canadian Manifest Found
Process Rules
📊 Business Logic Narrative
When the process 'No Canadian Manifest Found' is invoked, and assuming that no canadian cargo records were found matching the equipment id, when the system processes the no match scenario, the desired outcome is that the system proceeds to log search results without creating cross-border links.
💻 Technical Criteria
Given No Canadian cargo records were found matching the equipment ID
When The system processes the no match scenario
Then The system proceeds to log search results without creating cross-border links
R-GCX016E-cbl-02865 Log Search Results
Process Rules
📊 Business Logic Narrative
When the process 'Log Search Results' is invoked, and assuming that canadian manifest search has been completed with either match or no match results, when the system logs search results, the desired outcome is that search outcome is recorded with equipment id and result status information.
💻 Technical Criteria
Given Canadian manifest search has been completed with either match or no match results
When The system logs search results
Then Search outcome is recorded with equipment ID and result status information