Skip to main content
E
ErickEstrada1-Visitor
1-Visitor
April 24, 2020
Question

Integrity Requirements Connector failure with Mapping

  • April 24, 2020
  • 2 replies
  • 3860 views

 Good Day,

 

While doing the setup for the IRC, in Mapping options, I got a some issues referring to:

  1. "api exceptions"
  2. failed to read "itemconstraints"
  3. failed to read document definition

If I interpreted well, at least for the 2nd point, I got admin rights and the message said I might not be authorized.

 

Thank you.

2 replies

M
MichaelChatel5-Regular Member
5-Regular Member
April 28, 2020

Erick,

It would be helpful to provide the entire error/console message, from IRC, or some screenshots to show what you're seeing.

You may want to open a Support case for this.

 

Given the brief info available, if I had to guess at your issue, it sounds like it could be one of the known SPRs depending on your Integrity / IRC versions (what are they?), in relation to constraints:

Maybe,

https://www.ptc.com/en/support/article/CS244789

or

https://www.ptc.com/en/support/article/CS250963

 

If you can provide more info, I'm sure it can be figured out. 

 

 

    M
    MichaelChatel5-Regular Member
    5-Regular Member
    April 29, 2020

    Just to follow-up;

     

    Were one of those articles the situation you were seeing, or did you open a Support case instead?

    E
    ErickEstrada1-VisitorAuthor
    1-Visitor
    April 29, 2020

    Hello Michael,

     

    Thank you for your response, unfortunately those articles are not applicable for my situation.

    My colleague create a Support case (C15377533) with a more detailed explanation.

     

    Thank you.

    L
    LLawton16-Pearl
    16-Pearl
    April 29, 2020

     

    (Second, shorter version, first one got lost)

    This is about question #2 "itemconstraints".

    We are using IRC 3.4 with Integrity 11.2  The two articles above apply to earlier versions, especially the second one that says that the problem was fixed in 11.1.

    It seems this undocumented command's purpose is to determine the constraints on an item type by actually creating one item, but with the permissions assigned to the user running it.

    I ran the command against every type in my system and the bottom line is this: every document node type fails with "internal error MKS156897' (e.g. Test Case). That error code only applies to document nodes.

    The login I used has all admin rights and all edit rights on all fields and transitions, and there are no mandatory fields.

    I think the error has to do with the fact that the Integrity system prevents creating node items directly. So we need to hear from Requirements Connector support or development.

    Terms & ConditionsCookie settingsAccessibility statement