composer issue

[avkumar15]

scenario :

when we are trying to write any service in composer, at that time we have an option below to go at some reference service, which is non-editable, i.e. there is nobody can write any text on that box by keyboard input. But there is one way, it can take input which is the input parameter of the above service when we click the arrow button and that box is already selected then it will take that text and put it in that text box. Real problem is there is no option there to retrieve it from there. As a working solution we need to go on that reference service to edit it.

Thingworx version : 8.4.3

[slangley]

Hi @avkumar15.

Are you saying that no one is able to make updates in the script area?  If so, do you experience the same behavior using the Administrator account?  This could be a permissions issue.

If not a permissions issue, do you experience the same issue when testing under a different browser?

Regards.

--Sharon

[posipova]

Are you talking about system services that are part of the template (for example)? Or are you creating a new service in  a new thing (created by a user) and trying to use one of the snippets or "other entities" services? A screenshot would be helpful.

[VladimirRosu]

This is actually a bug, witnessed on 8.5.2 as well.

Consider you

1. Edit a service which has input parameters,

2. Click on the reference tab (usually on the bottom of the page)

3. Select any other service in the reference tab

4. Click in the service editor for the service you wanted to edit (meaning do not click on the reference service editor)

5. Click on the input arrow next to one of the service parameters

What happens:

Input parameter is added in the service you edited, but also in the reference code editor. The change is persisted also in the reference service code if you save the entity. 

Expected behavior:

Input parameter is added only in the service you edited.

Tech Support ticket 15217211 raised for this issue.

[slangley]

Hi @avkumar15.

I checked the internal case and at this time, it has not been designated for a specific future release.  I will monitor the case and as new information becomes available, I will post it here.

Regards.

--Sharon

[slangley · Accepted solution]

Hi @avkumar15.

This issue has been addressed in version 8.4.10 (as well as 8.5.6) which was released last week.  If you still have issues after upgrading, please let us know.

If this response has resolved your issue, please mark it as the Accepted Solution for the benefit of others on the community.  And thank you for participating in our community!

Regards.

--Sharon