Manage Trading Community Messages Setup Task Guidance
Purpose
Provide a task-specific entry point for Manage Trading Community Messages
under Trading Community Foundation, then delegate the manual execution
workflow to shared.common.manual-tasks.
Setup Task Skill Contract
- task_code:
ORA_HZ_MANAGE_MESSAGES - task_name:
Manage Trading Community Messages - parent_skill_id:
cx.customer-data-management.trading-community-foundation - pillar:
CX - offering:
Customer Data Management - functional_area:
Trading Community Foundation - functional_area_code:
ORA_HZ_CDM_FOUNDATION - available_flag:
Y - export_import_supported_flag:
Y - csv_export_import_supported_flag:
N - dataloader_import_mode:
REST - businessObject: ``
- source_catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Usage
Use this skill when a user wants to create, modify, delete, translate, or validate a Trading Community message or its tokens.
Setup Task Metadata
- Task name:
Manage Trading Community Messages - Task code:
ORA_HZ_MANAGE_MESSAGES - Available:
Y - Export/import supported:
Y - CSV export/import supported:
N - CSV export/import routing:
not supported - Data Loader import mode:
REST(inactive generator compatibility metadata) - Business Object: ``
Execution Route
Invoke shared.common.manual-tasks with:
manual_task_name=Manage Trading Community Messages- the user's exact
approved_configuration_change - the exact
target_environment
This authored body route is the task's operative dependency. The generated
frontmatter remains catalog-owned so a later pillar-skill-gen refresh
preserves this guidance instead of creating a competing generated route.
The shared skill must tell the user how to perform the approved change manually in Fusion. It must not open Fusion or perform the change on the user's behalf.
Automation Boundary
CSVExportImportSupportedFlag is N. The generated
dataloader_import_mode: REST value is non-operative compatibility metadata:
there is no registered businessObject, and it does not authorize a REST
call.
Do not route this task through:
core.data-loader- task-level FSM CSV export or import
- UCM, ESS, HDL, FBDI, CX Import, or spreadsheet loaders
- public, private, or inferred REST or SOAP endpoints
- browser automation or direct UI control
Do not reinterpret ExportImportSupportedFlag=Y as proof of an executable
route. No export or import workflow is selected for this skill.
Manual Message Guidance
Use Oracle's current Manage Messages behavior as the field-level guide after the user opens Manage Trading Community Messages through Setup and Maintenance:
- Search for the exact existing message, or create a message only when that is the approved change.
- For a new message, use a unique message name and the application/module appropriate to the approved Trading Community requirement.
- For predefined messages, do not change the predefined message number.
- Preserve seeded messages unless the approved design and documented task behavior allow the change. Do not delete a predefined message merely because it appears unused.
- Save the change manually.
Oracle references:
Tokens
When the approved message requires runtime values:
- Define the token while editing the message.
- Use a unique uppercase name inside curly braces, with underscores between
words and no spaces, for example
{PARTY_NUMBER}. - Select the documented token data type:
Text,Number, orDate. - Add a description explaining the runtime value.
- Do not edit or delete predefined tokens.
- Validate that the calling Trading Community flow supplies the value; creating a token definition alone does not bind application code to it.
Oracle reference: Use of Tokens in Messages.
Translations
Use the Translation Editor exposed by the manual message page for enabled languages. Preserve the intended meaning, tokens, cause, and user action in each translation. Do not claim translation completion until the user verifies the applicable language behavior.
Manual Verification
After the user reports saving the change:
- Ask for the message identifier or description and the target environment.
- Have the user reopen the message and confirm the saved fields and tokens.
- Have the user trigger the relevant Trading Community validation with safe test data and verify the rendered text and dynamic values.
- Check that no unintended validation behavior changed.
- Report
manual verification pendinguntil the user confirms the readback or runtime result. Never report automated execution success.
Inputs
implementation_objectiveproject_contextsetup_task_scopesetup_data_artifacts
Outputs
setup_task_plansetup_data_routingvalidation_checkpointsskill_run_recordtoken_usage_record
Implementation Notes
Use the parent functional-area skill
cx.customer-data-management.trading-community-foundation for functional-area
sequencing. Use shared.common.manual-tasks for execution guidance. Track
token usage for any generated project artifact or skill-run record using the
manifest policy.