CIRRUS LOGIC INC FAQs
CIRRUS LOGIC INC's Frequently Asked Questions page is a central hub where its customers can always go to with their most common questions. These are the 30 most popular questions CIRRUS LOGIC INC receives.
Frequently Asked Questions About CIRRUS LOGIC INC
Method description
readAllGroupIds is the method used to read all group syncIDs.
Message schema
Request parameters
Empty.
Response parameters
Name
Data type
Description
sourcedIdSet
Array<GUID>
The array of syncIDs
Example
Request message
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ims="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns:ims1="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<soap:Header>
<ims:imsx_syncRequestHeaderInfo>
<ims1:imsx_version>V1.0</ims1:imsx_version>
<ims1:imsx_messageIdentifier>0123456789</ims1:imsx_messageIdentifier>
</ims:imsx_syncRequestHeaderInfo>
</soap:Header>
<soap:Body>
<ims:readAllGroupIdsRequest/>
</soap:Body>
</soap:Envelope>
Response message
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<a:Action s:mustUnderstand="1">http://www.imsglobal.org/soap/lis/gms2p0/readAllGroupIdsResponse</a:Action>
<h:imsx_syncResponseHeaderInfo xmlns:h="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<imsx_version xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">V1.0</imsx_version>
<imsx_statusInfo xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<imsx_codeMajor>success</imsx_codeMajor>
<imsx_severity>status</imsx_severity>
<imsx_codeMinor>
<imsx_codeMinorField>
<imsx_codeMinorFieldName>TargetEndSystem</imsx_codeMinorFieldName>
<imsx_codeMinorFieldValue>fullsuccess</imsx_codeMinorFieldValue>
</imsx_codeMinorField>
</imsx_codeMinor>
</imsx_statusInfo>
</h:imsx_syncResponseHeaderInfo>
<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<u:Timestamp u:Id="_0">
<u:Created>2015-07-23T07:09:45.435Z</u:Created>
<u:Expires>2015-07-23T07:14:45.435Z</u:Expires>
</u:Timestamp>
</o:Security>
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<readAllGroupIdsResponse xmlns="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0">
<sourcedIdSet>
<sourcedId>9c34d19065f74ca78e9b3cbce0343496</sourcedId>
<sourcedId>a3feb430b62941c69457bbab2140e0a8</sourcedId>
<sourcedId>30fcfb36afd54b919f2f824c92e3e972</sourcedId>
<sourcedId>0852e382ec3b405cbed5086d0d048655</sourcedId>
<sourcedId>899fb46e295b4ac08efedcface42572e</sourcedId>
<sourcedId>506a759a54a24fd28f33a68839bca577</sourcedId>
<sourcedId>10c4b2a4fb134e49aea55d6fde0693cb</sourcedId>
<sourcedId>8df15ffaf5354721b410a275eef9437f</sourcedId>
<sourcedId>728341af5acb4d179a32e70d823a390b</sourcedId>
</sourcedIdSet>
</readAllGroupIdsResponse>
</s:Body>
</s:Envelope>
View ArticleMethod description
readGroups is the method used to read information of several groups from Cirrus.
Message schema
Request parameters
Name
Data type
Description
sourcedIdSet
Array<GUID>
ThesyncIDs of the groups to beread
Response parameters
Name
Data type
Description
groupRecordSet
Array<Object>
The array of group records. See group record mapping here
Example
Request message
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ims="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns:ims1="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<soap:Header>
<ims:imsx_syncRequestHeaderInfo>
<ims1:imsx_version>V1.0</ims1:imsx_version>
<ims1:imsx_messageIdentifier>0123456789</ims1:imsx_messageIdentifier>
</ims:imsx_syncRequestHeaderInfo>
</soap:Header>
<soap:Body>
<ims:readGroupsRequest>
<ims:sourcedIdSet>
<ims:sourcedId>9c34d19065f74ca78e9b3cbce0343496</ims:sourcedId>
<ims:sourcedId>0852e382ec3b405cbed5086d0d048655</ims:sourcedId>
</ims:sourcedIdSet>
</ims:readGroupsRequest>
</soap:Body>
</soap:Envelope>
Response message
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<a:Action s:mustUnderstand="1">http://www.imsglobal.org/soap/lis/gms2p0/readGroupsResponse</a:Action>
<h:imsx_syncResponseHeaderInfo xmlns:h="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<imsx_version xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">V1.0</imsx_version>
<imsx_statusInfo xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<imsx_codeMajor>success</imsx_codeMajor>
<imsx_severity>status</imsx_severity>
<imsx_codeMinor>
<imsx_codeMinorField>
<imsx_codeMinorFieldName>TargetEndSystem</imsx_codeMinorFieldName>
<imsx_codeMinorFieldValue>fullsuccess</imsx_codeMinorFieldValue>
</imsx_codeMinorField>
</imsx_codeMinor>
</imsx_statusInfo>
</h:imsx_syncResponseHeaderInfo>
<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<u:Timestamp u:Id="_0">
<u:Created>2015-07-23T07:26:56.692Z</u:Created>
<u:Expires>2015-07-23T07:31:56.692Z</u:Expires>
</u:Timestamp>
</o:Security>
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<readGroupsResponse xmlns="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0">
<groupRecordSet>
<groupRecord>
<sourcedGUID>
<refAgentInstanceID xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">Cirrus</refAgentInstanceID>
<sourcedId xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">9c34d19065f74ca78e9b3cbce0343496</sourcedId>
</sourcedGUID>
<group>
<groupType>
<typevalue>
<type>
<language xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">en-US</language>
<textString xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">Group</textString>
</type>
</typevalue>
</groupType>
<relationship>
<relationId>27a062726b264f5d962ec0c946ad6f27</relationId>
<relation>Child</relation>
<sourcedId>8df15ffaf5354721b410a275eef9437f</sourcedId>
<label>
<language xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">en-US</language>
<textString xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">Group (id: 9c34d19065f74ca78e9b3cbce0343496) is a child of group (id: 8df15ffaf5354721b410a275eef9437f)</textString>
</label>
</relationship>
<org>
<orgName>
<language xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">en-US</language>
<textString xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">Course A Group C</textString>
</orgName>
</org>
<extension>
<extensionField xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<fieldName>OrganisationAdress</fieldName>
<fieldType>String</fieldType>
<fieldValue>Berlin</fieldValue>
</extensionField>
</extension>
</group>
</groupRecord>
<groupRecord>
<sourcedGUID>
<refAgentInstanceID xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">Cirrus</refAgentInstanceID>
<sourcedId xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">0852e382ec3b405cbed5086d0d048655</sourcedId>
</sourcedGUID>
<group>
<groupType>
<typevalue>
<type>
<language xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">en-US</language>
<textString xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">Group</textString>
</type>
</typevalue>
</groupType>
<relationship>
<relationId>02f61589185045bbbe466cc9c05af3a3</relationId>
<relation>Child</relation>
<sourcedId>8df15ffaf5354721b410a275eef9437f</sourcedId>
<label>
<language xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">en-US</language>
<textString xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">Group (id: 0852e382ec3b405cbed5086d0d048655) is a child of group (id: 8df15ffaf5354721b410a275eef9437f)</textString>
</label>
</relationship>
<org>
<orgName>
<language xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">en-US</language>
<textString xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">Test Group</textString>
</orgName>
</org>
<extension/>
</group>
</groupRecord>
</groupRecordSet>
</readGroupsResponse>
</s:Body>
</s:Envelope>
View ArticleMethod description
readGroup is the method used to read group information from Cirrus.
Message schema
Request parameters
Name
Data type
Description
sourcedId
GUID
The syncID of the group to beread
Response parameters
Name
Data type
Description
groupRecord
Object
The group object. See mapping details here
Example
Request message
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ims="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns:ims1="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<soap:Header>
<ims:imsx_syncRequestHeaderInfo>
<ims1:imsx_version>V1.0</ims1:imsx_version>
<ims1:imsx_messageIdentifier>0123456789</ims1:imsx_messageIdentifier>
</ims:imsx_syncRequestHeaderInfo>
</soap:Header>
<soap:Body>
<ims:readGroupRequest>
<ims:sourcedId>9c34d19065f74ca78e9b3cbce0343496</ims:sourcedId>
</ims:readGroupRequest>
</soap:Body>
</soap:Envelope>
Response message
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<a:Action s:mustUnderstand="1">http://www.imsglobal.org/soap/lis/gms2p0/readGroupResponse</a:Action>
<h:imsx_syncResponseHeaderInfo xmlns:h="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<imsx_version xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">V1.0</imsx_version>
<imsx_statusInfo xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<imsx_codeMajor>success</imsx_codeMajor>
<imsx_severity>status</imsx_severity>
<imsx_codeMinor>
<imsx_codeMinorField>
<imsx_codeMinorFieldName>TargetEndSystem</imsx_codeMinorFieldName>
<imsx_codeMinorFieldValue>fullsuccess</imsx_codeMinorFieldValue>
</imsx_codeMinorField>
</imsx_codeMinor>
</imsx_statusInfo>
</h:imsx_syncResponseHeaderInfo>
<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<u:Timestamp u:Id="_0">
<u:Created>2015-07-23T07:06:53.763Z</u:Created>
<u:Expires>2015-07-23T07:11:53.763Z</u:Expires>
</u:Timestamp>
</o:Security>
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<readGroupResponse xmlns="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0">
<groupRecord>
<sourcedGUID>
<refAgentInstanceID xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">Cirrus</refAgentInstanceID>
<sourcedId xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">9c34d19065f74ca78e9b3cbce0343496</sourcedId>
</sourcedGUID>
<group>
<groupType>
<typevalue>
<type>
<language xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">en-US</language>
<textString xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">Group</textString>
</type>
</typevalue>
</groupType>
<relationship>
<relationId>27a062726b264f5d962ec0c946ad6f27</relationId>
<relation>Child</relation>
<sourcedId>8df15ffaf5354721b410a275eef9437f</sourcedId>
<label>
<language xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">en-US</language>
<textString xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">Group (id: 9c34d19065f74ca78e9b3cbce0343496) is a child of group (id: 8df15ffaf5354721b410a275eef9437f)</textString>
</label>
</relationship>
<org>
<orgName>
<language xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">en-US</language>
<textString xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">Course A Group C</textString>
</orgName>
</org>
<extension>
<extensionField xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<fieldName>OrganisationAdress</fieldName>
<fieldType>String</fieldType>
<fieldValue>Berlin</fieldValue>
</extensionField>
</extension>
</group>
</groupRecord>
</readGroupResponse>
</s:Body>
</s:Envelope>
View ArticleMethod description
updateGroup is the method used to update group information in Cirrus.
Message schema
Request parameters
Name
Data type
Description
sourcedId
GUID
The syncID of the group to be updated
groupRecord
Object
The group data. See mapping details here
Response parameters
Empty.
Example
Request message
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ims="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns:ims1="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0" xmlns:ims2="http://www.imsglobal.org/services/lis/mms2p0/wsdl11/sync/imsmms_v2p0">
<soap:Header>
<ims:imsx_syncRequestHeaderInfo>
<ims1:imsx_version>V1.0</ims1:imsx_version>
<ims1:imsx_messageIdentifier>0123456789</ims1:imsx_messageIdentifier>
</ims:imsx_syncRequestHeaderInfo>
</soap:Header>
<soap:Body>
<ims:updateGroupRequest>
<ims:sourcedId>2c942c76414e43cc962f90de28116dc4</ims:sourcedId>
<ims:groupRecord>
<ims:sourcedGUID>
<ims1:refAgentInstanceID>YourSystemName</ims1:refAgentInstanceID>
<ims1:sourcedId>2c942c76414e43cc962f90de28116dc4</ims1:sourcedId>
</ims:sourcedGUID>
<ims:group>
<ims:groupType>
<ims:typevalue>
<ims:type>
<ims1:textString>Group</ims1:textString>
</ims:type>
</ims:typevalue>
</ims:groupType>
<ims:org>
<ims:orgName>
<ims1:textString>Course A Group C</ims1:textString>
</ims:orgName>
</ims:org>
<ims:extension>
<ims1:extensionField>
<ims1:fieldName>OrganisationAdress</ims1:fieldName>
<ims1:fieldType>String</ims1:fieldType>
<ims1:fieldValue>London</ims1:fieldValue>
</ims1:extensionField>
</ims:extension>
</ims:group>
</ims:groupRecord>
</ims:updateGroupRequest>
</soap:Body>
</soap:Envelope>
Response message
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<a:Action s:mustUnderstand="1">http://www.imsglobal.org/soap/lis/gms2p0/updateGroupResponse</a:Action>
<h:imsx_syncResponseHeaderInfo xmlns:h="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<imsx_version xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">V1.0</imsx_version>
<imsx_statusInfo xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<imsx_codeMajor>success</imsx_codeMajor>
<imsx_severity>status</imsx_severity>
<imsx_codeMinor>
<imsx_codeMinorField>
<imsx_codeMinorFieldName>TargetEndSystem</imsx_codeMinorFieldName>
<imsx_codeMinorFieldValue>fullsuccess</imsx_codeMinorFieldValue>
</imsx_codeMinorField>
</imsx_codeMinor>
</imsx_statusInfo>
</h:imsx_syncResponseHeaderInfo>
<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<u:Timestamp u:Id="_0">
<u:Created>2015-07-23T07:29:19.192Z</u:Created>
<u:Expires>2015-07-23T07:34:19.192Z</u:Expires>
</u:Timestamp>
</o:Security>
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<updateGroupResponse xmlns="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0"/>
</s:Body>
</s:Envelope>
View ArticleMethod description
createByProxyGroup is the method usedto create a group inCirrus.The difference with the createGroup method is that you don't need to provide syncId.
Message schema
Request parameters
Name
Data type
Description
groupRecord
Object
The group object. See mapping details here
Response parameters
Name
Data type
Description
sourcedId
GUID
ThesyncID of the created group
Example
Request message
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ims="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns:ims1="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0" xmlns:ims2="http://www.imsglobal.org/services/lis/mms2p0/wsdl11/sync/imsmms_v2p0">
<soap:Header>
<ims:imsx_syncRequestHeaderInfo>
<ims1:imsx_version>V1.0</ims1:imsx_version>
<ims1:imsx_messageIdentifier>0123456789</ims1:imsx_messageIdentifier>
</ims:imsx_syncRequestHeaderInfo>
</soap:Header>
<soap:Body>
<ims:createByProxyGroupRequest>
<ims:groupRecord>
<ims:sourcedGUID>
<ims1:refAgentInstanceID>YourSystemName</ims1:refAgentInstanceID>
<ims1:sourcedId>00000000000000000000000000000000</ims1:sourcedId>
</ims:sourcedGUID>
<ims:group>
<ims:groupType>
<ims:typevalue>
<ims:type>
<ims1:textString>Group</ims1:textString>
</ims:type>
</ims:typevalue>
</ims:groupType>
<ims:org>
<ims:orgName>
<ims1:textString>Course A Group C</ims1:textString>
</ims:orgName>
</ims:org>
<ims:extension>
<ims1:extensionField>
<ims1:fieldName>OrganisationAdress</ims1:fieldName>
<ims1:fieldType>String</ims1:fieldType>
<ims1:fieldValue>Berlin</ims1:fieldValue>
</ims1:extensionField>
</ims:extension>
</ims:group>
</ims:groupRecord>
</ims:createByProxyGroupRequest>
</soap:Body>
</soap:Envelope>
Response message
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<a:Action s:mustUnderstand="1">http://www.imsglobal.org/soap/lis/gms2p0/createGroupResponse</a:Action>
<h:imsx_syncResponseHeaderInfo xmlns:h="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<imsx_version xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">V1.0</imsx_version>
<imsx_statusInfo xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<imsx_codeMajor>success</imsx_codeMajor>
<imsx_severity>status</imsx_severity>
<imsx_codeMinor>
<imsx_codeMinorField>
<imsx_codeMinorFieldName>TargetEndSystem</imsx_codeMinorFieldName>
<imsx_codeMinorFieldValue>fullsuccess</imsx_codeMinorFieldValue>
</imsx_codeMinorField>
</imsx_codeMinor>
</imsx_statusInfo>
</h:imsx_syncResponseHeaderInfo>
<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<u:Timestamp u:Id="_0">
<u:Created>2015-07-23T07:05:39.490Z</u:Created>
<u:Expires>2015-07-23T07:10:39.490Z</u:Expires>
</u:Timestamp>
</o:Security>
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<createByProxyGroupResponse xmlns="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0">
<sourcedId>9c34d19065f74ca78e9b3cbce0343496</sourcedId>
</createByProxyGroupResponse>
</s:Body>
</s:Envelope>
View ArticleMethod description
deleteMethod is the method used to delete existing group in Cirrus. The group to be deleted shouldn't have any subgroups.
Important note: It's not possible to delete root group.
Message schema
Request parameters
Name
Data type
Description
sourcedId
GUID
The syncID of the group to be deleted
Response parameters
Empty.
Example
Request message
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ims="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns:ims1="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<soap:Header>
<ims:imsx_syncRequestHeaderInfo>
<ims1:imsx_version>V1.0</ims1:imsx_version>
<ims1:imsx_messageIdentifier>0123456789</ims1:imsx_messageIdentifier>
</ims:imsx_syncRequestHeaderInfo>
</soap:Header>
<soap:Body>
<ims:deleteGroupRequest>
<ims:sourcedId>6254b08ff5d145a3b46387f92db3e379</ims:sourcedId>
</ims:deleteGroupRequest>
</soap:Body>
</soap:Envelope>
Response message
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<a:Action s:mustUnderstand="1">http://www.imsglobal.org/soap/lis/gms2p0/deleteGroupResponse</a:Action>
<h:imsx_syncResponseHeaderInfo xmlns:h="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<imsx_version xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">V1.0</imsx_version>
<imsx_statusInfo xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<imsx_codeMajor>success</imsx_codeMajor>
<imsx_severity>status</imsx_severity>
<imsx_codeMinor>
<imsx_codeMinorField>
<imsx_codeMinorFieldName>TargetEndSystem</imsx_codeMinorFieldName>
<imsx_codeMinorFieldValue>fullsuccess</imsx_codeMinorFieldValue>
</imsx_codeMinorField>
</imsx_codeMinor>
</imsx_statusInfo>
</h:imsx_syncResponseHeaderInfo>
<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<u:Timestamp u:Id="_0">
<u:Created>2015-07-23T08:02:53.046Z</u:Created>
<u:Expires>2015-07-23T08:07:53.046Z</u:Expires>
</u:Timestamp>
</o:Security>
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<deleteGroupResponse xmlns="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0"/>
</s:Body>
</s:Envelope>
View ArticleMethod description
createGroup is the method usedto create a group inCirrus.
Message schema
Request parameters
Name
Data type
Description
sourcedId
GUID
The unique syncID of the group to be created
groupRecord
Object
The group object. See mapping details here
Response parameters
Empty.
Example
Request message
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ims="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns:ims1="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0" xmlns:ims2="http://www.imsglobal.org/services/lis/mms2p0/wsdl11/sync/imsmms_v2p0">
<soap:Header>
<ims:imsx_syncRequestHeaderInfo>
<ims1:imsx_version>V1.0</ims1:imsx_version>
<ims1:imsx_messageIdentifier>0123456789</ims1:imsx_messageIdentifier>
</ims:imsx_syncRequestHeaderInfo>
</soap:Header>
<soap:Body>
<ims:createGroupRequest>
<ims:sourcedId>2c942c76414e43cc962f90de28116dc4</ims:sourcedId>
<ims:groupRecord>
<ims:sourcedGUID>
<ims1:refAgentInstanceID>YourSystemName</ims1:refAgentInstanceID>
<ims1:sourcedId>2c942c76414e43cc962f90de28116dc4</ims1:sourcedId>
</ims:sourcedGUID>
<ims:group>
<ims:groupType>
<ims:typevalue>
<ims:type>
<ims1:textString>Group</ims1:textString>
</ims:type>
</ims:typevalue>
</ims:groupType>
<ims:org>
<ims:orgName>
<ims1:textString>Course A Group C</ims1:textString>
</ims:orgName>
</ims:org>
<ims:extension>
<ims1:extensionField>
<ims1:fieldName>OrganisationAdress</ims1:fieldName>
<ims1:fieldType>String</ims1:fieldType>
<ims1:fieldValue>Berlin</ims1:fieldValue>
</ims1:extensionField>
</ims:extension>
</ims:group>
</ims:groupRecord>
</ims:createGroupRequest>
</soap:Body>
</soap:Envelope>
Response message
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<a:Action s:mustUnderstand="1">http://www.imsglobal.org/soap/lis/gms2p0/createGroupResponse</a:Action>
<h:imsx_syncResponseHeaderInfo xmlns:h="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<imsx_version xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">V1.0</imsx_version>
<imsx_statusInfo xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<imsx_codeMajor>success</imsx_codeMajor>
<imsx_severity>status</imsx_severity>
<imsx_codeMinor>
<imsx_codeMinorField>
<imsx_codeMinorFieldName>TargetEndSystem</imsx_codeMinorFieldName>
<imsx_codeMinorFieldValue>fullsuccess</imsx_codeMinorFieldValue>
</imsx_codeMinorField>
</imsx_codeMinor>
</imsx_statusInfo>
</h:imsx_syncResponseHeaderInfo>
<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<u:Timestamp u:Id="_0">
<u:Created>2015-07-23T07:02:52.444Z</u:Created>
<u:Expires>2015-07-23T07:07:52.444Z</u:Expires>
</u:Timestamp>
</o:Security>
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<createGroupResponse xmlns="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0"/>
</s:Body>
</s:Envelope>
View ArticleMethod description
changeGroupIdentifier is the method used to change the syncID of an existing group in Cirrus.
Message schema
Request parameters
Name
Data type
Description
sourcedId
GUID
The oldsyncID of th group to be updated
newSourcedId
GUID
The newsyncID of the groupto be updated
Response parameters
Empty.
Example
Request message
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ims="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns:ims1="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<soap:Header>
<ims:imsx_syncRequestHeaderInfo>
<ims1:imsx_version>V1.0</ims1:imsx_version>
<ims1:imsx_messageIdentifier>0123456789</ims1:imsx_messageIdentifier>
</ims:imsx_syncRequestHeaderInfo>
</soap:Header>
<soap:Body>
<ims:changeGroupIdentifierRequest>
<ims:sourcedId>2c942c76414e43cc962f90de28116dc4</ims:sourcedId>
<ims:newSourcedId>6254b08ff5d145a3b46387f92db3e379</ims:newSourcedId>
</ims:changeGroupIdentifierRequest>
</soap:Body>
</soap:Envelope>
Response message
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<a:Action s:mustUnderstand="1">http://www.imsglobal.org/soap/lis/gms2p0/changeGroupIdentifierResponse</a:Action>
<h:imsx_syncResponseHeaderInfo xmlns:h="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<imsx_version xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">V1.0</imsx_version>
<imsx_statusInfo xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<imsx_codeMajor>success</imsx_codeMajor>
<imsx_severity>status</imsx_severity>
<imsx_codeMinor>
<imsx_codeMinorField>
<imsx_codeMinorFieldName>TargetEndSystem</imsx_codeMinorFieldName>
<imsx_codeMinorFieldValue>fullsuccess</imsx_codeMinorFieldValue>
</imsx_codeMinorField>
</imsx_codeMinor>
</imsx_statusInfo>
</h:imsx_syncResponseHeaderInfo>
<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<u:Timestamp u:Id="_0">
<u:Created>2015-07-23T07:30:29.585Z</u:Created>
<u:Expires>2015-07-23T07:35:29.585Z</u:Expires>
</u:Timestamp>
</o:Security>
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<changeGroupIdentifierResponse xmlns="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0"/>
</s:Body>
</s:Envelope>
View ArticleMethod description
changePersonIdentifier is the method used to change the syncID of an existing person in Cirrus.
Message schema
Request parameters
Name
Data type
Description
sourcedId
GUID
The old syncID of the person to be updated
newSourcedId
GUID
The new syncID of the person to be updated
Responseparameters
Empty.
Example
Request message
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ims="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<soap:Header>
<ims:imsx_syncRequestHeaderInfo>
<ims:imsx_version>V1.0</ims:imsx_version>
<ims:imsx_messageIdentifier>0123456789</ims:imsx_messageIdentifier>
</ims:imsx_syncRequestHeaderInfo>
</soap:Header>
<soap:Body>
<ims:changePersonIdentifierRequest>
<ims:sourcedId>fd842a1dbe9f47a6a258f14adcbc83b7</ims:sourcedId>
<ims:newSourcedId>8a01331b4a77426abf79341d4751362c</ims:newSourcedId>
</ims:changePersonIdentifierRequest>
</soap:Body>
</soap:Envelope>
Response message
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<a:Action s:mustUnderstand="1">http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0/IPersonManagerSyncPortType/changePersonIdentifierResponse</a:Action>
<h:imsx_syncResponseHeaderInfo xmlns:h="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0" xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<imsx_version>V1.0</imsx_version>
<imsx_statusInfo>
<imsx_codeMajor>success</imsx_codeMajor>
<imsx_severity>status</imsx_severity>
<imsx_codeMinor>
<imsx_codeMinorField>
<imsx_codeMinorFieldName>TargetEndSystem</imsx_codeMinorFieldName>
<imsx_codeMinorFieldValue>fullsuccess</imsx_codeMinorFieldValue>
</imsx_codeMinorField>
</imsx_codeMinor>
</imsx_statusInfo>
</h:imsx_syncResponseHeaderInfo>
<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<u:Timestamp u:Id="_0">
<u:Created>2015-07-17T10:21:57.781Z</u:Created>
<u:Expires>2015-07-17T10:26:57.781Z</u:Expires>
</u:Timestamp>
</o:Security>
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/>
</s:Envelope>
View ArticleMethod description
deletePerson is the method used to put into trashcan anexisting person inCirrus.
Message schema
Request parameters
Name
Data type
Description
sourcedId
GUID
ThesyncID of the person to bedeleted
Response parameters
Empty.
Example
Request message
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ims="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<soap:Header>
<ims:imsx_syncRequestHeaderInfo>
<ims:imsx_version>V1.0</ims:imsx_version>
<ims:imsx_messageIdentifier>0123456789</ims:imsx_messageIdentifier>
</ims:imsx_syncRequestHeaderInfo>
</soap:Header>
<soap:Body>
<ims:deletePersonRequest>
<ims:sourcedId>f9e110a5d08c403faa61362fcae6d6cb</ims:sourcedId>
</ims:deletePersonRequest>
</soap:Body>
</soap:Envelope>
Response message
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<a:Action s:mustUnderstand="1">http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0/IPersonManagerSyncPortType/deletePersonResponse</a:Action>
<h:imsx_syncResponseHeaderInfo xmlns:h="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0" xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<imsx_version>V1.0</imsx_version>
<imsx_statusInfo>
<imsx_codeMajor>success</imsx_codeMajor>
<imsx_severity>status</imsx_severity>
<imsx_codeMinor>
<imsx_codeMinorField>
<imsx_codeMinorFieldName>TargetEndSystem</imsx_codeMinorFieldName>
<imsx_codeMinorFieldValue>fullsuccess</imsx_codeMinorFieldValue>
</imsx_codeMinorField>
</imsx_codeMinor>
</imsx_statusInfo>
</h:imsx_syncResponseHeaderInfo>
<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<u:Timestamp u:Id="_0">
<u:Created>2015-07-17T10:02:00.471Z</u:Created>
<u:Expires>2015-07-17T10:07:00.471Z</u:Expires>
</u:Timestamp>
</o:Security>
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/>
</s:Envelope>
View ArticleMethod description
readPersonCore is the method used to read main person data from Cirrus.
Message schema
Request parameters
Name
Data type
Description
sourcedId
GUID
The syncID of the person to be read
Response parameters
Name
Data type
Description
personCoreObject
Object
The main person data. See details here
Example
Request message
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ims="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<soap:Header>
<ims:imsx_syncRequestHeaderInfo>
<ims:imsx_version>V1.0</ims:imsx_version>
<ims:imsx_messageIdentifier>0123456789</ims:imsx_messageIdentifier>
</ims:imsx_syncRequestHeaderInfo>
</soap:Header>
<soap:Body>
<ims:readPersonCoreRequest>
<ims:sourcedId>fd842a1dbe9f47a6a258f14adcbc83b7</ims:sourcedId>
</ims:readPersonCoreRequest>
</soap:Body>
</soap:Envelope>
Response message
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<a:Action s:mustUnderstand="1">http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0/IPersonManagerSyncPortType/readPersonCoreResponse</a:Action>
<h:imsx_syncResponseHeaderInfo xmlns:h="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0" xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<imsx_version>V1.0</imsx_version>
<imsx_statusInfo>
<imsx_codeMajor>success</imsx_codeMajor>
<imsx_severity>status</imsx_severity>
<imsx_codeMinor>
<imsx_codeMinorField>
<imsx_codeMinorFieldName>TargetEndSystem</imsx_codeMinorFieldName>
<imsx_codeMinorFieldValue>fullsuccess</imsx_codeMinorFieldValue>
</imsx_codeMinorField>
</imsx_codeMinor>
</imsx_statusInfo>
</h:imsx_syncResponseHeaderInfo>
<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<u:Timestamp u:Id="_0">
<u:Created>2015-07-17T10:13:25.626Z</u:Created>
<u:Expires>2015-07-17T10:18:25.626Z</u:Expires>
</u:Timestamp>
</o:Security>
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<readPersonCoreResponse xmlns="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0">
<personCore>
<sourcedId>fd842a1dbe9f47a6a258f14adcbc83b7</sourcedId>
<formname>
<formnameType>
<instanceVocabulary>http://www.imsglobal.org/vdex/lis/pmsv2p0/nametypevocabularyv1p0.xml</instanceVocabulary>
<instanceValue>
<language>en-US</language>
<textString>Full</textString>
</instanceValue>
</formnameType>
<formattedName>
<language>en-US</language>
<textString>Richard The Lionheart</textString>
</formattedName>
</formname>
<userId>
<userIdValue>
<language>en-US</language>
<textString>richardthelionheart</textString>
</userIdValue>
</userId>
</personCore>
</readPersonCoreResponse>
</s:Body>
</s:Envelope>
View ArticleProduct Update | 2016-04-08 | Cirrus Assessment
With great pleasure were announcing our latest product update April 8th2016. Changes include:
Marking: exporting candidate scores per question
Scheduling: assessment deadline removed from required steps
Improvements & bug fixes
Marking: New - exporting candidate scores per question
Weve now extended the options when exporting assessment results:
Candidate results
This export creates an Excel file with your candidates' results such as theirScore, Grade (if Grading Scale has been used) and whether they've passed or failed the assessment.
Candidate scores per question
This export to Excel show the scores of each candidate per question, for example:
Please note that this export is currently only available for 'fixed' assessments (i.e. not randomly generated ) that have fixed question navigation.
Assessing deadline removed from requiredsteps to scheduleyour assessment
When creating or scheduling assessments it is no longer required to set the deadline for assessing. This means Scheduling got one step quicker.
Improvements and bug fixes
As always we keep on making improvements and fixing bugs, in this release forexample:
Weve fixed a bug were in some cases the assessor of an assessment were not displayed correctly after you removed one.
Delivery: the restore button for candidates was sometimes responding slowly. Weve fixed that.
Under Marking > Grades by score: now shows the Grades for you Assessment highest to lowest.
Were proud of our performance in delivering assessments. With this release weve also made some improvements for the performance under Authoring.
Please do not hesitate to contact us. You can send us your thoughts and comments at .
Best Regards,
The Cirrus Assessment Team
View ArticleDear all,
What:
Please be informed that we will perform some scheduled maintenance to the Cirrus Platform - all our environments will be affected.
When:
Start:Friday April 10th 23:00 PM CET (2016)
End: Saturday April 11th 04:00 AM CET (2016).
Impact:
No downtime is expected. However in some cases the Cirrus platform might be less responsive. In very rare cases your environmentmight be unavailable for 10-15 minutes.
What can / should you do?
Please do not schedule any exams during this period - in case this cannot be avoided please contact us before Friday April 15th.
Questions:
Should you have any questions, please contact us via [email protected]
Best Regards,
The Cirrus Assessment Team.
View ArticleProduct Update | 2016-02-12 | Cirrus Assessment
With great pleasure were announcing our latest product update today. Changes include:
Item chance score now visible in collections
User import improved
Bug fixes and improvements
Item chance score now visible in Collections.
Authors can now seethechance score of an Item by opening a collection and going to the Statistics Tab:
User import improved
The restriction that imported users should have a unique e-mail address has been removed. More information on importing users.
Bug fixes and improvements
As always we keep on making improvements and fix bugs, this release forexample
Several minor fixes in the naming of questions and in system messages. Examples include the message when deleting schedules that are 'in use'. We've removed a bunch oftypo's and improved several translations in both Dutch and English. Thanks for reporting these!
Improved the widget on the Dashboard after customer feedback to show the right amount of schedules and the number of Not Marked assessments from the widget should be the same as the items from Marking screen.
In rare casessuggestions appeared for the candidate in form fields if another candidate had taken the same question within the same browser session. We've taken care of this.
We've improved our performance and will give an update on this in the coming weeks.
Please do not hesitate to contact us. You can send us your thoughts and comments at .
Best Regards,
The Cirrus Assessment Team
View ArticleProduct Update | 2016-03-02 | Cirrus Assessment
With great pleasure were announcing our latest minor product update today, March 2nd.
Bug fixes and improvements
This release is mainly geared towards improvements made followingour successful tests to benchmark our performance.
Weve changed title of column "Questions" to "Items" in our Library (at Cirrus we use both interchangeably).
Weve changed the icons for Learning Objectives.
Please do not hesitate to contact us. You can send us your thoughts and comments at [email protected].
Best Regards,
The Cirrus Assessment Team
View ArticleProduct Update | 2015-12-31 | Cirrus Assessment
First of all: best wishes from all of us at Cirrus for 2016. As some of you have already noticed, we got a head start with our first Cirrus Platform product update which became available right at the start of 2016! Changes include:
Improved Scheduling
We have improved the options available when adding invigilators to you scheduled assessments. You can now not only search by name, but also very easily use hierarchies or roles to search and add the correct invigilators! Also, when adding candidates more information is available during selection.
Custom Skinning now available!
Starting this month you can opt for your own custom skin for your Cirrus environment. Love our product, but looking to customize it to match your own professional branding? This can now be done using a skin that includes for example your own logo, a branded background at login and custom colors for buttons. For more information contact your sales-representative of mail [email protected].
Marking: publishing results
When Scoring and Grading of an assessment is finished, you can now publish all results with or without sending an email to the candidates involved.
Improved usability when creating Assessments
Based on your feedback, weve added buttons to explicitly save and go to the next step when creating Assessments. When you are completely done, this will be indicated as you will automatically get a button to publish your assessment.
Bug fixes and improvements
Several bugs have been fixed, for example regarding the import of Learning Objectives, showing the correct information on (anonymous) candidates when marking. Also the reset password now has improved instructions..
Looking forward to your feedback in 2016!
Please do not hesitate to contact us. You can send us your thoughts and comments at [email protected] or simply reply to this email.
Have a great year!
The Cirrus Assessment Team
View ArticleProduct Update | 2016-03-14 | Cirrus Assessment
With great pleasure were announcing our latest minor product update today, March 14th.
Bug fixes and improvements
Improvements include:
Finishing off lessons learned from tests to benchmark our performance.
The extended match question now has a minimum 2 matches and 2 choices (used to be 3).
Small security fixes in our HTTP headers.
Please do not hesitate to contact us. You can send us your thoughts and comments at [email protected].
Best Regards,
The Cirrus Assessment Team
View ArticleProduct Update | 2016-02-04 | Cirrus Assessment
With great pleasure were announcing our latest product update today. Changes include:
Sowiso questions: added the 'test usage' field'
Export to Excel
Bug fixes and improvements
Maths questions: added the 'test usage' field and 'opposite evaluation'.
We've added the ' test usage ' field and ' opposite evaluation ' to our Maths questions developed with our partner Sowiso. This offers advanced scoring abilities in the form ofpartial scores. For instance, when somebody answers x=4/2 in stead of x= 2, you can use this in tests to score the first answer as 80%, and the second as 100%.
Export to Excel
Cirrus now offers the possibility to export certain question types to Excel, most notably Multiple Choice and Essay Items.
Bug fixes and improvements
As always we keep on making improvements and fix bugs, for example a bug was fixed were some Hotspot questions crashed when editing them.
Please do not hesitate to contact us. You can send us your thoughts and comments at .
Best Regards,
The Cirrus Assessment Team
View ArticleProduct Update | 2015-12-16 | Cirrus Assessment
With great pleasure were announcing our next Cirrus Platform product update, available from Wednesday 16th December 2015. Changes include:
Work has started on generation of random assessments (LOFT)We have improved the underlying logic for generating assessments in order to prepare for Linear On the Fly Tests (LOFT). Keep following our updates to see when this will become available!
User management integrationIn order to improve synchronising of users with a user management system, we've added a synchronisation key field for users.
ImprovementsWe've improved the general performance of the Cirrus platform in order to cater for a much higher number of users. As always several user interface improvements have been made in order to make the Cirrus platform even more user friendly.
Bug fixesSeveral bugs have been fixed, for example regarding the ability to compare revisions of questions but also in the rich text editor it is now possible to to paste text from Word using the designated button.
Please note: we have discovered a possible issue with the rich text editor in the candidate delivery. This is why we have disabled the rich text editor for candidates until this has been resolved.
Keep sending us your feedback!
Please do not hesitate to contact us. You can send us your thoughts and comments at [email protected] or simply reply to this email.
Have a great week!
The Cirrus Assessment Team
View ArticleDisclaimer
This website including all its contents are subject to copyright and must not be reproduced or distributed without permission from Cirrus Assessment or without stating Cirrus Assessment as the source of the material.
The Cirrus Assessment platform is constantly evolving and improving. We do our best to keep all our documentation up to date and in line with these developments. Please let us know if we missed something! The customer Success team and Cirrus Assessment are not liable for any errors following the use of this document.
View ArticleProductUpdate| 2015-10-30 | Cirrus Assessment
We can now announce our next Cirrus Platform product update, available from Friday 30th October 2015. Changes include:
Polytomous/dichotomous scoring for Match questions
If amatch questionis answered partially correctly, candidates can now receive apartial score. For this type of question youwill now need to select if you want Polytomous or dichotomous scoring.
Filtering
Many of you will be happy to hear that selected filters will now be remembered when returning to a filtered list. You will also notice that when filtering within a collection, the filter has been moved to the left hand side to make it more consistent with filtering in other parts of the platform.
Improved usability
We've added page titles on each page to improve usability. We've improved scrolling: nano scrollers are removed and browser-default scrolling is used instead throughout the application. The column header will stay in place when scrolling long tables, plus many usability improvements to make the tables more readable. Last but not least we've improved the modal dialog windows: the size of the windows will be more responsive, for example when there is lots of data to show. Also the layout is more in line with our new design
'Marking start/end' now will be 'Assessing deadline'
We've removed start date for assessing. This means the assessor can start assessing as soon as the first candidate submits the answer. When scheduling you will still need to set the deadline for assessing.
And more...
We continue to improve the SOWISO mathematical question integration. Whats more: over 30 other general improvements and fixed have also been made!
Keep sending us your feedback!
Please do not hesitate to contact us.You can send us your thoughts and comments at [email protected] or simply reply to this email.Have a great week!
The Cirrus Assessment Team
View ArticleProduct Update | 2015-12-02 | Cirrus Assessment
With great pleasure were announcing our next Cirrus Platform product update, available from Wednesday 2nd December 2015. Changes include:
Embedding video just got better
When you for example add a YouTube video, you can now add start and stop parameters. Please note that we use a HTML5 player - as the flash player is no longer considered up to standard by the industry (including YouTube itself).
New: Extended Match question Weve added a new question type: the Extended Match question. This allows you to enter elements and corresponding matching aspects. The matching aspects can be text, image or sound, or a mix of all these. The order will be randomly shuffled for your candidates.
Numerous visual improvements
As always we pride ourselves on the usability and design. This quest continues with improved widgets (Invigilation and Marking), clearer status styling and improved styling of the Learning Objectives repository.
Improved integration capabilitiesFor automated user imports weve added unique IDs on hierarchies.
And many more
Based on user feedback weve started to improve the print function under invigilation. Weve fixed a file upload bug and done much, much more. Over 20 other general improvements and fixed have also been made!
Keep sending us your feedback!
Please do not hesitate to contact us. You can send us your thoughts and comments at [email protected] or simply reply to this email.
Have a great week!
The Cirrus Assessment Team
View ArticleWe train the best...
To ensure the most effective adoption and use of the Cirrus Platform within your organisation, we offer training, webinars and inspirational sessions to our customers.
When you opt for the intuitive design of the Cirrus Platform, we will assist you by providing training to you and your colleagues. This will give everyone the knowledge and skills to immediately create great assessments that seamlessly fit within your organisation.
Our training programme consists of the following modules:
Cirrus Introductory Course:
This course is for anyone involved in using the Cirrus Platform within your organisation. It covers the complete lifecycle of digital examinations or e-Assessments using Cirrus.
Participants will get an overview of Item (bank) creation and maintenance, Delivery, Invigilation and Marking using Cirrus. This will be followed by a hands on focus session on creating Items and Assessments using the Cirrus Platform.
More information on the Cirrus Introductory Course
Cirrus Advanced Course:
During this course participants will gain insights and develop skills to ensure the effective delivery of your e-Assessments using the Scheduling, Invigilation and Marking features. We will also look into the power of using Taxonomies, Hierarchies, Blueprints and defining Roles within the system.
More information on the Cirrus AdvancedCourse
Cirrus Administration Course:
This course offers an overview of the Scheduling, Invigilation and Marking tools. It provides an in depth look at the setup and management of system wide settings such as Roles, Hierarchies, Learning Objectives and User-Management.
Together with our customers, we ensure that each organisation has at least one (or more) Cirrus Assessment Certified Super User(s). These are the gatekeepers of all things related to the Cirrus Platform. They will also have full access to our documentation and support to ensure your success.
More information on the Cirrus AdministrationCourse
Certified Super User
A certified Cirrus Assessment Superuser has successfully completed the Cirrus' Introductory Course and at least one of the following: the Cirrus Advanced Course, the Cirrus Administration Course.
Want to schedule a training? Need more information?
Want to schedule a training? More information on specific training and consultancy for your organisation? Contactus via [email protected] !
View ArticleAbout the Cirrus Introductory Training
Goals
Target Audience
Contents
More information
Goals
After completing the Cirrus Introductory Training course, participants will have a basic understanding of the way the Cirrus Platform can be used in the creation and delivery of questions and assessments. They will immediately be able to start creating Items and Assessments and be aware of other steps and roles involved in the assessment process.
Target Audience
New Cirrus Platform users (authors / teachers, staff) from your organisation. Those who work either directly in the system (as constructors, question authors, assessors or moderators) or indirectly (project managers, co-authors) and who have not previously used the system.
Contents
The Introductory Course will focus on gaining the basic knowledge and skills required to begin using the Cirrus Platform to create items and assessments.
Overview / Approach
An introduction to e-assessment using the Cirrus platform. This is followed by hands-on exercises using your custom training environment. During the training, the following topics will be covered:
Global overview of creating and delivering assessments
Overview of the Cirrus Platform interface
Item construction: different question types and options for creating digital questions
The development cycle of questions and assessments and the different roles involved
Candidate view: the candidate experience when taking an assessment
More information:
Duration: 180 minutes Trainer: one of our experienced consultants Group size: 4-10 people
Contact us via: [email protected]
View ArticleAbout the Cirrus Advanced Training
Goals
Target Audience
Contents
More information
Goals
After completing the Cirrus Advanced Training course, participants will be proficient in the use of the Delivery (Scheduling / Invigilation) and Marking tools in the Cirrus Platform.
Target Audience
Cirrus Platform users (authors / teachers, staff) who have successfully completed the Introductory training course and have begun to create item(banks) and assessments using the Cirrus Platform within their organisation.
Contents
The Advanced Course focuses on the different options for Delivery. The training can focus either on Marking or on giving an overview of Delivery.
Overview / Approach
Youve got your Items and Assessments ready, now its time to dive into one of the advanced modules. Training will be via hands-on exercises in your custom training or production environment and will include:
The sharing of experiences and best practices
How to deliver: Scheduling and Invigilating Marking your assessments.
Reflection: the development cycle of items and online assessments within your own organisation.
More information:
Duration: 180 minutes Trainer: one of our experienced consultants Group size: 4-10 people
Contact us via: [email protected]
View ArticleAbout the Cirrus Administrator Training
Goals
Target Audience
Contents
More information
Goals
After completing the Cirrus AdministratorTraining course, participants will be proficient in the use of the Administration Panel in the Cirrus Platform and have enough knowledge of Delivery(Scheduling / Invigilation) and Marking tools to facilitatetherequirements for the construction and distribution of items and assessments.
Target Audience
This in-depth course is designed for those users responsible for ensuring that the Cirrus Platform meets user requirements for the construction and distribution of items and assessments..
Contents
This Administrator training offers an overview of Scheduling, Invigilation and Marking. It provides an in depth look at the setup and management of system wide settings such as Roles, Hierarchies, Learning Objectives and User-Management.
Overview / Approach
Hands on training on the configuration of platform settings and advanced functions needed by Authors, Schedulers and Markers to support the effective creation of Item Banks, Assessments and Delivery.
Attendees are requested to think up-front about the way e-Assessment fits within their organisation. This is followed by ample opportunities for hands-on exercises based on realistic scenarios relating to your organisation and candidates, covering:
Analysis of requirements for your organisation
Detailed analysis of the admin panel in the Cirrus Platform.
Management of Roles, Hierarchies, Learning Objectives and Users
More information:
Duration: 180 minutes Trainer: one of our experienced consultants Group size: 4-10 people
Contact us via: [email protected]
View ArticleProduct Update | 2015-11-13 | Cirrus Assessment
With great pleasure were announcing our next Cirrus Platform product update, available from Friday 13th November 2015. Changes include:
Adding a collection just got easier
When you add a new collection, the modal window now contains informative descriptions helping you on choosing the right Hierarchy, Learning Objectives and Taxonomy.
Marking Essay / File ResponseWeve improved the right side bar when assessing an Essay or File response Item making it easier to make and view annotations. Let us know what you think!
Improved usability
As always we keep on improving our User Interface and design. For example, weve improved the responsiveness of the application to better suit lower resolution, changed the interaction when opening files during the assessment - candidates are no longer asked to leave the assessment-page.
And many more
Whats more: over 20 other general improvements and fixed have also been made!
Keep sending us your feedback!
Please do not hesitate to contact us. You can send us your thoughts and comments at [email protected] or simply reply to this email.
Have a great weekend!
The Cirrus Assessment Team
View ArticleProduct Update | 2015-09-18 | Cirrus Assessment
Were extremely proud to announce the release of a new version of the Cirrus platform on Friday 18th of September. Changes include:
New look and feel: Much effort has gone into analysing the existing interface and finding improvements to the usability. Our aim is to create the most user-friendly and intuitive e-assessment platform on the market and we look forward to hearing your feedback on these changes.
Improved marking workflow: With the new release, the Cirrus platform now supports workflow for multiple assessors and moderators. Assessments will automatically be marked for moderation if required.
Improved assessing of essay and file response questions. It is now possible to view the annotations of your co-assessor. Furthermore we have made the navigation easier (horizontal assessing).
SOWISO mathematics question: In conjunction with our partner SOWISO, we have created an additional question type, specifically for exact sciences courses. If you would like to know more then do not hesitate to contact us.
IMS LIS - Integration:Is your user management compliant with standards set in IMS Learning Information Services (LIS)? User management just became a whole lot easier as it can now be setup through APIs...
Whats more, we have also made over 100 other general fixes and improvements...
Wed love to hear your feedback - please do not hesitate to contact us about this update to the Cirrus Platform.
You can send us your thoughts and comments at [email protected] or simply reply to this email.
The Cirrus Team!
View ArticleProduct Update | 2015-10-16 | Cirrus AssessmentWith great pride we bring our latest release to you, available from Friday 16th October 2015. Changes include:New: section pagesIt is now possible to add section pages within a collection. Section pages can be used to describe case questions. We're working hard to add functionality for grouping questions in our next release.Rich-text editor improvements and fixesSeveral minor issues were reported when adding video: layout and playback should work smoothly with MC questions again.Please note: due to a potential security risk we've disabled the 'source code' option in the rich-text editor.New: coloured status boxesNow you can see the status of your Items, Collections and Assessments at a glance: status boxes now have colours!General fixes and design improvementsAs always we keep improving our design and fixing bugs. Examples in this release include the way questions are displayed, fixes to the breadcrumb (navigation) and improved translations in Dutch.
For Items it is now no longer possible to set the score to 0. A question marked 0 will no longer be shown as 'correct'. Also 'Save' and 'Save and New' will now be disabled if the author has no permissions within a collection.Keep sending us your feedback!
Please do not hesitate to contact us.You can send us your thoughts and comments at [email protected] or simply reply to this email.Have a great weekend!
The Cirrus Assessment Team
View ArticleProduct Update | 2015-10-02 | Cirrus Assessment
First of all, wed like to thank everyone for their responses to our last update. We value your input!
This is why were very happy to announce the new version of the Cirrus platform, to be released on Friday 2nd October 2015. Changes include:
A new and fresh text editor with the possibility to add web 2.0 contentThis will enable you to add YouTube and Vimeo videos to Questions. Weve also added the option to embed Google maps.
Improvements to the candidate deliveryWeve improved the layout and business logic to ensure the best experience for your candidates.
Look and feel...Thanks for your positive feedback and remarks after our update last month which included our complete new look and feel. Well continue to improve and polish our interface with your help!
SOWISO integration Additional improvements and some bug fixing together with SOWISO. Advanced mathematical questions now available in high-stakes assessments. For more info on this great addition for exact sciences courses contact us.
A bug found in Safe Exam Browser has been fixed. Whats more, we have also made over 80 other general fixes and improvements...
Wed love to hear your feedback - please do not hesitate to contact us about this update to the Cirrus Platform.
You can send us your thoughts and comments at [email protected] or simply reply to this email.
The Cirrus Team!
View Article
Working at CIRRUS LOGIC INC
CIRRUS LOGIC INC's Competitors
Recently Asked Questions
Recent CIRRUS LOGIC INC Employee Reviews
- My overall experience at Cirrus Logic is extremely rewarding
- Cirrus Logic really cares for the health and safety of its employees. Plus they offer activities that help us build good collaboration within our teams and across the company. And we have activities that are just fun.
- Their semi conductors are the best