![]() Primary name of the device, generally provided by the user. List of names provided by the developer rather than the user, often manufacturer names, SKUs, etc. ![]() This defines the commands, attributes, and states that the device supports. It should be immutable for the device if it changes, the Assistant will treat it as a new device. This must be unique for the user and for the developer, as in cases of sharing we may use this to dedupe multiple views of the same device. The ID of the device in the developer's cloud. Zero or more devices are returned (zero devices meaning the user has no devices, or has disconnected them all). ![]() an account number rather than email).ĭetailed error which will never be presented to users but may be logged or used during development. The string is opaque to Google, so if there's an immutable form vs a mutable form on the agent side, use the immutable form (e.g. Reflects the unique (and immutable) user ID on the agent's platform. Type and payload associated with the intent request. List of inputs matching the intent request. This does not determine whether any particular device is reachable. Your SYNC response should return all devices associated with the user. Supported traits and attributes for each device. It is triggered during account linking or when a user And a null value means Schedule Sync will not change the hold status in any way.This intent requests the list of devices associated with the given user and their capabilities. A 0 (false) value would cause the job to be released to production. A 1 (true) value would cause the job to be placed on hold. From there you can change the value of onhold to affect the job’s hold status in Pro. The record must include the (order_, material, pcode) data. Your own process should add records for any job that you wish to manipulate. Once the table is set up and Eclipse Pro is talking to your SQL database, you are ready to put the table to use. At that time, each feature will have it’s own set of columns, but it will not be necessary to create columns for features that you are not going to use. If it doesn’t exist then Eclipse Pro simply won’t change your schedule at all, but in future versions there will be more schedule manipulation features available through this mechanism. If it exists then Eclipse Pro will update the corresponding job’s hold status. These three values form the key (identity) of the job in the Eclipse Pro system, and as such cannot be null. We expect that in time the Schedule Sync feature will evolve to need it. This TSQL create statement would create a suitable table for Eclipse Pro to use. This name must be placed into the Schedule Table field on the Schedule Sync configuration editor. The table can have any name (we recommend “ams_SchSync”). The Schedule Sync feature retrieves job schedule information from a customer’s SQL Server database and uses that data to modify the Eclipse Pro production schedule.Įclipse Pro is going to reach into your SQL Server and query this table (or view) for job hold information which is then applied to the schedule.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |