Record Sync

Did you try to configure this in the record sync options?

Yes I tried Stefan Helzle  I know we can configure the sync options with scheduled time with individual record  .I am just looking is there any other suggested approach where we can do full sync for all the records which are there in my application

Why are you looking for another approach?

Instead of syncing single record at particular time .I wanted to create a schedular process which will Full sync all record at  scheduled time

In case you need to define a custom logic to sync all these records, you can schedule a daily process that triggers a deployment into the same Appian environment using the internal API. That deployment will contain a dummy object and a properties file which contains for every record to sync:

recordType.RECORD_UUID_TO_SYNC.forceSync=true

Otherwise, the way to go is using the OOTB functionality

This is a neat approach.

We thought about automated forced record syncs in a different scenario - automated credential rotation - in my last role. Generally the organization didn't like static secrets for any databases, and we kept all business data in a company-controlled database rather than Appian's. So we defined database the connections via Connected Systems with the plan to automatically implement and deploy new credentials every so often. The deployment would include a sample record to sync. If the record sync failed, then an Appian-based record monitor could trigger a revert of the credential deployment via API.

The main drawback(s) to this approach - (1) not every organization is ok with automated deployments, and (2) unlike process models, there is no way to add a non-administrative account email to the alerts sent when a record type de-sync's itself. Therefore automations (such as a periodic record query monitor) around error conditions are a bit hack-ish to manage.

This is a neat approach.

We thought about automated forced record syncs in a different scenario - automated credential rotation - in my last role. Generally the organization didn't like static secrets for any databases, and we kept all business data in a company-controlled database rather than Appian's. So we defined database the connections via Connected Systems with the plan to automatically implement and deploy new credentials every so often. The deployment would include a sample record to sync. If the record sync failed, then an Appian-based record monitor could trigger a revert of the credential deployment via API.

The main drawback(s) to this approach - (1) not every organization is ok with automated deployments, and (2) unlike process models, there is no way to add a non-administrative account email to the alerts sent when a record type de-sync's itself. Therefore automations (such as a periodic record query monitor) around error conditions are a bit hack-ish to manage.