Handling multiple "feature versions" in FastSpringAnswered

Hello again

I have set up my LimeLM node-locked licensing with a custom field for “license type”, which can hold “LITE”, “FULL”, or “PRO”, which determines the exposed features. Can FastSpring set that custom field, depending on which option the buyer selects?  Also, if the buyer wants to upgrade from LITE to FULL, for example, can FastSpring take into account that the user has already paid for a cheaper version?

Thanks for any suggestions!

ago
Answer

It looks like you could use FastSpring's “tags” to identify when specifc things are bought: License Keys

You can ask FastSpring if there's something more specific about their flow that you're looking for.

ago

Hi again, Wyatt.  Posting as guest, cause log-in failed for some reason.

Regarding the three functional versions of my add-in, I am still trying to understand how that will work with FastSpring. Kevin (from FastSpring) explained I would have to create three separate products in their store - each with its own licence-type setting in the custom field. However, I don't want to create three separate executables. Just one executable that exposes different functionality, based on that custom field in TurboActivate. Do you get my point and can you explain how to set this up?  THANKS ever so much.

ago

It sounds like he already explained it. You create 3 separate products in FastSpring. You set a custom license field depending on which one they order. They get a product key that will work in your single app (you don't create 3 versions, you just enable certain features depending on the field enabled).

See the docs for custom license fields: Custom license fields • LimeLM

ago

Hi again, Wyatt.  I think I'll need a bit of sample code for what you describe above, to “set a custom license field depending on which version they order”.  I assume this should be a few lines of script that I need to include in my FastSpring environment? Is this something you can provide?

Thanks again!

ago

The Web API pack, available on your API page, has a “FastSpring-PHP-Code.txt” file with example code that shows how to set a custom license field.

Also, our article about generating licenses in FastSpring using LimeLM tells you exactly how to do this.

ago

Fantastic.  I'll have a look.  THANKS

ago