The existing profile generally comes from creating a profile from a surface. This is automatically done for any surface that you've specified as the active terrain. (To do this, use the button Set Active Terrain in the terrain model tools. As is true for so many other things we can do, there are other ways to set active terrain, but this is the simplest to communicate.) When you specify an active terrain, your active terrain surface shows up with all profiles. (In case you have reasons to set some other surface as active, you can always create a profile from any surface using other tools.)
Once you have the profile from the appropriate surface, you'll probably want to set that profile as active.
Your template will need to have one null point X-CL representing the CL (I assume this is the way you want to go), and place that one at 0,0 within the template editor. Add another null point X-ES-horizontal at, say, 22' to the right of the CL, also at 0 elevation. This particular point should be set to look for a specific feature definition (in my workflow, I have it look for the feature definition X-ES or something). Now add another point X-ES-surface: the horizontal will be locked to X-ES-horizontal. Ignore the vertical for the moment.
Once you have these three points, add an end condition component which starts at X-ES-horizontal and ending at X-ES-surface. Make sure it's looking for the appropriate surface. There may be other settings to look at and toggle, but for the most part, I think this will get you in the right direction.
When you create your corridor, make it based on the CL (if you're using the workflow I'm assuming), use the active profile (probably), and attach the edges of shoulder that you've traced.
As for the matter of feature definitions, your client or your state's roadway design office may have a workspace all set up, which will include feature definitions that you'll need. I won't guarantee that it will be foolproof. You may need to make tweaks for your project. You won't necessarily need to have a different feature definition for each ES. And it's unlikely that (for these purposes) you would even need a feature definition for the left ES and the right ES.
I hope that helps.
I'll be the first to agree with you that written documentation is abysmal and the notion that video documentation is effective is ridiculous. (Just like you can't grep dead trees, you also can't grep video; and even if you find the video you're looking for, skipping around that video leaves you open to missing important context.) I've been complaining about this ever since I started working with OpenRoads about 2 years ago. Be that as it may, there are some videos I've gotten really good information from. If I can find one that might help on this, I'll try to remember to post it here.
