npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@iivanov/omnistudio-utils

v1.0.42

Published

OmniStudio CLI to allow renaming components and updating references.

Downloads

71

Readme

omnistudio-utils

This CLI allows you to perform tasks to rename OmniStudio components and remove special characters (mostly underscores) as part of your migration to Core and allow you to enable the Metadata API. After the renaming is done you can run additional commands to update cross references.

Here is how the Unique Name is constructed :

| Component | Object | Fields That Create Unique Name | |-------------------------|-------------------|---------------------------------| | Integration Procedures | OmniProcess | Type + Subtype | | Omnistudio Data Mappers | OmniDataTransform | Name | | Omniscripts | OmniProcess | Type + Subtype + Language | | Flexcards | OmniUiCard | Name |

All actions are performed locally based on content that is already downloaded using VBT / IDX. Once you are ready you can simply deploy the updated content into your Sandbox.

Please note that the CLI only supports Core Objects, assuming you have already migrated from Package into Core Objects for which you can use : https://www.npmjs.com/package/@salesforce/plugin-omnistudio-migration-tool

Disclaimer: This CLI is not an official module from Salesforce. It was created with the intent of distributing certain utility capabilities. Use it at your own risk.

Supported scenarios:

  • Rename IntegrationProcedure

  • Rename DataMappers

  • Rename OmniScripts

  • Rename FlexCards

  • Update IntegrationProcedure references

    • In FlexCards
    • In OmniScripts
  • Update DataMappers references

    • In FlexCards
    • In IntegrationProcedures
    • In OmniScript
  • Update FlexCard references

    • In FlexCards, directly embedded
    • In OmniScripts
  • Update OmniScript references

    • In Parent OmniScripts
    • In FlexCards

Patterns that are not supported yet:

  • References of OmniScripts or FlexCards within a Custom LWC (2nd level dependencies)
  • References of FlexCards as Flyouts within another FlexCards.
  • Set custom patterns for renaming. Currently all special characters and underscores are automatically removed.

Install

npm i @iivanov/omnistudio-utils

Note that you must install VBT/ IDX in order to export and deploy the updated content.

Usage

The default source folder to be looked up is set to ./vlocity. You can pass the folder to the command if your folder name is different.

Please note that you first need to execute the rename commands and then those to update references. Each Rename command will create a local JSON map file with the source and taret names to be used for the Reference commands.

Rename IntegrationProcedures:

npx omnistudio-command-exec rename-ip ./vlocity

Rename DataMappers:

npx omnistudio-command-exec rename-dm ./vlocity

Rename FlexCards:

npx omnistudio-command-exec rename-flex-cards ./vlocity

Rename OmniScripts:

npx omnistudio-command-exec rename-omniscripts ./vlocity

Update DataMappers references:

npx omnistudio-command-exec update-dm-references ./vlocity

Update IntegrationProcedure references:

npx omnistudio-command-exec update-ip-references ./vlocity

Update FlexCards references:

npx omnistudio-command-exec update-flex-cards-references ./vlocity

Update OmniScripts references:

npx omnistudio-command-exec update-omniscripts-references ./vlocity

Once you are done, you can deploy to your target using VBT.