This section outlines how developers will receive their task list. In order to begin capturing Smart-Data, you will need to create monitors and recorders, and their implementations deployed on Agent. The system administrator will request one or more implementations to be developed, and the embedded software developer will be responsible for creating the code and binaries.
Once development is complete, the developer can access this screen to let other team members know the implementation is done. This will update the implementation’s status across all systems where it is waiting to be deployed.
On the developer page, there are two primary statuses: Requested and Ready. When an implementation is marked as Ready, it indicates that the development is complete and the binary file is ready for deployment (or has already been deployed) on the target system(s). This status needs manual update. All other Heex Systems or Triggers statuses are automatically updated by the system.
On each system detail page, every implementation also has a status. This status provides insight into the relationship between the implementation and the specific system being viewed.
There are three statuses within the system:
This section outlines how developers will receive their task list. In order to begin capturing Smart-Data, you will need to create monitors and recorders, and their implementations deployed on Agent. The system administrator will request one or more implementations to be developed, and the embedded software developer will be responsible for creating the code and binaries.
Once development is complete, the developer can access this screen to let other team members know the implementation is done. This will update the implementation’s status across all systems where it is waiting to be deployed.
On the developer page, there are two primary statuses: Requested and Ready. When an implementation is marked as Ready, it indicates that the development is complete and the binary file is ready for deployment (or has already been deployed) on the target system(s). This status needs manual update. All other Heex Systems or Triggers statuses are automatically updated by the system.
On each system detail page, every implementation also has a status. This status provides insight into the relationship between the implementation and the specific system being viewed.
There are three statuses within the system: