Skip to main content

ATG CA - different activity sources used @ BCC

Read about how a new link can be added in BCC home page @ http://tips4ufromsony.blogspot.com/2012/03/atg-ca-bcc-home-screen-how-to-add-new.html

Normally an ActivitySource.properties file define the set of actions that it supports under a genericActivityDefinitionFile. But some ActivitySource.properties  define the actions  using the workflowActivityDefinitionFiles.

For example consider the default "Content Administration" ,  "SearchAdministration",  " Merchanding "  and "Personalization" options in BCC homepage. Below I listed the ActivitySource.properties and other properties for these links. To get all these activitysource names, just take the /atg/bizui/activity/ActivityManager component @ dyn/admin.



Content Administration
ActivitySource  --> /atg/bizui/activity/PublishingActivitySource
genericActivityDefinitionFile


Search Administration
ActivitySource  --> /atg/bizui/activity/SearchingActivitySource
genericActivityDefinitionFile

Personalization
ActivitySource  -->  /atg/web/personalization/activity/PersonalizationActivitySource
workflowActivityDefinitionFiles  and genericActivityDefinitionFile

Merchanding
ActivitySource  -->  /atg/commerce/web/CommerceActivitySource
workflowActivityDefinitionFile

Consider the tasks under Merchandising,  Administer Commerce Search  and Manage Commerse Assets and a Browse option. These are defined in the workflowActivityDefinitionFile @ /atg/commerce/web/CommerceActivitySource. You could find the details in the below screen shot.



Also consider the tasks under Search Administration , these are defined  in the genericActivityDefinitionFile @ /atg/bizui/activity/SearchingActivitySource. You could find the details in the below screen shot.


The PublishingActivities.xml file is checked at intervals for modifications, so you can make changes to it without needing to restart the server. The interval is set to 5 minutes by default and is defined by the genericActivityFileModificationInterval property in the /atg/bizui/activity/PublishingActivitySource.properties component.

When you create a workflow in the ATG Control Center, it automatically displays in the ATG Business Control Center under Merchandising in the Operations list as long as you save the workflow in the /atg/registry/data/epubworkflows/Commerce directory. If you’d prefer to keep the workflow in a different directory, you need to update the /atg/commerce/web/CommerceActivitySource component workflowDirectories property to with the new directory name and path.

Labels:

Comments

  1. Anonymous25 September 2012 at 17:18

    Under Personalization there are 4 sub tasks Targeting and Segmentation, Preview Users, Internal Users, External Users. When i look into the xml /atg/web/personalization/activity/workflowActivities.xml i cannot see 4 activites.


    <workflow-activities>
    <activity>
    <id>personalization.editSegmentsAndTargeters</id>
    <workflow-name>/Common/commonWorkflow.wdl</workflow-name>
    <acl>Profile$role$epubAdmin:read;Profile$role$epubSuperAdmin:read;Profile$role$epubManager:read;Profile$role$epubUser:read;</acl>

    <resource-bundle>atg.web.personalization.WebAppResources</resource-bundle>
    <display-name-resource>personalization.editSegmentsAndTargeters.displayName</display-name-resource>
    <description-resource>personalization.editSegmentsAndTargeters.description</description-resource>

    <display-name-resource-2>personalization.editSegmentsAndTargeters.browse.displayName</display-name-resource-2>
    <description-resource-2>personalization.editSegmentsAndTargeters.browse.description</description-resource-2>
    <destination-page-2>
    <url>/AssetManager/assetManager.jsp</url>
    <activity-id>personalization.browseSegmentsAndTargeters</activity-id>
    <clear-context>true</clear-context>
    </destination-page-2>

    </activity>
    </workflow-activities>


    I need to add subtasks to my custom link created as per your previous post.

    Thanks

    ReplyDelete

Post a Comment

Popular posts from this blog

ATG - more about Forms and Form Handlers

An ATG form is defined by the dsp:form tag, which typically encloses DSP tags that specify form elements, such as dsp:input that provide direct access to Nucleus component properties. Find below a sample dsp:form tag.    <dsp:form action="/testPages/showPersonProperties.jsp" method="post" target="_top">      <p>Name: <dsp:input bean="/samples/Person.name" type="text"/>      <p>Age: <dsp:input bean="/samples/Person.age" type="text" value="30"/>      <p><dsp:input type="submit" bean="/samples/Person.submit"/> value="Click to submit"/>    </dsp:form>   When the user submits the form, the /samples/Person.name property is set to the value entered in the input field.Unlike standard HTML, which requires the name attribute for most input tags; the name attribute is optional for DSP form element tags. If an input tag omits the n...
11 comments
Read more

ATG Search - high level overview of product-catalog-output-config.xml and XHTMLs

The definition file format begins with a top-level item element that specifies the repository and item descriptor to use, and then lists the properties of that item type to include. The top-level item element has the is-document attribute set to true. This attribute specifies that an XHTML document should be generated for each item of that type (in this case, each user item). Property values that come from standard JavaBean properties of the RepositoryItem object (rather than dynamic bean properties) are specified using a dollar-sign ($) prefix. The item element has an is-multi attribute for specifying multi-value properties. If a property is an Array, Collection or Map  you should set this attribute to true. Eeach ATG Search document is uniquely identified by a URL (typically the path name of the file on the file system). In the XHTML documents that the ATG platform generates from repository items, meta properties are represented by meta tags in the head of the document, whi...
Post a Comment
Read more

Eclipse plug-in to create Class and Sequence diagrams

ModelGoon is an Eclipse plug-in avaiable for UML diagram generation from Java code. It can be used to generate Package Dependencies Diagram, Class Diagram, Interaction Diagram and Sequence Diagram. You coud get it from http://marketplace.eclipse.org/content/modelgoon-uml4java Read more about it and see some vedios about how to create the class and sequence diagram @ http://www.modelgoon.org/?tag=eclipse-plugin Find some snapshots below which gives an idea about the diagram generation.
8 comments
Read more

Google Chrome shortcut keys

If you are a Google Chromey guy, please find below the list of shortcut keys for some of the most used features  :-) Find more shortcut keys @  http://www.google.com/support/chrome/bin/static.py?page=guide.cs&guide=25799&topic=28650
4 comments
Read more

Eclipse Juno - good features of Eclipse 4.2 ( Eclipse Juno ) JDT/Workbench

Global search bar The workbench now has a global search field in the tool bar. Multi-drag sash You can now place the cursor at the intersection of two or more sashes and drag them all at the same time. When you are going to be dragging multiple sashes, the cursor will change to one with 4-way arrows. The image below indicates one such intersection with a red circle. Ant updated to 1.8.3 and JUnit to 4.10 The bundled version of Apache Ant in the platform has been updated to version 1.8.3. The JUnit 4 version shipped with Eclipse has been updated to 4.10. CamelCase in Quick Outline The Quick Outline (Ctrl+O) and Quick Hierarchy (Ctrl+T) in the Java Editor now also support camelCase matching on the element name, quite similar to the Open Type dialog and Content Assist. Quick Assist to convert enhanced for loop Ever encountered an enhanced for loop and needed access to the Iterator or to the loop index? Now, you can just use a Quick Assist (Ctrl+1)...
Post a Comment
Read more