When I tried to download load runner free trial its asking for business email. how to download the setup?
This is an issue you need to take up with Microfocus. Keep in mind the license for the evaluation version is not for production use.
As a commercial tool, the vendor expects that at the end of your trial, if the tool meets your needs that you will have the means to purchase it. They6 will want to have salespeople follow up. Having a public email prevents that type of activity in most cases.
Related
I have a couple of months using Google Chrome Web Developer dashboard. Everything was very normal, publishing an updated version was taking around 30-40 mins, now that I added a few elements to my extension such as popmotion.js it keeps requiring manual revisions and my extension gets into "Pending for Review" state for so long.
My question is: Is this caused by something I could have done in the code? Is it possible to get rid of this condition that keeps telling Google's services that my extension needs to be manually reviewed?
Thanks in advance!
According to this link, Pending review means the Chrome Web Store automated systems have flagged your item for manual review.
Some of the reasons an item could be flagged for manual review include:
The item may have an NPAPI plugin, which requires a signed agreement from you. Check your email account associated with the item for an agreement notification from our abuse team.
The item is suspected to contain or to be distributed by malware or unwanted software.
The item is suspected to violate one of the developer program policies.
The item may have already been previously removed for a legal or policy violation, and has been resubmitted.
The item requests powerful permissions that require in-depth review.
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.
I want To Ask About The licence for ErpNext ERP GNU GPL3 , is it possible to get source code and change it and resell it
I think what you are talking about here is illeagal under theft of intellectual property, if the source code is not listed as "public domain" code odds are it belongs to someone
Looking for solution to be able to allow our CRM users to sign online documents on our site , is there opensource solution for this ?
basically we will be signing the documents on behalf of the customer for the supplier but of course customer himself will be signing online, so here we will use one certificate to sign for different customers... timestamp and other features required to be the legal,
and if there is open source solution or one of small cost product would cover Annex1 and Annex2 all the required points
http://www.berr.gov.uk/files/file49952.pdf
we found this but would this work on Linux servers http://www.signfiles.com/digital-certificates/ and ItextPDF but would any of this be ok for legal side of things ?
Thnx
You might want to check out a service like DocuSign which already has integrations with major CRMs. Your main issue here is proving that it actually happened and that it's legally binding. The best way to do this is not to have an open source solution that you control, but to rely on a trusted 3rd party.
Full disclosure: I work for DocuSign.
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.