| |
Results |
|
EXPM dumps out the request templates of products which are nothing to do with the process model of the product exported
|
EXPM dumps out the request templates of products which are nothing to do with the process model of the product exported
|
|
|
|
KM-Dim9: How to Export a Product's Process Model
|
What you need: The name of the Product . The base database and base database password for the base database containing the product.
|
|
|
|
KM-Dim7: message 206 not found. no message file for product rdbms, facility=exp: release n.n.n.n.n
|
KM-Dim7: message 206 not found. no message file for product rdbms, facility= exp : release n.n.n.n.n
|
|
|
|
What is the Export Classification Control number for Serena Products?
|
Product Classification ECCN
|
|
|
|
KM-Dim9: What the base database exports contains?
|
Base Database exports contain $GENERIC product , lifecycles, attribute definitions, update rules, roles and other control plan information. They do not include item revisions, worksets, baselines, users or change documents.
|
|
|
|
“Use Legacy Product Name” Registry Setting for Synchronous Orchestrations
|
Starting with SBM 11.2 , Composer now exports the product name to the WSDL during synchronous orchestration events. In previous releases, the service name was exported instead.
|
|
|
|
Projects On Demand Task Plan Export Instructions
|
Projects On Demand (POD) customers may want to continue working with the task plan information that is stored in POD after the POD service is ended. POD allows customers to export task plans which can then be imported into our free open source OpenProj product or into Microsoft Project.
|
|
|
|
KM-Dim10: Exporting the Design Part Structure from Desktop Client does not work with large number of objects
|
If you have a large amount of Design Parts in a product , in the example we used 28000, the option to save the Design Structure to an HTML file from Desktop Client doesn't work properly. A file will be created but only the top part will be present. Creating the output from smaller products works fine but we've yet to determine the threshold beyond which is fails to produce the report.
|
|
|
|
Dim10: DMDBA command EXPM based on product fails on UNIX
|
Running the EXPM command to export a process model fails when run on a UNIX system. On Windows it's fine.
|
|
|
|
non-Admin users get privilege errors trying to export items to another project
|
When non-Admin user tries to export items to a different project, he gets the following error: Insufficient privileges to import item into project < PRODUCT :PROJECT> at stage The Stage ID field for this item is blank in the Dimensions Client.
|
|
|
