Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| 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. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
Promote customizations from development to production
- Before you promote customizations from development to production, thoroughly document every change made in the development system that
will need to be part of the patch that is promoted to production. The information that you collect in this documentation depends on the
environment, but should at a minimum include the following fields, which are mentioned in the log file:
- Change Number
- Request Description
- Task Number
- Task Description
- Change Requester
- Change Owner
- Record modified
- Date Modified
- Change Description
- Unload Name
- Patch Name
- Test plan
- Test all changes in the development system.
- After all changes are documented, tested, and functioning in the development system, create a single unload.
We recommend that you:- Remove the field "keys" from the exclude list in the signaturemake file for the dbdict table before creating the signatures on both production and development. That way, dbdicts that had changes to the keys will be unloaded into the file that is loaded into test and then production and these changes are easier to find.
- Use the Differential Upgrade utility to create a single unload file containing all changes.
- Manually modify all keys that were changed in any of the dbdicts contained in the unload
- After the single unload is created, perform the following steps:
- Apply it to a test system that is a recent copy of the production environment.
- Test the changes thoroughly.
- Document any reported issues and fix these in the development system after each test iteration.
- Provide a repaired patch file (while still using a single unload file) to the testers at the beginning of each test iteration.
- After the unload is thoroughly tested and accepted, the latest unload can be applied to a production system or to any other system that needs to be upgraded with the patch, such as a training system.
Note: Do not modify the patch after this point. Address new issues found after testing is complete in the next development cycle.
Related concepts
Environment configuration
Applying customizations to the production environment
Best practices for promoting customizations
Comparison of the tools to use for promoting customizations
Development auditing
Differential Upgrade utility
Unload script utility
Revision control
