We have a custom solution made up of several screens that are packaged as a customization package. We'd like to be able to lock that down so that users need to purchase a license key to use these screens. I don't want to re-invent the wheel, so I'm wondering if there are standard examples (if this has been done before) on how to integrate this with Acumatica's license system.
It is not possible to integrate with the Acumatica licensing system. We implemented our own licensing and required the license when the Acumatica license has been applied. This is indicated by PXLicenseHelper.License.Licensed
I should point out I did spend a good amount of time on this very question before we implemented licensing for our product.
Related
I've been using VS Code for a year or so now. I have no idea how VS Code Extension security is handled.
I'm alarmed by things like this:
Markdown Preview Enhanced (927K+ downloads)
Markdown Preview Enhanced (fork that points to the original repo) (2k+ downloads)
Some questions I have are:
What does Microsoft do to ensure Extensions we install are safe?
Are they scanning the Extensions for known vulns?
Is VS Code safe to use in an Enterprise Environment?
How can I tell?
Why are duplicate extension names allowed!
There are security and marketing implications by Microsoft allowing "package-squatting".
Does anyone have insights to share regarding VS Code Extension Security?
Hm. Unfortunately, the link to "extension marketplace terms" that #jonrsharpe provided does not include the word "extension". If you extrapolate VS Code Extensions to be covered by the Azure Marketplace terms (as alluded to in the text), then you get this little tidbit:
https://azure.microsoft.com/en-us/support/legal/marketplace-terms/
Publisher Privacy Policies. Publishers are responsible for providing
privacy statements that describe their privacy practices with respect
to Customer Data collected by their Offerings or any customer
information that they receive from Microsoft. Unless indicated
otherwise in connection with a Marketplace Offering published by
Microsoft, Microsoft’s privacy, security, and data location and data
retention policies will not apply to any Marketplace Offering or to
Publishers’ use of any Customer Data or other customer information.
In short "...Microsoft's privacy, security...policies will not apply to any..." VS Code Extensions OR to "...Publishers' use of any Customer Data or other customer information."
Microsoft does NOT handle VS Code Extension Security.
Is there a Kentico Small Business Edition for purchase?
https://www.kentico.com/download-demo/free-cms-for-asp-net/kentico_12_editions.pdf
You should email sales#kentico.com and ask them. Since what is available to purchase starts at Base on their site, this small business one might be a free one under special conditions or no longer offered.
The Kentico Small Business License was introduced in 2009 as something that is only available to Kentico partners. This was following feedback from existing partners that smaller clients who did not need the full features of Kentico CMS.
It is still available as far as I am aware, but you would need to be a partner to get access to it.
I have to implement product configurator in hybris platform that allowing users customization front office interface (product details).
Like changing color of product, size, make text and managing prices.
I'm looking actually for open source product desinger.
Anyone has an experience with any integrated framework or any other recommendations ?
Kind regards,
Soufiane
If you are not using SAP CPQ which is integrated with Hybris out of the box, you can have a look at openCPQ
Managing the sizes, prices etc of products is performed via the productcockpit. Changes you make here will be reflected in the Accelerator storefront. This is also extensible and customisable.
I am looking for a product that can solve a problem for me, and I hope you can help me with this ASAP.
I have a client which needs software modules to be integrated together, the following are the modules with what I think is the software that fulfills its goals next to it:
Document Management System (DMS): Sharepoint Portal.
Company Organization Structure (needed for workflows and used in DMS also): Probably custom development integrated with Active Directory and sharepoint portal.
Workflow Managment System (or BPM): Nintex Workflow.
The questions are:
Are the points above logical, or is there something missing.
Will it take too much time for development to integrate the Company organization structure with the workflow management and sharepoint, or is there a simpler solution, such as a built in Organization Structure in sharepoint or in Nintex Workflow?
I am still reviewing software solutions, I am not familiar with sharepoint, a combination of software solutions which lead to this product/solution I can use as a product later on for future clients is what I am looking for also.
For example, let's say we have a Leave request workflow process, the process is as follows:
Start -> Fill Leave Form -> Approve Form by CURRENT active manager -> save leave form data by HR team (on file or on separate HRMS) -> Close process
The organization structure is defined, and then the "CURRENT active manager" is defined for a group of people, the process will be built by a "workflow management system"/BPM software, the "Leave Form" can be a webform, or a template stored on a document management system.
I'm not familiar with Nintex Workflow however if your active directory information is up to date, in terms of the organisation structure and user details & groups, the organisation structure is probably supported out of the box by SharePoint.
Thus all that might remain is the workflow component which again could probably be created using standard SharePoint functionality, with minor customization with SharePoint Designer.
Having said that, configuring and installing SharePoint is not simple, and needs some thought.
From my experience with Nintex Workflows, it integrates really well into SharePoint and would work in a hierarchical company organization structure. If Active Directory is correctly set to indicate "bosses", "subordinates", etc, this information can be used within the workflow. For instance, "Send this workflow to my boss", followed by "send it to his boss", would be simple to program, since that information would be available from Active Directory.
Depending on what is needed, standard OOB SharePoint and Nintex can be used together to produce amazing workflows. One of the major advantages of using Nintex Workflows is that it can be used without programming. However, if programmers are available, additional logic can be added to augment a workflow (such as event-level programming).
Let's assume that you've created a SharePoint solution - a WebPart, a feature for a List Template, whatever - that you are planning to sell as a product.
How would you go about handling licensing of your solution?
I'm looking for some input in at least the following areas:
Code-wise:
1.1. Where do you keep the license itself? as a file somewhere? (then what happens in farms?) as a property in the property bag of the farm?
1.2. Do you implement "home-calling" - where your solution validate the license every now and then against your company's servers?
1.3. Any other best practice in this area will be welcome...
Business wise: How do you license - per user? per server? per instance (in case of WebParts or List Templates)?
Thanks.
I could tell you what we do:
We have a separate farm solution that handles trial/registration support for all our products
The license is eventually stored in the farm property bag (you have to support multiple servers)
We have a page to enter license key under the central admin solution's page
We license by front-end, you can know the number of front-end in the farm in code.
All products have a product name and the license key is a one-way encryption containing the product name. the trial support solution handles key validation.
1.1 You have to put in in the documentation and in the distribution files.
1.2 I would not do that for a sharepoint web part.
1.3 Invest in layout, documentation, support... Not just in the product itself.
Nobody will be able to answer that without knowing detailed information about your product, your market, your competitors, the alternatives, etc. Consider this book if you are serious about pricing.