Use different url to create start / end bookings #21

New Issue

2018-10-16T23:36:26+02:00

0xFEEDC0DE64 commented

2018-10-16 23:36:26 +02:00

(Migrated from github.com)

All bookings created by the tool are marked as "modified afterwards" even if it was created right in time.
This happens because we use the api from the booking calender.
We should use the api from terminal instead!

method: POST
url: json/terminalPageController/evoTerminalBooking
sisAppName: terminal
request-body:

{
  persNr: null,
  bookingDate: 20171217,
  bookingTime: 190217,
  bookingTimespan: 0,
  bookingType: "G",
  hourCategory: "",
  bewEinh: "",
  empfEinh: "",
  einstuf: "",
  text: ""
}
em
```pty response

All bookings created by the tool are marked as "modified afterwards" even if it was created right in time. This happens because we use the api from the booking calender. We should use the api from terminal instead! method: POST url: json/terminalPageController/evoTerminalBooking sisAppName: terminal request-body: ``` { persNr: null, bookingDate: 20171217, bookingTime: 190217, bookingTimespan: 0, bookingType: "G", hourCategory: "", bewEinh: "", empfEinh: "", einstuf: "", text: "" } em ```pty response

0xFEEDC0DE64 commented

2018-10-16 23:36:42 +02:00

(Migrated from github.com)

The new url ignores the time for bookings! This is now definately considerd to be a bug! We need to use the new API url when creating bookings for NOW and the old url when creating bookings in the past / future.

also: [requested by mario]

The new url ignores the time for bookings! This is now definately considerd to be a bug! We need to use the new API url when creating bookings for NOW and the old url when creating bookings in the past / future. also: [requested by mario]

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: feedc0de/DbZeiterfassung#21