Table 3-2 lists the actions you can audit in Portal Studio.
Asset types |
Action name |
Action description |
|---|---|---|
STUDIO.Applications |
Studio.Create |
Creating a new application. Triggers page and page group add and update actions, which occur immediately, bypassing the deferupdate global setting only for the current user. |
STUDIO.AutoFillAdapter |
Studio.Create |
When an autofill adapter is created using Manage | Personalize | Adapter, the adapterType attribute in the audit records shows the adapter type. |
Studio.Delete |
Deleting a personalization adapter. |
|
Studio.Update |
Clicking Edit in Adapter Builder. |
|
STUDIO.Catalogs |
Studio.Create |
Creating a new catalog or saving an existing catalog. If the “requested catalog id” is zero, the catalog was newly created. Does not audit the portlets added to the catalog |
Studio.Update |
Clicking Update Catalog. |
|
STUDIO.Objects |
Studio.Deploy |
Clicking Deploy and performing deploy operation. All Studio objects deployed (saved to .ear file) are audited as attributes |
Studio.Export |
Clicking Deploy and performing export operation. All the objects exported (saved to .xml file) are audited as attributes. The log content is listed as an attribute. |
|
Studio.Import |
Clicking Deploy and performing import operation. All the objects imported (from the .xml file) are audited as attributes, which may trigger the page and page group update actions. |
|
STUDIO.PageGroups |
Studio.Create |
Creating a new page group or saving an existing page group. If the “requested page group id” is zero in the audit record, the page group was newly created. Does not audit pages and portlets added to the page group. |
Studio.Update |
Clicking Update. If the global property deferupdate is turned on, the update happens when the user logs in; otherwise, the update occurs immediately. Either way, the audit record is generated. When the update happens, it triggers page and page group deletions and portlet additions. |
|
STUDIO.Pages |
Studio.Create |
Creating a new page or saving an existing page. If the “requested page id” is zero in the audit record, the page was newly created. Does not audit portlets added to the page. |
Studio.Update |
Clicking Update. If the global property deferupdate is turned on, the update happens when the user logs in; otherwise, the update occurs immediately. Either way, the audit record is generated. When the update happens, it triggers page and page group deletions and portlet additions. |
|
STUDIO.Portlets |
Studio.Create |
Creating a new portlet or saving an existing portlet. |
Studio.Preview |
Clicking Preview in Portlet Builder. The portlet preview is audited when a valid portlet ID is passed to UWPWindowApp.GetWindowContent. |
|
Studio.Search Replace (one word) |
Performing a search and replace action on a portlet. The pages and catalogs affected are listed as attributes in the audit record. If Update Pages is selected, this action also triggers the page and page group update action and audit. |
|
STUDIO.Resources |
Studio.Create |
Creating a new resource ID. |
Studio.Delete |
Deleting or undeleting a resource. Deleting a resource ID does not physically delete the resource; the resource is just marked for deletion from the database. |
|
Studio.Update |
Clicking Edit in the Resource Builder. |
|
STUDIO.Roles |
Studio.Create |
Creating a J2EE role reference. |
Studio.Delete |
Deleting a J2EE role reference. |
|
Studio.Update |
Clicking Edit in the Role Builder. If you “undelete” a J2EE role, an update action is generated. |
|
STUDIO.Templates |
Studio.Create |
Creating a new template or saving an existing template. |
Studio.Preview |
Clicking Preview in Template Builder. |
