Feedback

ScreeningOrderServiceCode / synchronous and asynchronous use cases

Contact First/Given Name: margaret

Question: I'd like to confirm these enumerated values:
Immediate - does this mean that requester is going to wait online until the results are ready (i.e. I'll wait until you process the credit check and have results to send back immediately)
Delayed - does this mean that I'm submitting my request for a credit check and the supplier just needs to respond with an acknowledgement that the order was recieved. Then the results will be sent back in a separate request/response transaction.

Margaret,

I assume you are talking about ScreeningOrderServiceCode. You probably found this definition: Refers to type of order processing pattern or level of service requested. This is an open HR-XML list. Enumerated values are Delayed and Immediate. Delayed = Acknowledgement of order receipt requested, but no immediate business-level processing expected. Immediate = Immediate business-level processing expected. This is an HR-XML Open List.

"Immediate" does imply a near-real-time response, which might support the return of a result to a user waiting for a result. I guess there are only a few types of screenings where this might be a reasonable expectation. **just an update to emphasize that this primarily is something that has meaning with a particular trading partner arrangement. I probably should just leave it there. I think the definition is actually pretty good -- immediate business-level processing. I think a synchronous, real time response with a result is a likely outcome, but the message exchange is really a separate matter.***

I'd agree that delayed is generally has the meaning you describe.

PositionLocation / UserArea, PositionLocation

PositionLocation.

Question: There are a couple of requests here.

1. Need a UserArea
2. PositionLocation should mirror WorkLocation and include a LocationID and LocationName.

This would aling PositionPosting with IndicativeData.

PositionOrganizationDetails / multiple identifiers like DeploymentOrganizationDetails

PositionOrganizationDetails

Question: Hello,

The model should mirror that of DeploymentOrganizationDetails in IndicativeData. It allows for multiple identifiers and types of identifiers.

RemunerationRange / RemunerationAmount

Comments about RemunerationRange

Question: Hello,

We have a requirement to pass a minimum, maximum and reference amount.

Also in some cases an explicit remuneration amount may need to be specified, not always a range.

I think adding either the generic RemunerationAmount or a new RemunerationReferenceAmount would work.

PositionPosting: languageCode on PositionTitle

Comments about PositionPosting

Question: We have a requirement to have PositionTitle in multiple languages. I can accomplish this using multiple PositionFormattedDescription, but I think it would be appropriate for PositionTitle to have a languageCode attribute and to occur multiple times.

Resolution: Make PositionTitle of TextType and make repeatable.

NewHireEmployeeDetails: EmployeeGroup

Comments about NewHireEmployeeDetails.

Question: We use EmployeeGroup as a group and sub-group in IndicativeData. It would be nice to have this field, unbounded in NewHireEmployeeDetails.

Disability Details

Comments about DisabilityDetails.

Question: Hello,

We have requirements for explicit dates associated with a disability such as DisabilityDate, RecoveryDate and DisabilityCertifiedDate.

These would be in addition to the validFrom and validTo dates.

Syndicate content