Once Argos is ready to be released across campus, the appropriate person (managers, directors, chairs, etc.) must request for an Argos account to be created for each user via an ITD work order. A work order can contain account requests for multiple users. To request an account, log into the ITD FootPrints work order system. Create a new issue. Select "Account Requests/Connectivity/Logon" as the problem type and "Argos Account" as the category. Next select add, modify, or remove account as the symptom. Another window will open for the remaining information such as username, M number, job title, employee type, reason for the account, the user type requested, the functional group model (student, budget, etc.), and the database system (REPT, BLUEINFO DW, etc.) to be entered. Finally click Save.
After access has been approved and an account has been created, users should log into Argos with their FSA username and password at http://evmaps.fsa.mtsu.edu/.
Users can log into the Argos client app or log into the Argos Web Viewer which has a sleeker appearance. However, the Argos Web Viewer does not replace the client app for development.
Navigating is simple in Argos. It uses an Explorer Tree similar to Windows Explorer. This tree view of the folders contains the DataBlocks and reports the user has permissions to view, modify, or create. Argos lists the actions available to the user on the right side of the screen for each object. Users can access this same list of available actions by right-clicking on the object. Actions are available to the users based on their user type of Report Viewer, Report Writer, or DataBlock Designer. A few examples of actions include: Run Dashboard, New, Edit, and Delete.
All user types can execute reports for which they have permissions to view. Report
Viewers can only execute reports. Report Writers can create/modify reports for existing
DataBlocks as well as execute reports. DataBlock Designers can create/modify DataBlocks
as well as create/modify reports and execute reports.
A proposed naming convention has been established for naming DataBlocks and reports. It is as follows.
Datablock –> mnnnn - DataBlockName – n.n
Report –> mnnnnx – ReportName – n.n
m = module
nnnn = 0001 – 9999
x = A – Z, AA to ZZ, AAA to ZZZ, ...
n.n = version number
For example, a General Campus DataBlock could be named G0001 – Students by Dept and Major – 1.0 and the reports using this DataBlock could be named G0001A – All Information without Address – 1.0 and G0001B – All Information Including Address – 1.0. Please note that there would not be another DataBlock named with the prefix G0001, even if it was in a separate folder in the Explorer Tree structure.
Executing a report can be done by selecting the Run Dashboard action for the dashboard or report. Some reports may have parameter selections that need to be made prior to running them or the report could run with the default selections if defaults are set. The user will select the report they wish to execute for the DataBlock in the Report Options dropdown list at the top of the window. Depending on the type of report, there will be options available to preview the report, save the report, email the report, or print the report. The options available for each report are dependent upon the report type that was created: banded, csv, or extract.
If a user runs specific reports more frequently than others and does not want to sift through the Explorer tree to find them, shortcuts can be created for easy access. Rather than searching the Explorer tab for the reports to run, the user can simply click on the Shortcuts tab and see only the reports he wants to execute.
Argos has wonderful Help which contains detailed descriptions and instructions concerning the Argos interface as well DataBlocks, charts, the various report types, scheduling reports, OLAP cubes, and more. This Help also includes user guides and pre-recorded training videos for each user type.