Adobe Captivate - Oracle



Slide 1 - Oracle Order Management Cloud

[pic]

Slide notes

Hello, my name is Al. Welcome to training for Configurator Cloud, in the Oracle Order Management Cloud.

In this session, we talk about how configurator modelers can unrelease in advertent changes to their models from production and revert to a prior release of their model definition.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 2 - Agenda

[pic]

Slide notes

For the capabilities covered in this training, we’ll give an overview, followed by more detail to explain how you can use them, and what business value they bring.

Then, we’ll walk you through a demonstration.

Next we’ll explain what you need to consider when the feature is enabled for your business and any related setup that's required.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 3 - Unrelease Models from Production

[pic]

Slide notes

This new capability will enable you to unrelease the latest version of a model in production using a REST service call, and revert back to the previously released version of the model.

Changes made to the model being unreleased are preserved in a new workspace, for future edits and subsequent release

And finally, any draft versions of the model currently under development, will be re-baselined to the prior released version of the model, to ensure development consistency.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 4 - Unrelease Models from Production

[pic]

Slide notes

The Configurator Cloud now provides an additional safeguard to users when unwanted changes to a model are released to production.

Without this feature, you might inadvertently release a model into production, and then scramble to correct the changes, test them, and then re-release the model, which could take significant time and effort. In the interim, in valid orders may be submitted, further compounding the problem.

With the ability to now unrelease models from production, modelers can quickly revert to the prior released version of a model when unwanted changes are released, allowing business operations to continue with minimal impact.

Notes

| |

| |

| |

| |

| |

| |

| |

Slide 6 - Additional Information when Unreleasing Models from Production

[pic]

Slide notes

Here're some important considerations when planning to use this feature:

It’s important to note that the unrelease operation is limited to models in a workspace without any snapshots in them.

Models can't be unreleased unless all its referring models are also unreleased in the same action.

And finally, the unrelease operation is limited to future-effective models. Models released with a past-effective start date cannot be unreleased.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 7 - Implementation Advice

[pic]

Slide notes

In this section, we provide implementation and uptake considerations for the feature.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 8 - Unrelease Models from Production Impact

[pic]

Slide notes

The “Unrelease Models from Production” feature is Ready to Use by End Users, and is delivered enabled.

Access to this feature is through the Configurator Workspace Release privilege.

And the business process affected by this feature is Manage Configurator Models.

This concludes this presentation. Thank you for listening. You can easily pause and rewind if you require additional time to take in the detail.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download