AGRIS Customer Documentation

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Next »

TABLE OF CONTENTS:

Purpose of this Document:

Below are some of the basic setup prerequisites and system requirements that must be in place before the AGRIS Sales Application installation can begin. 

Once you have completed these requirements, Greenstone will install the agent on your AGRIS / Component server that enables the running of the AGRIS mobile apps.  

Prerequisite - Issue a Quote that Client Signs:

The Greenstone Client / Customer Relationship Manager needs to issue a quote to the client that contains the following:

Product:

  • AGRIS™ Sales Application (Product Code = GAGRSOE05E), quantity of 1 with a price of $0.

Customer must meet the requirements below:

Infrastructure and Supporting Requirements:

Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'Master Agent Pre-Install Requirements'.

End user Considerations

  1. Have stable WiFi or cellular data access where the people will use the devices to run the application.

App Requirements (Apple and/or Android devices):

  1. Setup a single email address with a secure password.  The password must have a minimum of 8 characters.  Every user of the application will need this email address and password in order to access the application.

  2. Setup users with accounts for accessing the application from either the Google Play Store or the Apple App Store.

Other Requirements:

  1. Work with Cultura personnel via a tool like ConnectWise to setup with the applicable agent (MS/SQL or PSQL) on the AGRIS server.

  2. Work with Cultura personnel via a tool like ConnectWise to help set up the application for the first user(s).

  3. As of  TLS 1.2 is supported.   Cannot use earlier versions.  

Run the Agent Checklist Utility (see information on AGS-7215 below):

Please send a screenshot of the result to Tracy Curtis (tracy.curtis@culturatech.com).  Each row of the screen should be green in order for you to proceed.

Navigation to Use:

  1. From the AGRIS System Menu, select Utilities > Diagnostics > Agent Pre-Install Utility.*

  2. Enter an AGRIS Dataset, User Id and Password.

  3. Select the Check button and a screen like this will appear.

  4. Capture a screenshot of your screen and email it to the Greenstone person who will be installing your agent (or send it to tracy.curtis@culturatech.com).

*If the menu for the Utility does not appear, go to your \\...Apps\AGRIS\Bin folder and right-click on the file titled "Agris.Sys.AgentCheck.exe" and choose to run it as Administrator.  NOTE: This utility was also made available with AGRIS 18.4.0 Software Update 1 (SU-1).

AGRIS Requirements:

  1. Be live on AGRIS 19.1 (or higher) and comply with the AGRIS 19.1 System Requirements HERE.

    1. The agent will be install on the AGRIS / Component server.

    2. Convert the applicable dataset(s) to AGRIS 19.1 (or higher) and apply the latest software update.
  2. Assure that there are enough available AGRIS concurrent user licenses available to all users of the AGRIS Sales Application (as each user of this application will consume an AGRIS concurrent user license).
  3. Apply the AGRIS System license.

  4. Enable the Extended Option:  Dataset Maintenance > Extended Options >  NAM > "Y" in AGRIS Sales Mobile (#12).

Agent Pre-Installation Checklist Utility (Readiness Assessment):

If you are running AGRIS 18.4.0 with Software Update 1(or higher), click this link for instructions on how to run the Agent pre-installation checklist utility (https://culturatech.atlassian.net/wiki/x/4IDHL).

AGRIS Sales App - Security to ENTER / ADD a Booking or Prepay using the mobile app

Unable to render {include} The included page could not be found.

AGRIS Sales Review App - Security to REVIEW & APPROVE a Booking or Prepay

Unable to render {include} The included page could not be found.

Related Content:

The selected root page could not be found.

  • No labels