Considerations When Using Page Composer and Application Composer Together
Application Composer is the recommended tool for configuring and extending PLM applications. Page Composer can’t be used with all PLM objects. If you attempt to add Page Composer-enabled configurations to existing Application Composer-enabled pages, such configurations can break during an update.
Let's look at PLM objects that you can configure using Page Composer.
Supported | Not Supported |
---|---|
You can configure the following PLM objects with Page Composer:
|
You can't configure the following objects with Page Composer:
|
You can use Page Composer to do some configurations for change orders, change requests, problem reports, and corrective actions. Use Page Composer to add components only within the tab regions of the predefined tabs like General Information, Affected Items, and Attachments.
However, you can't make changes to the tabs configured by Application Composer or the tab bar component itself. You can't add, rename, hide, delete, or modify the tabs. This is applicable for actions or buttons on the page.
Page Composer Configurations | Description and Examples |
---|---|
Rename or hide standard fields in the object pages. | Rename standard fields such as:
Note: You can use the Show Component
property on the Component Properties dialog box to show or hide
page components. |
Make the fields for standard attributes mandatory. | Make these fields mandatory:
|
Reorder the standard and previously configured fields. | Select the page and change the order in which the fields appear
in the Component Properties: panelFormLayout page. Add components to
the object. Some examples of components:
|
Use Expression Language to show or hide fields and their labels. | Add a condition using an expression to control the visibility of a component. If the condition is met, then the component is displayed, otherwise, the component isn’t displayed. |
Label and font changes, or any CSS changes. | Configure your page layout to define the number, placement, and
orientation of content regions. You can set the layout style while
creating a page or you can change the layout style even after adding
content to the page. Note: You can't change the
page layout for all pages. |
Add Action, Links, or Buttons. | Add an expression to the Change Status button to control the display of change orders and change requests. |
Validate the user entry in a field. | Display an error message if a value isn't entered for a specific field. You can do this, by selecting the Required check box on the Component Properties page, and entering the message that you want to display. |
Configure the Change Overview page. | Hide the Approve and Reject options in the My Worklist or My Changes on the Overview tab in the Product Development work area. |
Existing Page Composer Configuration | Additional Application Composer Configuration | Supported on Upgrade? |
---|---|---|
Button created on the General Information page to launch a PaaS application. | Action to launch a configured extension on the same page. | No |
Button created on the General Information page to launch a PaaS application. |
Groovy scripting that validates the presence of value in the Priority field of the General Information page after changes are saved. Groovy script that populates Tasks on the Task tab in the Edit Change Order page. |
Yes |
Attributes made mandatory using Page Composer on General Information page. | Configured action created using Application Composer on General Information page. | Yes |
Add hyperlinks to internal sites like confluence. | Configured button to perform Save As of certain aspects like General Information or Affected Object of the current object. | Yes |
If you've used Page Composer to configure buttons, actions, or tabs, avoid using Application Composer to make further changes to these, including adding expressions. Likewise, if you've modified buttons, actions, and tabs using Application Composer, don't use Page Composer to make additional configurations.