Date: Thu, 28 Mar 2024 03:29:20 -0500 (CDT) Message-ID: <1867200447.1.1711614560347@slrs01vf4p1cn02.as.ad.digital.accenture.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_0_1026619763.1711614560312" ------=_Part_0_1026619763.1711614560312 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Workflow is divided into two parts: the Workflow Library an= d the Workflow Tree.
In the Workflow Library you can fin= d applications and rules to create your own business rules, just by draggin= g and dropping into the Workflow Tree; all stored in a collap= sible menu divided by categories. In the workflow we can find two types of = rules.
The available Publishers, Applications and Big Data may change according= to your entitlements
The folder is used to group a set of rules into one branch which later c= an be moved, shared or disabled.
With the Publishers you can publish the jobs coming f= rom the connector and into a search engine, each publisher must be configur= e before it's added as a application rule. They are all downloadable java a= pplications.
The Applications are used to modify the jobs coming f= rom connector in a more complex way that a simple Groovy script could had d= one. They are all downloadable java applications.
The Big Data category holds all the big data related = applications such as Co-occurren= ce, Hadoop Job Launcher, among others.
The Base Functions are scripting rules base on Groovy= that can do simple functions to the jobs, it also has rules that can skip = or stop the process of a job in the workflow. You can also create your own = custom rules.
The Choices are scripting rules base on Groovy that a= llow us to create branches in the workflow base on a decision, this branche= s are only be executed by the jobs that comply with the made decision.
The Local Library category, holds all the rules used in the current work= flow, even the shared rules used in the workflow. Dragging the rul= es from this category will just create a reference to the existent rule&nbs= p;
The Shared Libraries are sets of rules and applicatio= ns we save to use with other content sources. If a rule or application is n= ot in a share rule, we can't use it again in another content source.
This section walks through the steps necessary to share any rule or appl= ication with the enabled menu.
You can delete a shared rule by clicking on the trashcan next to the nam= e of the rule in the Workflow Library
The share library may change position if we have several shared librarie= s, this is because is going to sorted by alphabetical order.
If you already have a share library and you want to add a new rule or ap= plication to it, repeat Step 1 and instead of cl= icking over New Library we can click over the name of ou= r library, this will add the rule or application automatically.
The Workflow Trees represent specific point in the information = flow, they are stages in which the jobs are processed before they are sent = to the next one. The root node of each tree is always going to be named as = the stage it represents. We have 5 trees for the content source:
* The workflow trees are saved with every change you made, they are = independent from the Save button
<=
/p>
The controls for the Workflow Tree ar= e explained in the Admin UI Content Sources. B= ut the most important control for the Workflow tree is the Tre= e Selection. With this control we can select the tree we want to modif= y, and we can see it in a representation of the information flow, also we c= an see the description of each tree just by putting the mouse over the butt= on. The current tree will be highlighted in green
For some rules there are some restrictions of which rules can contain wh= ich one, in the list below we can see which rules can contain which types o= f rules.
Root
Folder
Condition
Choices
This section walks through the steps necessary to add any rule or applic= ation to the Workflow Tree.
You can add any rule or application just by dragging the rule from the <= em>Workflow Library and dropping it in the part of the Workflow Tr= ee you want to put the rule or application.
If the rule needs to be configured, it will open a window with all the c= onfiguration properties, otherwise it just will appear in the tree. If a wi= ndow is opened just fill the necessary properties and click on the Add<= /em> button to create the rule.
By double clicking the rule on the tree, we can open the window it the c= urrent properties of the rule. Then we can change the properties and save t= hem by clicking on the Update button.
The Context Menu has several option to manage the business rule= s:
This includes the Publishers, for which= all related information can be found on this page, Applications th= at at the moment includes the Hierarch= y Extractor and Mime Type Normalizer, and Big Data.
By dragging and dropping the Custom option of publish= ers or applications, you will open a window from which you can choose betwe= en two methods to install a custom application, publisher or big data, = repository and configuration file, both shown as tabs on the top of the window.
The repository method is always the default one, with this option we can= download the custom application, publisher or big data from a maven reposi= tory. To install the custom application, publisher or big data you nee= d to fill the following fields:
Before accessing the configuration file method an alert will be show ind= icating that the application/publisher added using this method are not goin= g to be included in the respective category in the Workflow Librar= y.
The configuration files method requires to have both application file an= d dxf file (in this format <application>-dxf.xml) in the sam= e folder on the server machine. To install the custom application= , publisher or big data you need to fill the following fields:
After you have all of the necessary fields, click on continue and the ap= plication will be loaded in the same window.
If the dxf file doesn't have the new valid format for applicat= ion, publisher or big data, it won't be possible to = open the configuration.
By dragging and dropping the Custom= option of Base Functions, you will open a window where = we can add you own groovy script to manipulate the jobs.
To add the custom script you need to fill th= e following fields:
= Groovy Script with Twilight Theme