Changes

IMSMANG IMSMA^NG provides a local identifier (local ID) data element widget for each item category or subcategory, which when used on data entry forms Data Entry Forms allows information managers to track items and field reports Data Entry Forms entered into {{IMSMANG}}. These local ID data elements widgets enable data entry clerks to click on a button and insert an automatically generated an ID rather than enter one manually, helping to reduce duplicate local IDs in the system.  The local ID generator enables you to define a numbering scheme/series for an item ID e.g. Accident ID and the Form ID, on a Data Entry Form template. Once the numbering scheme/series is defined, users can automatically assign IDs to objects each time they add a Data Entry Form with an object ID field to IMSMA by clicking on the widget/button. 

|[[HowTo:Set Object Local ID Fields to Autogenerate Object ID Numbers|Set Object ID Fields to Autogenerate Object ID NumbersGenerator Window]]

IMSMANG comes with a default local [[File:Local ID type per item, but there is no limit to how many different types can be createdGenerator Button. It is recommended to create at least one local png|600px|center|''Local ID type per item subcategory. For example, create a local ID type for completion reports, another for clearance reports and another for minefields. Also, establishing a convention for the local ID types makes it easy to understand and find data.Generator Button'']]

Local {{IMSMANG}} comes with a default local ID types are typically comprised of generator scheme/series per item, but there is no limit to how many different scheme/series can be created. It is recommended to create at least one local ID generator scheme/series per item subcategory. For example, create a local ID generator scheme/series for Completion Reports and another for Clearance reports. Also, establishing a convention for the following components:local ID generators makes it easy to understand and find data.

[Local {{note| *Information managers can also create an individual local ID for each Data Entry Form template that indicates the kind of information in the form. For example, a Completion Report can have a local ID Name]beginning with “DEF-[System Name]CR-[Incremented Number]” to give users an immediate understanding of the content of the form.*For exampletemplates intended to update existing items, such as status change templates, CR-HQ-1information managers can exclude the item ID generator or the ID field entirely to prevent users from accidentally creating new local IDs for existing items.}}

{| class="wikitable"|-| '''Local ID Name''' || A text string that represents the item category or subcategory. For example, a completion report could be represented by “CR.”|-| '''System Name''' || A value specified in the Client Configuration Tool of the IMSMANG TrayLauncher where system administrators can set a separate system name for each installation of IMSMANG. For example, the Headquarters installation could have “HQ” as a system name while a regional installation could have “R1.”|-| '''Incremented Number''' || A value that increases each time a new ID is generated. Information managers can specify the next number to be generated when the local ID generator button is clicked. For example, a new local ID starting with CR-HQ-1 and proceeding to CR-HQ-2 and so on will be generated each time the Completion Report local ID generator is clicked.|{NavBox IMSMA NG Administration}}

{| class="wikitable"|-| [[FileCategory:Note.jpg | 40px NAA]] || *Information managers can also create an individual local ID for each field report template that indicates the kind of information in the form. For example, a completion report can have a local ID beginning with “FR-CR-” to give users an immediate understanding of the content of the form.*For templates intended to update existing items, such as status change templates, information managers can remove the local ID generator or the ID field entirely to prevent users from accidentally creating new local IDs for existing items.|}