While trying to create a new item of segment type using im createsegment command through SoapUI, I get the state of the newly created item as 'Unspecified'. Ideally, the new item created should automatically move to the state 'Proposed' as seen in the workflow diagram below but it's not happening.
In the request below, the type 'Requirement Document' is a Segment type. I get a successful response and the item is created but the state is 'Unspecified' rather than 'Proposed'. Is this behaviour expected or are there any configuration changes that I need to do so that the new item I create moves to the 'Proposed' state automatically when it is created?
<ns2:Envelope xmlns:ns4="http://webservice.mks.com/2009/Generic" xmlns:ns3="http://webservice.mks.com/2009/Generic/schema" xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/"> <ns2:Header/> <ns2:Body> <ns4:command> <arg0> <ns3:Username>myusername</ns3:Username> <ns3:Password>mypassword</ns3:Password> <ns3:Application>im</ns3:Application> <ns3:Command>createsegment</ns3:Command> <ns3:Option Name="type">Requirement Document</ns3:Option> <ns3:Option Name="field">Project=/MyProject</ns3:Option> <ns3:DateTimeFormat>d-MMM-yyyy h:mm:ss a</ns3:DateTimeFormat> </arg0> </ns4:command> </ns2:Body> </ns2:Envelope>
I'm working on version 10.8 if that helps, and I've checked the permissions and the mandatory fields to see that they are being populated properly.
A quick glance at this, makes me suspect that this behaviour is because you aren't supplying field values for all the mandatory fields. Something besides State, although it seems "State" could be a mandatory too?
I can't recall off-hand the behaviour of the "im createsegment" command, but I think this may be by design, as the only alternative would be to fail the command without the mandatory fields, when trying to manually create the segment in this fashion.
You may want to open a Support case to confirm, with the details, but I think that is probably why you're seeing this.
The 'Proposed' state has no fields set as mandatory, so I doubt it's failing for Mandatory fields.