pub struct CheckinResource<'a> { /* private fields */ }Expand description
client.checkin()
Implementations§
Source§impl<'a> CheckinResource<'a>
impl<'a> CheckinResource<'a>
Sourcepub fn create_persons(
&self,
body: &CheckinPersonCreate,
) -> Result<CheckinPerson>
pub fn create_persons( &self, body: &CheckinPersonCreate, ) -> Result<CheckinPerson>
Create new person and add to group
POST /checkin/persons
Creates a person and admits them to a group for the check-in workflow. Requires administer persons, or create person in churchcheckin plus group meeting permission and a person security level covering the selected status. Masterdata IDs are installation-specific. Ordinary duplicate-person confirmation is bypassed; a unique GUID and license limits still apply. A creation note and optional tag are saved before the membership. This request does not record meeting attendance or print a label; perform the actual check-in separately. Failure can leave earlier steps saved because the whole workflow is not one transaction. The response is the legacy person model, not the regular Person representation.
Use Self::create_persons_with to pass query parameters.
§Example
let body = models::CheckinPersonCreate {
group: models::CheckinMembershipCreate {
id: 9,
person_fields: Default::default(),
..Default::default()
},
person: models::CheckinPersonDataCreate {
campus_id: 42,
department_ids: vec![42],
first_name: Some("Alex".into()),
last_name: "Example".into(),
status_id: 42,
..Default::default()
},
..Default::default()
};
let result = client.checkin().create_persons(&body)?;
println!("{:?}", result.first_name);Sourcepub fn create_persons_with(
&self,
query: &PostCheckinPersonsQuery,
body: &CheckinPersonCreate,
) -> Result<CheckinPerson>
pub fn create_persons_with( &self, query: &PostCheckinPersonsQuery, body: &CheckinPersonCreate, ) -> Result<CheckinPerson>
Create new person and add to group
Like Self::create_persons, with query parameters.
POST /checkin/persons
Creates a person and admits them to a group for the check-in workflow. Requires administer persons, or create person in churchcheckin plus group meeting permission and a person security level covering the selected status. Masterdata IDs are installation-specific. Ordinary duplicate-person confirmation is bypassed; a unique GUID and license limits still apply. A creation note and optional tag are saved before the membership. This request does not record meeting attendance or print a label; perform the actual check-in separately. Failure can leave earlier steps saved because the whole workflow is not one transaction. The response is the legacy person model, not the regular Person representation.
Sourcepub fn update_persons(
&self,
body: &CheckinPersonUpdate,
) -> Result<CheckinPerson>
pub fn update_persons( &self, body: &CheckinPersonUpdate, ) -> Result<CheckinPerson>
Put existing person into group
PUT /checkin/persons
Admits an existing person to a group using its default role and check-in membership origin, optionally adds a tag, and updates person fields configured for that group. Requires administer persons or group meeting permission. Existing membership is a conflict, not an idempotent success. The operation does not record attendance or print labels. Tag changes occur before membership creation and can remain after a failed request. The returned legacy person-model representation differs from the regular Person API.
§Example
let body = models::CheckinPersonUpdate {
group: models::CheckinMembershipCreate {
id: 9,
person_fields: Default::default(),
..Default::default()
},
person_id: 42,
..Default::default()
};
let result = client.checkin().update_persons(&body)?;
println!("{:?}", result.first_name);