Change one detail of a personal event (hosts only)
event_change_detailTHE HOSTS' OWN EDIT. Call it when somebody asks to CHANGE a detail of a wedding or other personal event this connector serves: "move the ceremony to 4:30 PM", "the reception is at the barn now", "change the dress code to garden formal", "update the parking note", "answer the question about children". IT APPLIES THE CHANGE ON THIS CALL and the reply says what the detail is now and what it was before: read BOTH of those out. Only the hosts of the event can change it; anybody else gets a refusal that you read out as given and do not work around. It changes ONE field per call, from a closed list: pass field as one of the named values and value as the new value. A time must carry am or pm ("4:30 PM"), or be a 24 hour time that cannot be read two ways ("16:30"): a bare "4:30" is refused on purpose, because this server will not guess between half past four in the afternoon and half past four in the morning. For schedule_time also pass entryTitle, exactly as the schedule row spells it. For faq_answer also pass question, which adds the entry if the hosts have not answered it yet and replaces the answer if they have. Pass undo: true with no field to reverse the caller's own most recent change on this event. Every change is written to a log that can be read back, so say what changed and do not promise anything the reply does not carry: it sends no message and it changes nothing else on the event; the event's Wallet passes are updated with the new detail as a lock-screen notice and the reply's passNotice says how many passes were reached. Reasons to read out as given: "NOT_A_HOST" means they cannot change this event; "BAD_TIME" means say am or pm; "NO_SUCH_PLACE" means the event has no such place to change; "NO_SUCH_ENTRY" means no schedule entry answers to that title, or two of them do, so ask which; "NO_CHANGE" means it is already that. It requires a personal connector token.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| undo | No | OPTIONAL. True reverses the CALLER'S OWN most recent change on this event, through the same validation and into the same log. It cannot reverse somebody else's change, cannot reverse an undo, and cannot reverse the same change twice. | |
| field | No | WHICH detail to change, one of the named values and nothing else. Required unless `undo` is true. ceremony_time and reception_time take a clock time; ceremony_place and reception_place take the place label in `value` and optionally a venue name in `venueName`; dress_code and arrival_note take a sentence; schedule_time takes a clock time plus `entryTitle`; faq_answer takes an answer plus `question`. | |
| value | No | The NEW value, as the hosts would say it. A clock time for the time fields, the place label for the place fields, one sentence for dress_code and arrival_note, the answer for faq_answer. No links and no markup: both are refused. Required unless `undo` is true. | |
| question | No | REQUIRED for faq_answer: the question being answered. An exact existing question replaces that answer; a new one is added. | |
| venueName | No | OPTIONAL, and only for ceremony_place and reception_place: the name of the venue, when the hosts named one. Left out, the venue already stored is kept rather than cleared. | |
| entryTitle | No | REQUIRED for schedule_time: the TITLE of the schedule entry to move, exactly as a schedule row spells it. If two entries answer to it the reply is NO_SUCH_ENTRY and nothing moves, and you ask which one they mean rather than choosing. | |
| eventIdOrName | Yes | REQUIRED. The event id (test_wedding_a_garden) or the event NAME as the hosts spell it ("Susie and John"). |