Connecting to Edval Daily - PosiEd K-12

If the Edval app is not yet created and configured in your Org, follow the steps below.

1. Go to Setup -> App Manager.
    

   

2. In the Lightning Experience App Manager, click the New Connected App button.

3. Input the following values: 

• Connected App Name = Edval 

• API Name = Edval (auto-populated) 

• Contact Email = product email/company email 

• Enable OAuth Settings = Checked 

• Callback URL = (URL is login if production, test if sandbox)  

  • https://login.salesforce.com/oauth2/callback 

  • https://test.salesforce.com/oauth2/callback 

• Selected OAuth Scopes = Full access (full) 

4. Go back to the App Manager and click Manage beside the LISS/Edval app. 

5. Click Edit Policies and update the IP Relaxation to Relax IP restrictions and save.

6. Go to Setup > OAuth and OpenID Connect Settings > enable Allow OAuth Username-Password Flows

Sharing Settings

User Setup for Integration

1. Create a user with the following details:

Note: When trying to log in with the user above, you will see the message below.    

2. Create the Permission Set first.

   1. Label: Edval

   2. API Name: (auto-populated)

   3. Description: Permission set for objects and fields used for Edval processes

   4. License: Salesforce API Integration

   5. Give access to the following objects and fields

3. Go to the user record and assign the EDVAL permission set. The EDVAL permission set provides access to the objects and fields needed for the sync process.

Edval Daily Synching Process

After creating the Edval app, connect your Org and the Edval file.

1. Open this link in a New tab

• URL: https://my.edval.education/login

• Webcode: <Enter your Webcode>

• School Code: <Enter your Account’s School zcode> (Put the School Code value from your School Account record)

2. Once opened, click the Daily dropdown and choose Synchronise

3. Click Add sync system > and populate the fields with their corresponding values:

   1. System= Posimente

   2. Server Address = https:// + {instance URL, from Setup -> My Domain -> Current My Domain URL+

      1. /services/apexrest/PosiEd/liss

         1. In the URL, if the connection is not working, try to:

            1. exclude the Posi_Ed 

            2. or do not include the _ between Posi and Ed

   3. Username = Salesforce org username 

   4. Password = Salesforce org password 

   5. Client Id = previous Connected App’s Consumer Key  

   6. Client Secret = previous Connected App’s Consumer Secret 

      1. App Manager > Edval > View > Manage Consumer Details

4. Click Test connection to confirm and click Save.

You can now start the Publish process.

Tick the Org you just configured > click the Advanced Sync button

Publish the records in this order.

Note: Before publishing, ensure the School’s PosiEd State is set to Subscriber.

From Edval Daily:

1. Publish Bell times

   1. Before publishing the Bell Time, we need to add the complete period values.

   2. Make sure TTStructure records are set correctly. (Check how many TTStructure is linked to the School account).

      1. If the TTStructure is not set up correctly, the PPublish Bell time will be affected. There will be missing bell time records after synching.

2. Publish Rooms/Assets

3. Publish Student

   1. Before doing the Publish Student synching, make sure to set up the PosiEd Value Mapping (custom settings) for the LISS Grade Level values and Gender field automation. See the file below for your reference.

      1. Value Mapping - PosiEd

   2. Make sure the Student Records’ Start Date and End Date fields are populated.

   3. Make sure that the Student Record and the Contact objects have the same Current Grade Level values.

4. Publish Teachers

   1. Before doing the Publish Teacher, make sure the etz file for Teachers from Edval has the Email and Staff IDs field populated. These two should be unique. These are the criteria for the creation and the linking of the Users to the Employee Role records.

      1. Workaround: If the Teacher records don’t have email and usernames, you can turn off the Employee Role triggered flow before publishing, and then turn it On again after publishing.

         1. You also need to have the Users created (if not yet existing) before doing the Publish Teacher

            1. Turn On the Employee Role Triggerd Flow and then manually link the Users to the Employee Role records (If the trigger is turned on, this will automatically create the Person Account for the Employee Role)

         2. Employee Role triggered flow includes the creation of the Users and will automatically link to the Employee Role records. The User will have a Profile of Chatter Free

            1. Note: The Staff users should have a correct profile license for the Calendar access. The Chatter Free license is a non-calendar license.

5. Publish Classes (Cohort)

   1. Import the PosiEd Value Mapping for the Primary Grade Level population before doing the Publish Classes

6. Publish Class lists/Cohort Member

   1. Start Date and End Date in the Student Records should be set up properly before publishing the class list

7. Publish Cyclical Timetable/Cohort Schedule

   1. Issues workaround (Edval sample file only)

      1. Before Publishing the Cyclical Timetable (CS) for the first time, make sure to update the Staff ID of Janice Young to YOUJSYS.

      2. If you will republish the Publish Teacher, make sure you update the Staff ID of Janice Young to 34567.

8. Publish Daily Timetable/Daily Data (Session)

   1. Before publishing, ensure the following values for the Session records are in your Salesforce Org. If the records are not yet there, republish the following.

      1. Bell Time

      2. Primary Staff Member

      3. Primary Location

   2. Make sure to set the From and To fields correctly. Set it based on your preferred dates for the Session creation.

   3. You may encounter this system validation error if you generate records with a 2-month range.
      

      

      This is because Salesforce only allows a size of 6MB or approximately 6000000 bytes of characters. If ever you encounter this issue, lessen the date range for lesser results so you won’t hit the limit. You may try to sync a 2-3-week range of data.

9. Publish Daily changes (Delta)

   1. This will update your changes in the Daily Timetable (Session details).

User Password Expiry

You need to check the expiry of your password, follow these steps to check

Go to Profiles > Minimum Access API Integrations > Password Policies

If the User password expiry is limited, change it to Never expires and save.

If the password has expired already then reset the password.

Go to Set up > Users > Click the User name that has the Minimum Access API Only Integrations profile > Click Reset Password

The user receives an email that contains a link and instructions to reset the password.

Follow the instructions that were sent through the email to successfully reset the password. If you have set the user password expiry to "Never expire," your password will not expire, and you will not be required to change it.