VenturesAPI
Login to VenturesAPI at https://vapi.avsbcloud.com
Create Vlow
Go to Vlows.
Click on Create
Fill in the name “FADA to OC (Current Date)”.
Example: “FADA to OC 4/10/2022”.
Vaction: Trigger
Click “Edit” on the first Vaction.
Click “Save”. Then go Back.
Vaction: Interpreter: FADA to VenturesAPI Properties
Click on “+” icon at the bottom.
Select “Interpreter_BodyToProperties_PreDefined”. Click “Save”.
Click “Edit” on the newly created Vaction.
Select FADA: Realtime Glog and click “Save”.
The VoutputProperties will be automatically populated.
Click “Back”.
Vaction: Interpreter: VenturesAPI Properties to OfficeCentral Check In/Out Format
Click on the ‘+’ button at the bottom.
Select “Interpreter_PropertiesToBody_Predefined”. Click “Save”.
Click “Edit” on the newly created Vaction.
Select “OfficeCentral: Attendance Check In/Out”. Click “Save”.
The VinputProperties will be automatically populated.
Edit the values so that the Vinput Properties looks like this:
Note: Latitude, Longitude can be set to your own value if required.
Vaction: HTTP Request to OfficeCentral Endpoint
Go back to the Vlows page and click on the ‘+’ icon at the bottom of the screen.
Select HttpRequest and click ‘Save’.
Click “Edit” on the newly created Vaction.
Update so that the fields resemble above:
Input Source | FromVobjectBody |
From | 2 |
Method | Post |
HTTP Request URL | https://v2.officecentral.asia/api/attendances/fadachecksingle?apiKey=xxxxxxxxx |
Replace xxxxxxxxx with your OfficeCentral API Key.
Get VenturesAPI Vlow Listener URL
Get the Vlows ID.
Navigate to the Vlow page.
For the example above, the listener URL is https://vapi.avsbcloud.com/vlows/listener/6997945.
FADA
Login to FADA at https://vfada.avsbcloud.com.
Webhooks
Navigate to Webhooks.
Click the “+” icon to add a new Webhook.
Select your Device. Fill the fields as above (change the Listener URL to your listener URL in 2.6).
Device | {Your Device} |
Enabled | Active |
Event | RealtimeGlog |
HTTP Method | POST |
URL | {Your Listener URL} |
Device Users
Navigate to Device Users.
If you have not, click Synchronize to synchronize the device users with the online portal.
Ensure that the External User Id matches with the Staff ID at OfficeCentral as per in 1.3. If this does not match, the integration will fail.
Validation
VenturesAPI
Login to VenturesAPI at https://vapi.avsbcloud.com.
Navigate to “Vlogs”.
The Vlogs page shows a log of any Vactions happening between VenturesAPI and any other apps that calls VenturesAPI.
Try to check in using the Device and the view the logs if it is updated.
If the log is updated, this means the integration between your device and VenturesAPI is successful.
OfficeCentral
Log in to OfficeCentral and navigate to Classic View > HRMS > Attendances > Overall > Daily.
Check in using the Device and refresh the page.
The user that was checked in in 4.2 should be shown here as well.
If the user is shown here, it means the integration is successful.