Difference between revisions of "Training Portal"
From Adjutant Wiki
(Created page with "ADJUTANT LANGUAGE • CID – Company ID. This identifies the database name the application is linked to and where to access or store transactions from the software • Sandbo...") |
|||
Line 2: | Line 2: | ||
• CID – Company ID. This identifies the database name the application is linked to and where to | • CID – Company ID. This identifies the database name the application is linked to and where to | ||
access or store transactions from the software | access or store transactions from the software | ||
+ | |||
• Sandbox – An Adjutant CID that is set up for testing transactions and training new users. Any | • Sandbox – An Adjutant CID that is set up for testing transactions and training new users. Any | ||
records created here will not impact the company’s operating software | records created here will not impact the company’s operating software | ||
+ | |||
• Attributes – Identifiers given to any static record in Adjutant (Customer, Vendor, Item or User) | • Attributes – Identifiers given to any static record in Adjutant (Customer, Vendor, Item or User) | ||
which allows the system to assign responsibility or save additional information to the record | which allows the system to assign responsibility or save additional information to the record | ||
+ | |||
• Organizations – Every entity Reed’s Metals interacts with will be referred to as a organization | • Organizations – Every entity Reed’s Metals interacts with will be referred to as a organization | ||
record, then attributes will be assigned to define the prospect/ customer/ vendor/ | record, then attributes will be assigned to define the prospect/ customer/ vendor/ | ||
subcontractor/ etc. relationship | subcontractor/ etc. relationship | ||
+ | |||
• Rule Maintenance – End user screen that allows admin users to update dropdown values | • Rule Maintenance – End user screen that allows admin users to update dropdown values | ||
throughout the system. The rules will often have a code identifier that allows the unique | throughout the system. The rules will often have a code identifier that allows the unique | ||
Line 19: | Line 23: | ||
features or modify processes within that screen. NOTE: Using the sandbox to test any set up | features or modify processes within that screen. NOTE: Using the sandbox to test any set up | ||
option changes is recommended before making changes in the live environment. | option changes is recommended before making changes in the live environment. | ||
+ | |||
• User – Any person that has access to the Adjutant system, either through the Desktop, Web or | • User – Any person that has access to the Adjutant system, either through the Desktop, Web or | ||
Terminal Scanner applications | Terminal Scanner applications | ||
+ | |||
o Security Tokens – Permissions given to each Users throughout the system | o Security Tokens – Permissions given to each Users throughout the system | ||
+ | |||
o User Options – Universal preferences for how Adjutant is displayed and operates for | o User Options – Universal preferences for how Adjutant is displayed and operates for | ||
each specific user. | each specific user. | ||
+ | |||
• Resource – A defined contact, user or machine in Adjutant that can be given skills, tasks and | • Resource – A defined contact, user or machine in Adjutant that can be given skills, tasks and | ||
responsibilities. All of which can be reported as needed | responsibilities. All of which can be reported as needed | ||
+ | |||
• Auto Process – Back End system procedures that run during off hours to update records, run | • Auto Process – Back End system procedures that run during off hours to update records, run | ||
reports and close daily batching processes | reports and close daily batching processes | ||
+ | |||
o Diamond Report – Custom SQL reporting provided by ABIS or admin team members to | o Diamond Report – Custom SQL reporting provided by ABIS or admin team members to | ||
pull specific data without going through a front-end report screen | pull specific data without going through a front-end report screen | ||
+ | |||
• Blocks – Web Adjutant Business Intelligence and KPI elements that are set up specific to the | • Blocks – Web Adjutant Business Intelligence and KPI elements that are set up specific to the | ||
user for dashboard reporting | user for dashboard reporting | ||
− | |||
− |
Latest revision as of 09:42, 24 March 2020
ADJUTANT LANGUAGE • CID – Company ID. This identifies the database name the application is linked to and where to access or store transactions from the software
• Sandbox – An Adjutant CID that is set up for testing transactions and training new users. Any records created here will not impact the company’s operating software
• Attributes – Identifiers given to any static record in Adjutant (Customer, Vendor, Item or User) which allows the system to assign responsibility or save additional information to the record
• Organizations – Every entity Reed’s Metals interacts with will be referred to as a organization record, then attributes will be assigned to define the prospect/ customer/ vendor/ subcontractor/ etc. relationship
• Rule Maintenance – End user screen that allows admin users to update dropdown values throughout the system. The rules will often have a code identifier that allows the unique dropdown record to be related to other saved values throughout the system. o Units – Specifically set up to identify all relationships between different Units of measure for all item records i.e. LBS/FT, FT to Each (or piece), Each to Box (or bag), etc.
• Set Up Options – Each Adjutant screen has a series of logic checkboxes that dictate how that screen reacts when used. The admin team can update these checkboxes in order to add new features or modify processes within that screen. NOTE: Using the sandbox to test any set up option changes is recommended before making changes in the live environment.
• User – Any person that has access to the Adjutant system, either through the Desktop, Web or Terminal Scanner applications
o Security Tokens – Permissions given to each Users throughout the system
o User Options – Universal preferences for how Adjutant is displayed and operates for each specific user.
• Resource – A defined contact, user or machine in Adjutant that can be given skills, tasks and
responsibilities. All of which can be reported as needed
• Auto Process – Back End system procedures that run during off hours to update records, run reports and close daily batching processes
o Diamond Report – Custom SQL reporting provided by ABIS or admin team members to pull specific data without going through a front-end report screen
• Blocks – Web Adjutant Business Intelligence and KPI elements that are set up specific to the
user for dashboard reporting