Schedule

Change

This is your name for the configuration for reference, this is also the name that will be shown in success and error emails from the scheduler.

Type

The type of object there will be updated

Use transaction

Here you may is the updates should happen in a transaction

SQL

Shows the standard SQL there will be used to find the objects there should be updated

Condition

Here you can write the condition for the SQL there is used determine which objects should be updated.

Success email

If set you will receive an email confirming that the schedule where run correctly.

Error email

The email that will receive an error report if the schedule encounters and error.

Preview button

the preview button will show you a list containing all the primary keys there will be found by running the SQL with the given condition

Type Column

Here you can see what kind of value there is valid for the properties

Change Column

this column tell decides if a given property should be updated

Value

Here you write the value the properties should be updated with.

TIP: IT IS POSSIBLE IN THE VALUE TO WRITE PROPERTY:<NAME OF SDK BP PROPERTY> TO GET THE VALUE FROM AN EXISTING FIELD: EXAMPLE: PROPERTY:CARDNAME

TIP: IT IS POSSIBLE IN THE VALUE TO WRITE SQL:<’SQL SENTENCE> TO GET THE VALUE FROM AN EXISTING FIELD. YOU CAN USE DOCKEY@ TO REFER TO THE CURRENTLY UPDATING PRIMARY KEY: EXAMPLE: SQL:SELECT COUNT(*) FROM OINV WHERE CARCODE = ‘DOCKEY@’

Change Column

this column tell decides if a given Udf should be updated

Value

Here you write the value the Udf should be updated with.

TIP: IT IS POSSIBLE IN THE VALUE TO WRITE PROPERTY:<NAME OF SDK BP PROPERTY> TO GET THE VALUE FROM AN EXISTING FIELD: EXAMPLE: PROPERTY:CARDNAME

TIP: IT IS POSSIBLE IN THE VALUE TO WRITE SQL:<’SQL SENTENCE> TO GET THE VALUE FROM AN EXISTING FIELD. YOU CAN USE DOCKEY@ TO REFER TO THE CURRENTLY UPDATING PRIMARY KEY: EXAMPLE: SQL:SELECT COUNT(*) FROM OINV WHERE CARCODE = ‘DOCKEY@’

Property

Name of the property

Value

The value to be set for the property

Server start time (24 H/M)

When the schedule should be executed the first time.

Recurrence pattern

There are currently five supported types:

Minutely: Run the schedule every X minutes.

Hourly: Run the schedule every X hours.

Daily: Run the schedule once each day on the server start time.

Weekly: Run the schedule on specific days of the week on the server time.

Monthly: Run the schedule every X day of the month on the server time.

Only ones: Run the schedule only on the start date and the server start time.

Last day of month: Run the schedule on the last day of the month on the server start time (hour and minute)

Range of recurrence

Start: Start date of the recurrence.

No end date: The schedule should never end.

End by: The schedule should end by the specific date.