My Oracle Support Banner

When creating a Macro, the changes done in the Model are not reflected in the spreadsheet (Doc ID 880846.1)

Last updated on MARCH 27, 2020

Applies to:

Oracle Business Process Analysis Suite - Version and later
Information in this document applies to any platform.


While There are changes done in the model, for example using a customized attribute (with the name changed) assigned to an object, when the macro is started and an excel spreadsheet is created, it doesn't keep the name just created, and it uses the original value (i.e: User Attribute Text 1).

In a BPA model you are changing the name of a customized attribute or combo box.
Start a macro to get model details and in the created excel spreadsheet the original value name is used and not the new changed one, for example : User Attribute Text 1 instead of MyNewAttribute.

Simple example steps to reproduce:

1- Create a UML Use case diagram
2- Drag and drop an Actor.
3- Drag and drop use cases
4- Link all the use cases to the actor (Picture 1)
5- Change the name of an attribute by doing the following:
a- Go to Administration tab
b- Go to Attribute types
c- Select User Attribute Text 1 and rename it to any name.
6- Select one of the use cases in the diagram and add the attribute just created
6- Select one of the use cases, and press start macro
7- Accept the default values pressing Next-> finish
8- An excel spreadsheet will be created
9- The problem resides that the value of the Attribute is the original value, not the name of the
attribute just assigned.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.