First step? Started by creating a test project to be able to choose the best plugin that suited my needs.

However…In the moment that I had to install it in the final app, I ran into… “Element uses-permission#android.permission.CAMERA at AndroidManifest.xml:30:5-90 duplicated with element declared at AndroidManifest.xml” error!

The plugin was: https://www.outsystems.com/forge/component-versions/1403 , and by extensibility configurations, I reached the project URL, as in the image bellow.

So, after a brief research, I found out that what I had to do was a minor change in plugin.xml file, instead of having

I had to have:

So all I needed to do, was to change this snippet and compile it into the OutSystems project.

So, how can we do it without native software?

1^st step: create a git account at https://github.com/ and install git  https://gitforwindows.org/

2nd step: Fork the project.

Then, in your computer, open git bash in the project folder that you want the project:

Config your account on git bash.

 git config –global user.name “your username”

 git config –global user.password “your password”

or

git config user.name “your username”

git config user.password “your password”

And clone the project, as showed in the image bellow.

After cloning the project into your computer, make your code changes using any editor, and then, follow the steps:

1. Check modified files: git status
2. Add modified files into the list of the next commit: git add -u
3. Commit your changes: git commit -m “description”
4. Create a tag: git tag v1.0_1.0 -a
5. Push your changes into the server: git push origin –tags

The project is now ready to be compiled in OutSystems project!!

Open your plugin in OutSystems, and change the URL to your repository#yourtag

1 – Publish the changes
2 – Generate App – this will compile your plugin changes

Reinstall the app in your device, and test it! 🙂

References:

https://www.outsystems.com/forums/discussion/44842/box-camera-overlay/

https://github.com/phonegap/phonegap-plugin-barcodescanner/issues/418

The post How to modify and compile a mobile plugin using OutSystems appeared first on Blog IT.

So, although we know that OutSystems Development Platform is ‘top gun’ we also know that is developed by humans, and humans usually make mistakes.

Today I want to show you that you shouldn’t trust the default value of your variables, when bounding it to other than Basic Data types.

So the scenario is the follow:

Imagine that you are building a ComboBox and you bound this Combo’s Source Entity to a very simple Static Entity

A Person type, and we will assume that there only exists 3 of these, Adult, Child and Baby.

And so, all is good in the kingdom of Outsystems. You Bond the Combo to a variable of the type PersonType Identifier

And change the value of the combo to display the data based on the type of person you selected on that Combo.

So for instance you would have something like this (assuming that you have an entity with PersonType Identifier as an atribute for each PersonType and an Expression below the ComboBox to display the Name of the Person)

Now you bound that Local Variable’s default value to be ‘Adult’ type’, so that each time you enter the page it displays the Adults first.

And you are done with your development. All is working good, months have passed and you got 0 complains about your perfect and complex WebSite.

But today your Boss decides to call you and say, ‘We have done a great job building that website, but it’s somehow slow. As so, we will separate the entities and static entities and put them on another application.’

Like a good lad you do it, unaware about the danger that is coming…

So you start by moving the Entities to the other Application and doing so will, of course, create a ton of errors, because the module doesn’t know where are those entities you are referring to.

But once you manage the dependencies and grab the entities you moved to the new application the errors are automatically corrected because the amazing OutSystems will know that those are the Entities you are looking for. And so the green color of joy will appear…

Publishing it will be a terrible mistake, but you do it anyways.

What happened, you may ask? Here is what, once you moved the entities and you got the errors saying that there isn’t a known Entity to bound your variables and inputs, you lost your default value of your Variable bound to the ComboBox we mentioned in the beginning.

And this ‘Bug’ is a master in disguised because it leaves no errors or warnings.

What will happen is once you access your webpage you will find that you don’t have any adults to display.

But you do have, Hugo was an Adult like we have seen. In fact, if you change your combo box to any other value and change it back to the Adult value you will see Hugo there.

What is happening is, Outsystems will by default bound the variable to its default value, if there isn’t one, it will put the value to null, 0, or something similar. As the variable is bounded to the combobox, and we didn’t specify a specialList value it will display the first record of the static entity ‘Person Type'(the one we used to fill the ComboBox with) which is Adult.

This is a visual error, misleading the user to believe that there aren’t any Adults. But it could be a List of records, it could be a dead end, “if there aren’t any adults, disable combobox”, it could be something way more important than just displaying the adults that we have previously created.

So, in order to avoid this issue, you should always bound your variables, that you want to display straight away in the first load of the page, on the Preparation of the WebPage.

That way you will assure that even if someday you change the structure, entities, or static entities, the value you want to be firstly displayed will always be the same.

Oh, and leave the default values of the variables to Basic Data types 🙂

The post Beware of the Lost Variables Default Values appeared first on Blog IT.

1 – In Service Studio, open your module and goto Module -> Export -> Save As…

2 – Navigate to Intellectual Property Protection (IPP) Rights Validation

Here you need to enter your email, the destination activation code for your target infrastructure, and upload your OML

3 – You will receive an email with the OML file without IPP protection. Download the file.

4 – In Service Studio goto Module -> Open File…

5 – Publish your module

The post Move modules – Remove IPP – OutSystems appeared first on Blog IT.

Internal Error 
No data type 'Status' could be found. 
Exception Details:
[1] Internal Error: No data type 'Status' could be found.
at OutSystems.HubEdition.Compiler.WebWidgets.ComboBox.dumpEntityDeclaration(TextWriter res)
 at OutSystems.HubEdition.Compiler.WebWidgets.ComboBox.DumpDataBindingCode(TextWriter writer)
 at OutSystems.HubEdition.Compiler.AbstractServerWebWidget.DumpOnDataBinding(TextWriter writer, NodeViewState viewState)
 at OutSystems.HubEdition.Compiler.AbstractServerWebWidget.DumpHandler(TextWriter writer, NodeViewState viewState)
 at OutSystems.HubEdition.Compiler.WebWidgets.ComboBox.DumpHandler(TextWriter res, NodeViewState viewState)
 at OutSystems.HubEdition.Compiler.Nodes.WebScreen.Dump(TextWriter writer)
 at OutSystems.HubEdition.Compiler.Flows.WebFlow.Dump()
 at OutSystems.HubEdition.Compiler.WebFlows.WebHandler.Dump(IEnumerable`1 webFlows)
 at OutSystems.HubEdition.Compiler.ESpace.Dump()
 at OutSystems.HubEdition.Compiler.Compiler.InnerCompile(CompilationContext context)
 at OutSystems.HubEdition.Compiler.Compiler.Compile(CompilationContext context)
 at OutSystems.HubEdition.Compiler.Utils.CompilerUtils.WithOverridenSettings(IDictionary`2 settingsOverride, Action body)
 at OutSystems.HubEdition.Compiler.Compiler.<>c__DisplayClass3.<Compile>b__1()
 at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
 at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
 at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
 at System.Threading.ThreadHelper.ThreadStart()

But TrueChange didn’t show me any errors or warnings. I got this error only when I tried to publish the application.

The problem was that the variable that I defined to hold the value entered by the user was of the Static Entity type instead of the Static Entity Identifier type.

That variable “Status” was defined like this:

And must be defined like this:

It must be a Status Identifier instead of the Status (static entity).

The post No data type ‘TYPE’ could be found – OutSystems Combo Box appeared first on Blog IT.