Easy Redmine icon

Easy Redmine

Easy Redmine Operations

Actions37

Overview

This node integrates with the Easy Redmine platform to perform various operations on its resources. Specifically, for the Attendance resource and the Update operation, it allows users to update existing attendance records by modifying fields such as arrival time, departure time, description, and associated activity ID.

Typical use cases include:

  • Correcting or updating attendance times after an employee forgets to clock in/out.
  • Adding descriptive notes or linking attendance entries to specific activities for better tracking.
  • Automating attendance record adjustments based on external triggers or workflows.

For example, a user might automate updating an attendance record's departure time at the end of a workday or add a description explaining a late arrival.

Properties

Name Meaning
Attendance ID The unique numeric identifier of the attendance record to update.
Update Fields A collection of fields to update on the attendance record. Options include:
- Arrival The new arrival date and time (timestamp) for the attendance entry.
- Departure The new departure date and time (timestamp) for the attendance entry.
- Description A textual description or note related to the attendance entry.
- Activity ID Numeric ID linking the attendance to a specific activity within Easy Redmine.

Output

The node outputs JSON data representing the updated attendance record(s). Each output item corresponds to one processed input and contains the updated fields as returned by the Easy Redmine API.

If the node supports binary data output (not indicated here), it would typically represent attachments or files related to the attendance record, but this is not applicable for the Attendance Update operation.

Dependencies

  • Requires an active connection to an Easy Redmine instance via an API key credential.
  • The node expects the base URL of the Easy Redmine domain to be configured in the credentials.
  • No additional external dependencies are required beyond the Easy Redmine API access.

Troubleshooting

  • Common Issues:

    • Invalid or missing Attendance ID will cause the update to fail.
    • Providing invalid date/time formats for arrival or departure fields may result in API errors.
    • Attempting to update fields without proper permissions in Easy Redmine can lead to authorization errors.

  • Error Messages:

    • Errors from the API are captured and returned as error messages in the node output if "Continue On Fail" is enabled.
    • Typical error messages include "Attendance record not found," "Invalid date format," or "Unauthorized access."

  • Resolutions:

    • Verify that the Attendance ID exists and is correct.
    • Ensure date/time values conform to ISO 8601 or the expected format by Easy Redmine.
    • Confirm API credentials have sufficient permissions to update attendance records.

Links and References

Discussion