89
Views
5
Comments
Solved
Service module not in Module alias rules
Question

I recently converted one of my modules to Service Module in OS11. Before that, i had a Module Alias linked to that module on my dev environment.

When i transferred it to our int environment i found that i could not find the module in the alias list (SEO Friendly URLs - Module Alias Rules).

I was able to create the alias by republishing the older (not service module) version of the module and then transfer it back after the creation.


Is this a bug or is there a reason why Service modules are not selectable for creating a module alias?

2018-05-30 02-48-38
Rui Barbosa
Solution

So depending on your use case you have a few options:

  1. Create a non service module just for the API and use your SEO rule
  2. Rename the existing module to match the name you want

If the name issue is deeper on the API url path, you can also customize the URL path of the methods.

Something like this:



Cheers

2020-09-01 10-42-42
Stefano Valente

Rui Barbosa wrote:

So depending on your use case you have a few options:

  1. Create a non service module just for the API and use your SEO rule
  2. Rename the existing module to match the name you want

If the name issue is deeper on the API url path, you can also customize the URL path of the methods.

Something like this:



Cheers

 Thank you. I will mark this one as solution, but i actually hope Outsystems will add Service Modules with an exposing webservice to the list of Modules in the SEO.


For now i will keep module structures as they are and add my publish old version magic to our release/deployment script. But you are correct this is not something i would like to maintain. I will need to split the modules and move logic accordingly. 

 

2018-05-30 02-48-38
Rui Barbosa

Hi Stefano Valente 

So I guess its by design...

Service modules don't have entry points besides the REST api's, so there should be little need to apply an SEO rule.

But please do elaborate on your use case.

Cheers

2020-09-01 10-42-42
Stefano Valente

Rui Barbosa wrote:

Hi Stefano Valente 

So I guess its by design...

Service modules don't have entry points besides the REST api's, so there should be little need to apply an SEO rule.

But please do elaborate on your use case.

Cheers

We had just set a Module alias in place for the REST service (to have a more appropiate url). Then i decided to convert the module to a Service module so i could have a Service action without the Authorisation component to be used from our own UI.


The module alias was still active on our DEV environment. But when i exported the module to our INT environment for the first time as a service module, i could not select the module in SEO. After i published the previous version with the regular module, i could create the alias and publish back the new version (the service module version).


Perhaps service modules are not meant to be used this way, but since it is possible to create webservice in them, i would expect there is a possibility to have an alias in SEO.




 

2018-05-30 02-48-38
Rui Barbosa
Solution

So depending on your use case you have a few options:

  1. Create a non service module just for the API and use your SEO rule
  2. Rename the existing module to match the name you want

If the name issue is deeper on the API url path, you can also customize the URL path of the methods.

Something like this:



Cheers

2020-09-01 10-42-42
Stefano Valente

Rui Barbosa wrote:

So depending on your use case you have a few options:

  1. Create a non service module just for the API and use your SEO rule
  2. Rename the existing module to match the name you want

If the name issue is deeper on the API url path, you can also customize the URL path of the methods.

Something like this:



Cheers

 Thank you. I will mark this one as solution, but i actually hope Outsystems will add Service Modules with an exposing webservice to the list of Modules in the SEO.


For now i will keep module structures as they are and add my publish old version magic to our release/deployment script. But you are correct this is not something i would like to maintain. I will need to split the modules and move logic accordingly. 

 

2018-05-30 02-48-38
Rui Barbosa

Stefano, thanks for the feedback.

I'm forwarding this thread to our engineering team, but if you could create this on the ideas section that would be great.


Cheers

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.