How to know template name of an existing extension in Hybris - sap-commerce-cloud

If you have been provided a hybris extension code, how can we know it is generated using which template. For example, if I have been given an extension code, I want to know it is ycommercewebservice or ywebservice or yaccelatoraddon ?

I'm not 100% sure, but I think this is not possible. A lot of extensions are not generated using a template at all (but just from scratch by manually creating the required files and directories), so I don't think it is noted anywhere during the creation process.

Related

Customizing CRCreateActions Extensions in Acumatica 2022R1

We are currently in the process of a much needed upgrade from Acumatica 2019R2 to 2022R1 and are running into some questions that we are unable to locate information for. At some point in between the versions the workflow engine was created and also extracted the actions away into extensions in CRCreateActions.
Is there documentation anywhere that explains this new process? From what we can tell, if you want to customize these actions and override a method that the extension did not override you must create your own action extension and go from there. This then means you must also extend the worflow extension in order to swap out the action in the workflow. This feels like we are going down the wrong path.
What is the correct approach to extend what used to be ConvertToBAccount but is now called CRCreateBothContactAndAccountAction?

Creating new extension

I have to write code for consuming a SOAP web service using some WSDL files.
Is it a good idea to create a new extension for this specific task or should we use the available extension generated via modulegen?
For separation of concerns, you can create a new extension, but it's up to you.
However, if you need to use a different kind of template (e.g. ybackoffice, instead yempty), you will need to generate another extension based on the other template.

Custom statuses in Liferay's workflows

I want to make an workflow that has other statuses than the Single Approver workflow, other than "Update", "Approved" etc. Is it possible?
What I have found on Internet is how to create custom portlets and I am not sure I have to go so far. I understand that these statuses are constants from the WorkflowConstants.java file and that it is possible to extend that file in order to add my own constants. But where should I place that file? What other changes do I have to make to make it work?
Thank you.
Liferay has offered different approaches to extend and customize liferay portal depending on the nature and complexity of changes required.
Following are the possible ways:
1. via Extension (ext) environment
2. via Plugins
i. Portlet
ii. Hook
Using extension environment, you can simply move that file from portal source to the relevant package of ext and introduce changes.
Lets say, WorkflowConstants.java resides at location
\portal-service\src\com\liferay\portal\kernel\workflow\WorkflowConstants.java in portal, so you can copy that file to \ext-service\src\com\liferay\portal\kernel\workflow\WorkflowConstants.java.
Make required changes in ext-service file and deploy ext. One restarting container changes will reflect.

add custom webpi feed programmatically

Is it possible to add custom feed programmatically to Web Platform Installer? I tried adding the feed manually and found that the feed location is stored in `%APPDATA%\Microsoft\Web Platform Installer\web.preferences file. However the file seems somewhat cryptic and I would not like to modify it manually. Is there any API for that?
Update: even if this web.preferences file could be edited it is not the way to go as it is user specific file and I need system wide configuration.
Based on this link,
Sorry, there isn't a way to do that currently (for security reasons,
we don't allow an untrusted feed to be loaded without the user's
consent)
Once the feed is added via the Options dialog, it does persist between
sessions
I think we can't add custom feed without intervene from user. Maybe you can use WebpiCmd.exe
that can be configured programmatically via scripts.
C:\Program Files\Microsoft\Web Platform Installer>WebpiCmd.exe /List /Feeds:http://yourcustomwpifeed.co.id/customFeed.xml
A little late, but maybe it may interest others. You can modify the file %APPDATA%\Microsoft\Web Platform Installer\webpi.preferences. Yes, it is a little cryptic, but here's my post about how to do it.
The file webpi.preferences is user-specific. If you want to set settings for all users, all I can think of is to write a bootstrapper application that first modifies webpi.preferences (using the code in the post) and then runs WebPlatformInstaller.exe.

Localize SharePoint 2010 Folder Names

I'm looking for a way to localize SharePoint 2010 Folder Names, for a specific application.
I've seen that site names/description are automatically translated, and it seems like SharePoint 2010 supports "multilingual" fields for metadata - but I haven't been able to apply this successfully for folder names.
The folders are automatically generated, and the number of folder is limited (so I'm not looking at providing the users a way to translate their folder names, but a way to localize a predefined folder structure).
In a nutshell :
- is there a way to localize folder names ?
- if yes, is what's the best way to deploy this as part of a solution ?
Have you considered how Managed Metadata might be able to help you with this? If you're able to control terms that are also localized in Taxonomy, perhaps when creating a folder you would pull from the Managed Metadata Store, and then display the appropriate language based on the user's language setting. Just a thought... Since you know the name of the folder ahead of time, you could use that as a label for a folder name term, and then pull another label that matches the user's language and display that.
You can start using a resource files in your project and this link can help you about it.
But if you want to let the user, who creates a folder to set its localized name; then you should consider using SP event receivers.
I hope I've understood you correctly.

Resources