The name of the folder Text 100 Required The recruiter that owns the folder, and has full control of the folder. Inbound, you need to specify the userId or the UserName. Monster can provide these values to you, if needed. Required JobApplicants are currently supported only outbound. This object provides information about ones applicant data management techniques. This object's primary purpose is to support the new OFCCP regulations for government contractors. The description of the applicant data management techniques. This field has a maximum size of 3000 characters. This is OUTBOUND only data providing resume search history information for the folder. The hiring organization's unique id for this Folder Text 50 Not required Use this value if you want the job to be physically deleted from the Monster databases. Boolean This outbound only value indicates the current state of the posting. The states are: o open - indicates that the folder is in use and may have any combination of expired, active, purged, and pending postings o purged - indicates that the folder is marked for removal from the database Enumerated String can be omitted for folder "adds". For now, we will not support individual nodes. When we do, the monsterId will represent the resourceACL. The monsterId attribute in represents the DACRoleId. If the node is not present, fail. If the node does not have an attribute, then DACRoleId is assummed to be NULL. If the node does have an attribute, set the DACRoleId to the specified value. We should probably validate that the DACRoleId is valid - hopefully there's a proc for that. A recruiter specified here also has access to this folder. You need to specify the userId or the UserName. Monster can provide these values to you, if needed. A refererence to an MOHQ "team"; a team specified here gives members of that team access to the folder in MOHQ. Specify the team name or the unique TeamID as the "monsterId". Monster can provide these values to you, if needed. 0 - new position; 1 replacing an existing position Boolean Requisitions are not required to be a folder. If they are, however, this is a required field. Requisition title Text 75 Requisitions are not required to be a folder. If they are, however, this is a required field. Complete description of the requisition Text 8000 Requisitions are not required to be a folder. If they are, however, this is a required field. Notes pertaining to the requisition Text 255 Location of job in requisition. NOTE: A locationId must be used for companies using custom locations. Companies using standard Monster locations can specify the individual address fields. The recruiter selected as the Supervisor for this requisition. It's the same value specified in MOHQ in the "Supervisor" dropdown. Inbound, you need to specify the userId or the UserName. Monster can provide these values to you, if needed. Required for inbound requisitions. The recruiter that created the requisition; generally, the same as the recruiter on the Folder and the job. Inbound, you need to specify the userId or the UserName. Monster can provide these values to you, if needed. Required for inbound requisitions. The recruiter assigned to this requisition. It's the same value specified in MOHQ in the "Recruiter" dropdown. Inbound, you need to specify the userId or the UserName. Monster can provide these values to you, if needed. Required for inbound requisitions. 0 - Exempt; 1 - Non-exempt Boolean Requisitions are not required to be a folder. If they are, however, this is a required field. Text 1000 Money 10 digits Money 10 digits The history of the requisition's states Indicates the EEOC job category for this requisition. This is the equivalent of the "EEO-1 Job Classification". Indicates the organization for this requisition. See Monster for the values appropriate to your company. Requisitions are not required to be a folder. If they are, however, this is a required field. The shift of job such as 1st, 2nd, 3rd, rotating, etc. This field is supported outbound only. Defines the open date of the JobRequisition. Is not supported inbound. This date will be internally set to UserOpenDate or current Datetime if no UserOpenDate present. Monster maintains a set of ids that relate to Affirmative Action Plan (AAP) Job Groups. Please contact your customer service representative for the list of ids. Non-Monster text identifier of the requisition Text 25 Requisitions are not required to be a folder. If they are, however, this is a required field. indicates if the requisition needs to be approved before becoming active Boolean Requisitions are not required to be a folder. If they are, however, this is a required field. Outbound, this provides the current Requisition Status along with a history of previous statuses. Inbound, it provides the current requisition status. Boolean One and only one ReqStatus with the state of current should be provided on an inbound requisition. More than one ReqStatus with a type of current will cause an error. Any inbound ReqStatuses that do not have a type of current will be ignored. Rounds required to be passed for the req to be approved SmallDateTime Identify a recruiter that is an approver of a requisition Comments about the requisition and its approval worthiness Text 1000 Value stored in our database that is displayed for the user in the UI. Text 255 Text 8000 Int int