Changing name of a module exposing service actions
271
Views
6
Comments
Out of scope
References

Suppose that 

  • I have a Service module, exposing a service action (under the hood rest endpoint).
  • I have a consumer application that references this service action.
  • I change the name of the service module.

This change does not result in an incompatible/outdated consumer in service studio. 

Now on run time I do get errors when I use the logic that uses the service action. This is understandable ofcourse since in the service action is just a rest endpoint (and changing the name, means the url path is changed).

However, since the consumer is known, it would be so nice to have a TrueChange warning during deployment of outdated consumers. 

Changed the category to
References

Honestly, this reads more as a bug, agree that at least a TrueChange warning during 1CP of outdated consumers should be created.

Changed the status to
Out of scope

Hi,

This problem seems already to be fixed in platform version 11.17.0:
https://www.outsystems.com/downloads/ScreenDetails.aspx?MajorVersion=11&ReleaseId=20060&ComponentName=Platform+Server

Given that this release is already available prior to you creating the idea, I marked it as out-of-scope.

Regards,

Daniel

Changed the status to
New
Changed the status to
Out of scope

Hi,This problem seems already to be fixed in platform version 11.17.0: 

https://www.outsystems.com/downloads/ScreenDetails.aspx?MajorVersion=11&ReleaseId=20060&ComponentName=Platform+Server

Given that this release is already available prior to you creating the idea, I marked it as out-of-scope.

Regards,

Daniel

2016-04-21 20-09-55
J.
 
MVP

I agree it sounds like a bug, after all, that's why we have service actions. Otherwise we could simply use webservices.