Version: eXtendOrders 2.1.69 and above
Audience: Administrator
Overview
Configuration
The IMC caching system requires three main components to be configured:
1. Script Deployment Setup
Navigate to Customization → Scripting → Scripts
Locate the workflow action script: eXtendOrders Set IMC Cache Data
Ensure the following script deployment has been created:
- Record Type: eXtend IMC Imprint Method Configuration
- Status: Released
- Log Level: Audit or Error
- Audience: All roles
- Record Type: eXtend IMC Imprint Method Configuration
2. Workflow Configuration
- Access the active workflows for eXtend IMC Imprint Method Configuration record type
- Locate the workflow: eXtendOrders Create/Update IMC Cache[B]
- Ensure the workflow is running and that it contains the "eXtendOrders Set IMC Cache Data" workflow action
3. Map/Reduce Script Scheduling
- Navigate to Customization → Scripting → Scripts
- Locate the script: eXtendOrders Set IMC Cache Data MR
- Create or update the scheduled deployment
- Note: There is an unscheduled deployment present that shouldn't be modified
- Name: eXtendOrders Set IMC Cache Data MR[DNS]
- ID: customdeploy_extend_orders_imc_cache_dns
- We recommend running this weekly during off-peak hours for most environments
Frequently Asked Questions (FAQs)
Q: What happens if the IMC cache becomes outdated?
A: The Map/Reduce script refreshes the cache during its next scheduled run. For immediate updates, the workflow action script handles real-time changes when IMC records are modified.
Q: Do I need to enable any specific preferences for IMC imports?
A: Yes. Enable the "Run Server SuiteScript and trigger WorkFlows" preference when importing IMC records to ensure proper cache updates.
Q: What happens when an IMC record is inactivated?
A: The "eXtendOrders Set IMC Cache Data" workflow automatically updates the cache to reflect the inactivation.
Q: What happens if an IMC record is deleted?
A: We recommend inactivating the IMC record instead of deleting it. However, if deletion is necessary, create another version of the eXtendOrders Create/Update IMC Cache[B] workflow that runs After Record Submit to handle IMC record deletions. The base workflow handles creations, edits, and inactivation in a Before Record Submit context, which isn't valid for deletions—the record won't exist when the workflow runs. The scheduled eXtendOrders Set IMC Cache Data MR Map/Reduce script will also handle this scenario, but the workflow is recommended if you need a real-time update to refresh the cache immediately after deletion.