What is the function of the "screen" custom property in a canvas app component

[KASCHN]

I am very excited about the component libraries and while building my component and custom properties, I noticed that there is a datatype of "screen". Does anyone have any examples of how this is used? Like, can you pass a screen as an input property? Why would I do this? Or is this used to add an entirely new screen back to the canvas app.

Looking forward to your suggestions.

[cha_cha · Accepted solution]

Hello @KASCHN 

Yes, you are right, you can pass the screen to the custom component. Similar to different dev platforms, it will be up to the creativity of the developer how to utilize it.

A simple example would be a dynamic prompt component with two buttons. Next and Back as shown below.

On the component:

On the button in the component:

On the Actual component imported to a screen:

This might not be much if you only use the prompt component once. But let's say you use it multiple times, there is no predefined pattern of which screen it will go to next and you want to just put the destination screen instead of coding the Navigate function for each button. Another nice thing about this is you can standardize your button. So when you need to make changes, you will only need to go to the component and update one time instead of going to every screen.

Going back, I mentioned a bit about patterns. This is a nice example tutorial on that concept. Reza Doranni's side bar menu component. 

https://www.youtube.com/watch?v=3S0h2nODcxM

---

✔️	Just in case you my answer helped you solve your problem, please mark/accept this as a SOLUTION.  This helps community members if they experience a similar issue in the future.

🔗	🕸bistek.space  🐦 @cha_bistek  📺 @BisTekSpace