Pages sorted Alphabetically
|
Trackable actions can be generated from any document in the database. The actions will be similar to those used in the SHE Reports database and will have 4 parts : #Owner proposes an Action and an Actionee. The priority is set using the prioritisation wizard. The suggested target date is added. ... |
|
This data will be migrated to the new [[Spend Map Item]] form |
|
Hello , I am Andrew Champion and am based in Cleveland ( Loftus ) I am the FoCul Developer for the new system. Tel Mobile 01287 244 003
email andrew.champion@focul.net |
|
==Description== The Area Configuration will list the following information : Plants within the Area - multi value list
Systems within the Area - multi vlaue list Note that changes to Plant and System names will not be pushed down to related documents. A Plant deficintion form was ... |
|
==Description== A tool is required to change the equipment Criticality across several documents at view level. ==Location== The Action menu ==Access== Whoever can change a document can run this action against that document i.e. let it run and test on an item by itme basis ==Technical ... |
|
==Description== A tool is required to change the equipment type across several documents at view level. Note that a dialogue will be needed as it is a dependent drop down e.g. Pump >> Centrifugal Pump ==Location== The Action menu ==Access== Whoever can change a document can run this action ... |
|
==Description== The "Current Doer" functionality allows all individuals to see what documents are awaiting their specific input. These names are captured in a multivalue field called xxxxxxxx Action:SC ==Terminology==
==Examples==
===Actions===
Draft Actions = Initiator
Awaiting Acceptance = ... |
|
One of the most important aspects of the new system is the data hierarchy. The Data hierarchy has the following main purposes. # To provide information that is used by the policy driven workflow and security engines
# The Visual ordering of information on the screen
# The ability to click ... |
|
==Description== The Data Integrity Agent runs on a periodic basis to ensure that the data hierarchy is intact as per the [[Data Hierarchy]] scheme and the [[Data Integrity Engine]]. It compares the hash codes of a document to those of its children and where there is a difference it corrects ... |
|
==Description== With Lotus Notes not ebing relational a process is needed to ensure that all of the meta data is correctly synchronised across all related records. There are four aspects to this process : ##All records need to contain references to their parent records using backend keys. ##All ... |