Creating new Solution

How to Create and Upload a Solution Using the Authoring Tool

Step 1: Preparing the Resource Files

1. Check Application Installation:

a. Confirm whether the application is already installed.

b. If not installed, proceed to download the resource file.

2. Execute the Installer File:

a. Use a silent execution command to automate the installation process.

3. Create a Batch File:

a. Prefer using an .msi file (if available) over an .exe file.

b. Use the installer file to create the batch file.

4. Find Silent Switches:

a. Research online or use the command prompt with “/?” to identify silent installation switches.

b. Test the switches to ensure the installer runs without manual intervention.

5. Package Resource Files:

a. Combine the installer and batch file into a zip file.

b. Important: The zip file name should be formatted like Application_Name.zip (e.g., Google_Chrome.zip).

c. Ensure the extracted zip file directly contains the installer and batch file, not a nested folder. (Avoid common mistakes of having additional folders.)

6. Document the Zip File Name:

a. Note the zip file name for later use when creating the solution.

Step 2: Creating the Solution Using the Recorder

1. Required Information:

a. Display name of the application (from Control Panel).

b. Name of the zip file containing the installer and batch file.

c. A unique solution number (any number above 10,000).

d. Client configuration file.

2. Authoring Tool Basics:

a. Types of Steps:

i. Action: Perform tasks.

ii. Condition: Evaluate and direct based on criteria.

iii. Guiding Message: Provide instructions to the user.

b. Navigation Between Steps:

i. Proceed to the Next Step.

ii. Use Conditional Logic to skip or jump to specific steps.

3. Testing the Display Name:

a. Use the Test button inside the Action step to verify if the display name is entered correctly.

Step 3: Creating the Configuration File

1. Navigate to Solution > Configuration File in the Authoring Tool.

2. Important Points to Note:

a. The URL should include the full address (with http or https) and must not end with a trailing ‘/’.

b. Two configuration files can be generated:

i. Anakage.ankscpt (Encrypted version).

ii. AnakageTest.ankscpt (Unencrypted version).

c. The configuration file acts as a communication bridge between the solution and the portal.

Step 4: Setting Up the First Step of the Solution

1. Use Solution > Properties to create the initial step.

2. Assign a unique solution number when generating an executable.

3. Uploading the Resource File:

a. Upload the prepared zip file containing the installer and batch file.

b. Enter the exact name of the zip file in the corresponding field within your solution.

4. Additional Requirements:

a. Ensure that Anakage HealITService is available to execute any solution requiring admin rights.

5. Admin Rights Setup:

a. Check the Admin required checkbox in the Install step for solutions that need elevated privileges.

Step 5: Exporting and Finalizing the Solution

1. Important Notes:

a. Use “Save As” to save your solution script with the extension .ankscpt. Save it with a descriptive name (e.g., Google_Chrome_Installation.ankscpt).

b. Use “Export > Solution/Exe” to create the final executable file.

i. Options include: Online (32-bit) or Online (64-bit).

ii. Name the final solution executable as techselfsupport_xx_.exe, where xx represents the unique solution number.

Step 6: Testing and Uploading the Solution

1. Test the .ankscpt file to ensure all steps function as expected.

2. Upload the final executable to the designated portal or deployment system, ensuring proper configuration and testing for end-user usage.