Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

IT Business Analytics10.10

Content Customization Best Practices

This section provides the best practices for content customization.

Preparation

Take a snapshot of the Dev/QA environment before customization (the system doesn't support uninstalling content packs. If the customization fails, you can restore the back up and redeploy the latest content pack.)
Before each migration, make sure the Dev/QA/Production environment are the same.
If the customization content doesn't finalize, do not deploy it in the production environment.

Back up the IDE workspace before development. There will be some dirty data in the IDE during the deletion of an entity from IDE.
Do not modify the OOTB content in the IDE or in the database. Instead, develop a new content pack to include all the customizations.
Define the last modified column in the integration entity during development in the IDE. This column is used to compare the records in the source system with ITBA to identify which records need to be extracted in the different ETL processes.
Define the MD_BUSINESS_KEY in uppercase (BODS is case-sensitive).
To delete an entity from the IDE, follow the below steps:
1. Delete the relationship arrow.
2. Save the operation.
3. Delete the entity.
Recommended: If the MD_BUSINESS_KEY is combined with multiple fields, put the date type field at the end.
Double-check that the field type and the length are correct before generating the content pack.
If the target entity is defined as a Dimension, set the SCD Type:
1. SCD1 means that the field does not keep the historical data, it only stores the latest value.
2. SCD2 means every change of this field creates a new record in ITBA.

CAPs should not be used to store customer data. A CAP helps you migrate the KPIs, Pages, and/or Contexts.
If you meet any issue while creating a CAP, check the CAP.log and xs2go.log in the ITBA log Portal using the following URL: linkhttp://{ITBAinstance}:10002/LogPortal.
The table and view used by the CAP are generated by the deployment of cp-core. If you get an error message that there is no relevant table or column, check whether the cp-core has this entity or column.
If you develop a CAP with different iterations, it should aggregate. This means that the last iteration of the CAP should include all the feature of previous ones.
During the migration of the CAP file, follow the below steps:
1. De-activate the previous CAP in the target environment.
2. Remove the previous CAP from the target environment.
3. Import the latest CAP to the target environment.
4. Activate the latest CAP in the target environment.

The ETL scheduler need to be rescheduled after each restart.
If the ETL fails at step 3, check the detailed error message in the fbi.log in $HPBA_Home\agora\glassfish\glassfish\domains\BTOA\logs.
If the ETL fails before step 3, check whether the BOE and BODS servers are up, and whether the end user connects to the correct server.
If the ETL fails after step 3, access the BODS manager console to get the detailed error message.