Add content pages to content areas

You must at least add one content page to the content area.

1. Right-click the content area node in the explorer and select Create New Content Page.
2. Click the new content page in the explorer and define the following:
   • Caption: Enter the text displayed in the tab for the content page.
   • Description: Enter a description that will be displayed as a tooltip on the Alfabet user interface in the selector to hide and show content pages in a content area.
   • Name: Change the name to a meaningful name that helps you to identify the content page in the explorer.
   • Base Object Query: Optionally, you can define a query to determine a base object for a content page which is added to any kind of content area. For example, you can add information about the current user to the class-independent start content area of a user profile. In class-based content areas, the base object definition of the content page supersedes the base object definition of the content area. You can, for example, add content pages with information about the source and target application to the content area of an information flow, or information about the object a workflow is about to the content area of a workflow step.
     • The query can be defined in Alfabet query language or in native SQL. An Alfabet query builder is not available. The query must be defined in a text editor.
     • The query must return the REFSTR of a single object. Any additional data about the object is ignored.

       The following query changes the base object for a content page in the class-based content area of an information flow to the source application of the information flow.

       • SELECT app.REFSTR
       • FROM APPLICATION app
       • INNER JOIN INFORMATIONFLOW inf ON inf.A_FROM = app.REFSTR
       • WHERE inf.REFSTR = @BASE
     • You can use Alfabet parameters referring to the current environment in the query. The Alfabet parameter @BASE can be used in class-based content areas to refer to the base object of the content area. The Alfabet parameter @WORKFLOWBASE can be used in class-based content areas of workflows and workflow steps to refer to the base object of the workflow.

       The following query defines the current user as base object for a content page in a class-independent content area:

       • SELECT pers.REFSTR
       • FROM PERSON pers
       • WHERE pers.REFSTR = @CURRENT_USER
   • Allow Moving Content Page Items: Set this attribute to False if users should not be able to re-size and move the content items on the content page.
   • Sort Content Page Buttons: You can use this attribute to sort custom button after you have added them to the content page.
   • Sort Content Page Items: You can use this attribute to sort content items on the page after having added content items.
   • Default Visibility:Set the attribute to Hidden if the content page shall not be visible directly in the content area but only available via the content repository.

     For customers migrating from Alfabet 11.8 to Alfabet 11.11 the attribute will be set to Hidden for content pages which were in Alfabet 11.8 available in the configuration in Alfabet Expand but hidden in the default configuration.

   • Visibility Conditions: If you want the content page to be only visible under specific circumstances, you can define a condition element testing whether the specific circumstances apply. You can then select the condition element in this attribute. The content page will be visible if the condition applies. For example, a condition specifies that the content page shall only be visible for users in user group B. The condition checks the user group configuration for the current user at runtime and hides the content page if the user is not a member of user group B.