Transcript:
0:00 [Music]
0:05 in this video we're going to show you
0:08 how you can use the North52 data
0:10 package to move functionality that
0:12 you've created on the portals from one
0:14 environment to another our scenario here
0:17 is that we have got a product
0:19 registrations functionality on our
0:21 portal that consists of a entity list
0:25 here and a form to create a new product
0:29 registrations we want to be able to move
0:32 this from one environment to another
0:34 easily we can do this using in North52
0:36 data package our first thing we want to
0:38 do is create a new solution to hold our
0:41 data package so just down here and add
0:47 in the name choose the publisher I use
0:52 the default one if you like and just put
0:54 a version number in here click Save and
0:57 close
0:58 then we navigate to Owl
1:02 david packager signor $52 data package
1:07 and create a new data package in this
1:11 case we'll just give it the same name as
1:13 our solution one that's there by default
1:19 and we also need to change the
1:21 deployment settings from the default
1:22 solution to our data package a solution
1:27 for the product registration then we
1:33 click Save now there's a number of
1:38 components that we need to add to this
1:39 data package to capture all the entities
1:42 that contain the configuration data for
1:46 the portals I think it's like the entity
1:48 permissions web roles associations forms
1:51 metadata for the form list and web page
1:55 and also the finally the web thing one
1:58 of the things that we need to do as part
1:59 of the set up of the stated package is
2:03 we need to exclude certain fields when
2:06 we're building up the data package so we
2:08 have a configuration sitting here
2:11 configuration exclude fields and in here
2:15 all the fields that we don't want to
2:16 bring into the data package and the as
2:18 you can see some of these things like
2:20 status codes owners etc when we're
2:23 creating data packages with portals
2:26 quite often we don't want to also have
2:30 the created by the author ID and created
2:34 by be user named etc in there as well so
2:37 I've just added those three entities the
2:38 author ID created by username modified
2:40 user by name into this area here as well
2:45 so once that's done we are ready to add
2:48 some data to our data package so we can
2:52 come across to explore tab and the first
2:55 thing that we're going to add is the
2:58 entity permissions so we're going to go
3:00 across navigate to entity permission and
3:05 it'll bring back all the entity
3:07 permissions in this instance and so I
3:10 just want to look for the one that's
3:11 concerned with their project product
3:13 registration
3:15 and there's two here so I simply check
3:17 those two and then click on the
3:19 lightning bolt to add those interesting
3:22 permissions to our data package second
3:25 thing that we're going to do is add the
3:28 web roles that are related to these
3:30 interesting permissions so I just need
3:32 to expand both of those records here and
3:37 expand the related to entities here we
3:39 can see here's the web role there we
3:42 want to check that and we want to expand
3:45 this one here as well so I want to add
3:48 those just click click those two and we
3:50 can see that we've got another sheet
3:52 that's been added here and that will
3:53 create many to many relationships
3:55 between the entity of admissions and the
3:57 web roles the next item that we need to
4:01 bring along is the entity form so if we
4:06 look at the entity form we can see our
4:08 product registration one here so we want
4:12 to add that and there's also some
4:17 metadata that belongs to this entity
4:20 form so we can either get that from our
4:22 list density form this data here or we
4:25 can just expand the relationship here
4:29 and look for the entity form mr. data
4:33 and we can see here here's the record we
4:36 just need to check that and click our
4:39 lightning bolt again and that's going to
4:41 add the entity form metadata for this
4:44 particular record we have an entity list
4:48 that we want to add as well and again we
4:53 don't need to filter down these records
4:55 we can see which one it is I simply
4:57 click on the product registration one
4:59 and add that to my data package there
5:04 are web pages which hosts the entity
5:07 listen form so I just need to look for
5:10 the web page and see in here again this
5:15 one I will need to filter down so just
5:18 do a sort of search for my product
5:19 registration again it's best to have
5:23 these ordered route ones first so I can
5:25 just simply click the search again that
5:26 will reverse the search
5:28 and I just want to click all those I can
5:30 use The Awl selection here as well click
5:34 that and we can see all the web pages
5:37 that have gone through notice that we've
5:39 also got another a couple of entities in
5:44 here are sari sheets in here web page
5:48 self referencing updates so this is the
5:51 post web page create so once these web
5:54 pages have been created there's another
5:55 step in here which associate those web
5:58 pages to the the relevant parent pages
6:01 the final thing that we or final piece
6:04 that we need to add to the data package
6:09 here for configuration data is the web
6:13 link so if we look for the web link so
6:15 this will determine the navigation so we
6:19 can find the product registrations and I
6:22 just need to add that and I can click
6:27 click that to add that to my data
6:29 package as well now that we've got all
6:31 the data added to our data package we
6:34 can set up the ability to disable
6:39 plugins and processes and so when you're
6:41 building out data packages for portals
6:43 and where they can contain webpages this
6:47 practice will be to disable any plugins
6:49 because when you create a webpage it
6:51 creates a child web page for the
6:53 language variant but because we've we
6:55 are creating that as part of our data
6:57 package here we can see that we've got
6:59 the product registrations here and the
7:03 so the product registration root page
7:06 and then we've got a product
7:07 registration English language page here
7:10 as well so that's all created so we
7:12 don't need to rely on the Alpha box and
7:15 plugins creating those pages so we need
7:17 to disable those so one of the things
7:19 that we've got is the ability to
7:22 disable and enable plugins once a
7:26 desolated package is executed so to add
7:29 that functionality to a data package we
7:30 come to snippets DP setup processors we
7:33 click that and a couple of sheets are
7:37 added to our data package so we've got a
7:38 deactivate plugins sheet here and then
7:41 at the other end we have got a activate
7:44 plugins inactivate processes the
7:47 processes themselves that are activated
7:49 on this and deactivated on these sheets
7:50 are contained in the global calculations
7:53 here and we can see here the entities to
7:56 disable and any workflows that we want
7:58 to disable in here the entities that we
8:01 want you to disable for this particular
8:03 one so if I come into here and expand
8:06 this out I can just copy and paste these
8:08 in so know what they are but they relate
8:10 to the entity form the metadata empty
8:13 list web page permissions etc so in any
8:16 entity that you're updating it can be
8:18 safe to assume that you might want to
8:19 delete that or disable those plugins so
8:26 once that's done we all we need to do is
8:29 save our data package and it's ready to
8:35 be exported as part of the solution so
8:37 we'd go back to our solutions here
8:42 product registration 1 here if we open
8:45 that up we will see that we've got some
8:48 data package records and we've also got
8:50 some ex cash data package records as
8:53 well so these store information that's
8:57 not able to be contained in the data
8:58 package of sheets itself so it might be
9:00 HTML code or the fields that are too
9:03 long to store in the data pack yourself
9:05 we store those as X cash records and
9:07 once you've got this all set up all you
9:11 need to do click on the export solution
9:14 and import it to your target environment
9:18 and click the execute data package on
9:21 the target environment and you will have
9:23 that deployed for further information
9:25 please see our website North52 comm or
9:28 our knowledgebase
9:30 at support North52 com