How to assign a Blueprint to a TeamRaiser

You can't assign an existing teamraiser to a blueprint / different blueprint.  You can only / push create a new child teamraiser out of an existing blueprint.


As for "type" -- I am assuming you are referring to "Event Type" -- that is useful to group different teamraisers for use with the search API purpose (i.e. you want to show a listing of different events that have been grouped under a certain category / classification where the value of the assigned "event type" would serve as the filter on your API query parameter -- think of it more like "tagging" those teamraisers into a category.  But assigning those teamraisers under the same event type does not mean it will make those teamraisers inherit a Blueprint configuration.


Other thing would be "Security Category" -- assigning teamraisers into same security categories would allow them to benefit from using the same components (i.e. pagewrapper templating) belonging to that the Security Category, but this also will not make an existing teamraiser automatically available to be associated with a blueprint.  However, this could be your less-than-ideal solution to achieve certain things, say if you want to use same pagewrapper that a blueprint is using, hence, you can associate those otherwise non blueprint children teamraisers into using that same pagewrapper through the backend configuration; but certain blueprint inheritance (like whatever is defined in the blueprint settings, blueprint AutoResponder components, suggestion messages, won't be automatically pushed / inherited to those non-children Teamraisers)



regards,

Daniel

Hi Michael,


Is it pushing a new child or pushing changes to an existing child?


New child:

To create a new child from a blueprint,   click on the "Copy" link under that "Action" column associated to your Blueprint row. You should be brought to the next page that gives you 3 options (Copy Blueprint, Create a Child Blueprint, or Create a Child Event); choose the last one and fill up the "Administrative Name" and check the checkbox if your Blueprint has coaching email(s) you want to carry over to your newly created child.


New changes to existing child / children:

1. Make the changes first on your Blueprint, save and you might want to "lock" the section that you made the changes prior to make the push of those changes -- you'll see those lockpad icons on some sections (for any that have those lockpads, click on the lockpad to ensure your changes is going to be pushed to the children; for some sections that doesn't have that lockpad, it's likely the changes are automatically carry forward to children (i.e. Stationery of a blueprint seems not to have lockpad, and when you make changes on that section it will likely automatically carry forward to the children as you save / finalize the changes). Add on notes:
   • The lockpad also serves as to either make those components accessible / available for child specific edits on the child teamraiser setting or not. So if you keep a component locked, change are only available from the blueprint and it can't be override on the child level. With that said sometimes you have to "push" twice just for the purpose of lock and unlock (because you need to lock for the changes to push, and you need to unlock to make it available for override at child level if that so the case you want)
2. Once you are satisfied with all the changes you made on the blueprint, exit that blueprint edit page and go back to the blueprint listing page, and this time click on "Push Changes" from that same "Action" column associated to your blueprint in question.  You'll be given a list of what is going to be changed and what is not, make sure you review them before you finalize your action. The push is happening overnight as you finalize it,

Important note: changes and push to an existing child would only honor those original setting / component that initially comes with the child when you first create that, meaning say if I have Teamraiser Custom Page A, B, C on the Blueprint and I make a new child, the child is going to inherit those A, B, and C pages and any changes you make and push at anytime afterwards from the blueprint will be pushed to the child. However if after that child has been created, and you happen to create Custom Page D on the blueprint, that will never get carry forward to the existing child and you can't never push that to the child. Hence it's always good to have all the things you need first laid out on the blueprint and then create child/children as opposed to litte afterthoughts modification here and there afterwards.


Also another hints:

You could always identify which teamraiser(s) are children of blueprint -- they should say under their name on your teamraiser listing page something like "Parent Event: your blueprint parent name"  -- so when a teamraiser has that underneath its name, you know that this is a child teamraiser of whatever blueprint specified there thus you can retrace back accordingly.

Always welcome Michael