Salesforce Known Issues
Trailblazer Community

Known Issues · sfi Communication Cloud - Order Management

List index out of bounds exception due to JSON string Parsing error

sfi Communication Cloud - Order Management

When you use an auto task(XOMAutoTaskInvokeIntegrationProcedure) in the orchestration Plan of V236.2.5 where the Product attribute is having the ,(Comma) getting an exception List index out of bounds exception due to JSON string Parsing error

In Review ·Reported By 1 ·Updated Today

most of the Queue layout fields shows “undefined”/ “unassigned” as text in the fields where there are no values

sfi Communication Cloud - Order Management

most of the Queue layout fields shows “undefined”/ “unassigned” as text in the fields where there are no values

In Review ·Reported By 1 ·Updated 7 days ago

Incorrect ContextId in 'Launch Omniscript' Manual Task Execution URL

sfi Communication Cloud - Order Management

ContextId not present in the Omniscript linked to a Orchestration Item of type Manual Task after upgraded to Vlocity version 900.456.2

In Review ·Reported By 0 ·Updated 13 days ago

View Orchestration Plan not working in 234.0

sfi Communication Cloud - Order Management

unable to view orchestration plan when in classic view 234.0 in all the lower sandboxes.

In Review ·Reported By 0 ·Updated 18 days ago

Install or upgrade of vlocity_cmt package versions 232.x,234.x , 236.x on Summer '22 Orgs fails with LWC errors

sfi Communication cloud - Cart API , sfi Communication Cloud - DC API , sfi Communication Cloud- EPC , sfi Communication Cloud - Order Management , sfi Communication Cloud - Express Application suites

Installing/ Upgrade of the CME core package versions 232.x,234.x , 236.x on a Summer fails with LWC Related errors. This is because Summer '22 LWC Framework enforces syntax and semantic rules. The fix is being actively worked on, to comply the LWC HTML with the Syntax.

Fixed in version 232.8.11,234.6.2,236.2.2 ·Reported By 0 ·Updated 21 days ago

Records missing in cache during a catalogue reload (OM+)

sfi Communication Cloud - Order Management

Records missing in cache during a catalogue reload(OM+)

Fixed in version OM Plus: cme-234.6.1-2 ·Reported By 0 ·Updated 2022-05-25

FRLs are not created for DISCONNECT scenario in multi-level decomposition

sfi Communication Cloud - Order Management

1.Create a Multi-level Decomposition order, use 'XOMAutoTaskStagedAssetizer' in the Orchestration plan to assetize. Multi level Decomposition relationships will be available when New order scenario executed. 2.FRLs are not created for DISCONNECT scenario in multi-level decomposition using item implementation...

No Fix ·Reported By 0 ·Updated 2022-05-19

In Cancel Order, 'Scheduled' Orchestration Item is not getting Discarded

sfi Communication Cloud - Order Management

An order is created with Orchestration plan containing a Callout with 'processAfter' set to a future date. Orchestration plan completed the tasks until this callout and it is set to 'Scheduled' state. At this situation, if the Order is cancelled, the Callout with 'Scheduled' state remains in 'Scheduled'...

In Review ·Reported By 1 ·Updated 2022-04-19

1 to 8 of 8

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.